Was there a possible use-case envisioned for declaring this protection level?
I mean the how can system application be aware of your (3rd party) app's functionality in the first place? Thanks. On Mar 27, 9:45 am, Dianne Hackborn <[email protected]> wrote: > Um yeah I guess you could use it for an app that is installed as a third > party app. I can imagine any reason in the world why you would want to do > that though. Actually it probably wouldn't work, since the system processes > system apps first, so it wouldn't know about your third party app permission > until well after it has granted permissions to the system apps. > > On Fri, Mar 27, 2009 at 3:47 AM, guillaume leterrier (Teleca Germany) < > > > > [email protected]> wrote: > > >http://developer.android.com/guide/topics/manifest/permission-element... > > > "signatureOrSystem" A permission that the system grants only to > > applications that are in the Android system image or that are signed > > with the same certificates as those in the system image. > > > I guess the above statement is a bit misleading. "that are signed with > > the same certificates as those in the system image. " > > > Indeed, they must be signed by the same certificate, but not necessary > > by one from the system image. Basically, this is the equivalent of the > > protection level "signature". However, the above statement assumes > > that "signatureOrSystem" protected permissions are only declared by > > applications located in the system image. > > > guillaume > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support. All such questions should be posted on public > forums, where I and others can see and answer them.
