Using PackageInfo.signatures to get public ke

by Yuliy Pisetsky » Fri, 16 Jul 2010 06:35:17 GMT

Sponsored Links

I was wondering if there's any more detail that can be extracted from
PackageInfo.signatures. For instance, can we extract the public key
that was used to sign the package? (and trust that the OS had already
verified that the APK was indeed signed with the corresponding private
key). What I'd want to do is to be able to have a list of trusted
partners that are allowed to call my app, with those partners all
having separate keys. I'd have a database of partners and their public
keys available somehow (embedded or on a web site), and would be able
to make security decisions based on who the caller is (while reducing
the risk of the user making an incorrect decision and granting an app
which shouldn't have that access the permission to call my app.


Other Threads

1. Developer does't see comments on android market from other countries

On Cyrket only comments published by phones with English locale are


2. GLSurfaceView Renderer problem

I've been working through some of the OpenGL stuff, but I've hit a bit
of a snag. I'd like to use the RENDERMODE_WHEN_DIRTY renderMode, but
it doesn't seem to recover from an incoming call properly -
onSurfaceCreated() and onSurfaceChanged() are not being called. The
docs say to call onPause() and onResume() at the appropriate times and
I've done that, but still no go.

I put in some debug prints and when RENDERMODE_CONTINUOUSLY is set, it
works fine - in fact, everything works fine either way until the app
is paused and resumed with RENDERMODE_WHEN_DIRTY. I'm really new to
OpenGL, so perhaps there's some black magic I'm missing. Any hints?

I should mention I'm using android-sdk-windows-1.5_r2, jdk1.6.0_14,
with Eclipse version 3.4.2. I've only seen this on the emulator so far
- I don't have a device yet.


3. PPC based development

4. how to install Android build on a g1

5. GLSurfaceView.Renderer onSurfaceCreated/onSurfaceChanged not called if RENDERMODE_WHEN_DIRTY

6. pressing menu key slows down surfaceview

7. Map problem