Ok, cool, thanks!
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers+unsubscr...@googlegroups.com
For mor
Got it, thanks! Here's the snippet of code:
Signature[] sigs =
getBaseContext().getPackageManager().getPackageInfo(getPackageName(),
PackageManager.GET_SIGNATURES).signatures;
for(Signature sig : sigs)
{
byte[] hexBytes = sig.toByteArray();
On Thu, Jun 9, 2011 at 12:21 AM, Dom wrote:
> Got it, thanks! Here's the snippet of code:
>
> Signature[] sigs =
> getBaseContext().getPackageManager().getPackageInfo(getPackageName(),
> PackageManager.GET_SIGNATURES).signatures;
> for(Signature sig : sigs)
> {
3
Sent from my Verizon Wireless Phone
-Original message-
From: Nikolay Elenkov
To: android-developers@googlegroups.com
Sent: Wed, Jun 8, 2011 11:46:52 GMT-03:00
Subject: Re: [android-developers] Re: How do I get the MD5 fingerprint of my
application certificate through code?
On Wed
On Wed, Jun 8, 2011 at 10:54 PM, Dom wrote:
> Actually, I (and mendhak's original post) would like to get the MD5
> fingerprint via CODE or PROGRAMMATICALLY. Getting it via the keytool is well
> documented in tonnes of places across the web.
>
Simply use the MessageDigest class to calculate the h
Actually, I (and mendhak's original post) would like to get the MD5
fingerprint via CODE or PROGRAMMATICALLY. Getting it via the keytool is well
documented in tonnes of places across the web.
I would like to implement an architecture similar to google maps api. The
way google maps authorizes re
Hi Dude,
follow this link ..
it will work
http://blogspot.fluidnewmedia.com/2009/04/displaying-google-maps-in-the-android-emulator/
On Wed, Jun 8, 2011 at 6:37 PM, Dom wrote:
> Hi mendhak, did you solve this problem? Were you able to get the MD5
> Certificate Fingerprint of your app programmatic
Hi mendhak, did you solve this problem? Were you able to get the MD5
Certificate Fingerprint of your app programmatically? Any directions on how
to achieve this please?
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this grou
On Sun, Apr 11, 2010 at 6:08 AM, ko5tik wrote:
> It definitely varies - I use several boxes for development (my
> older laptop retired to mother in law house ;) ) and I have to uninstall
> apps compiled with debug keys before I can start them from other box.
>
I believe that the debug key is
> I'm curious as to whether these are always the same, or generated for
> us and unique to each SDK install, but I'm not going to look just now.
It definitely varies - I use several boxes for development (my older
laptop
retired to mother in law house ;) ) and I have to uninstall apps
compiled
OK, converting to base64 (using your link), formatting it as a
certificate file, and using openssl to parse the result, we get to see
the actual content:
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1269799100 (0x4baf98bc)
Signature Algorithm: sha1WithRSAEncryption
Hi, thanks for responding.
I had a look, and yes, the bytes were the same as the 979 character
string (hex) - they contained the certificate itself. I should post
it here anyways, since it is the debug certificate in this case.
Well, here it is:
--
308201e53082014ea003020
Actually, the package manager would be able to check using the API.
The only thing that was at question was whether the byte sequence
included anything beyond the certificate or not. We know the API
doesn't. Actually, what I'd like to know is whether it includes the
certificate, or just the public
On Apr 5, 6:09 pm, Bob Kerns wrote:
> Hashcode would not be secure. That is, you can construct an alternate
> app+signature that would produce the same hash code. That may be good
> enough for you, but I would discourage such a technique. However, you
> could construct a secure SHA-1 hash of th
Well, first, there's likely to be no MD5 hash involved at all. DSA
with SHA-1 would be the default signature type now, I believe.
Hashcode would not be secure. That is, you can construct an alternate
app+signature that would produce the same hash code. That may be good
enough for you, but I would
Still struggling with this. Based on what you said, I tried playing
with this:
Signature[] sigs =
getBaseContext().getPackageManager().getPackageInfo("com.whatever.blahpackage",
64).signatures;
(64 = GET_SIGNATURE)
I then had a look at
sigs[0].toCharsString()
which produced a 979 character lo
I'm also gnawing on the same problem. At the moment
I'm investigating following path:
Context -> Package Manager -> Package info (for name, with
signatures ) -> Signatures
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this g
17 matches
Mail list logo
