On Wed, Jul 30, 2014 at 4:58 AM, reox <[email protected]> wrote: > ... > > The Author speaks from PKI and Chain of Trust - but as far as i know this > was never planed to be used on android. As far as i understand the concept > of code signing on android, it is just a bit-per-bit compare of certificate > files to ensure that the app is allowed to do things.... Actually, there are 3 or 4 platform signing keys. The keys work in a traditional code signing sense. Platform vendors are expected to change them from the default provided in the AOSP code (I'm waiting to read about that vulnerability). The platform keys are the 'system' in signatureOrSystem.
You are right about typical application signing, too. That's the 'signature' in signatureOrSystem. Application level signing essentially ensures continuity. That is, once an app is published, only the author can update it. It does not really serve any other purpose (IIRC). With respect to 'signature', I don't know about the intersection with the business cases. For example, what Google does behind the scenes when it requires a developer sign up for an account, and how it binds the account with the signing keys. From the outside, we don't get to see those details. See Android Security Underpinnings by Marko Gargenta at http://www.youtube.com/watch?v=NS46492qyJ8. Nikolay Elenkov also has a good article at http://nelenkov.blogspot.com/2013/05/code-signing-in-androids-security-model.html. (Related: Nikolay has a book coming out soon on Android Security. If you follow his blog, you probably know it will be good reading). Jeff -- You received this message because you are subscribed to the Google Groups "Android Security Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/android-security-discuss. For more options, visit https://groups.google.com/d/optout.
