On Thu, Jul 18, 2013 at 10:20 PM, Alex Gerdov <[email protected]> wrote:
> Your are right, I've used auto-generated Eclipse key to sign the app. > I've found the keys you mentioned, but what do I need to do with them now? > > > > On Thu, Jul 18, 2013 at 2:30 PM, rpcraig <[email protected]> wrote: > >> On 07/18/2013 07:23 AM, Alex Gerdov wrote: >> >>> Hello, >>> >>> I've tried to label an app I created with my own custom label, but it >>> always gets the "untrusted_app" context. >>> >>> I've made the following changes: >>> >>> "type my_app, domain; >>> app_domain(my_app)" >>> >>> to app.te and >>> >>> "user=_app seinfo=release name=com.text.myapp domain=my_app >>> type=platform_app_data_file" >>> >>> to seapp_contexts >>> >>> Can anyone please tell me what I'm missing? >>> >>> Thanks. >>> >> >> Are you signing this new app with a different key then any of release >> keys in AOSP? The mac_permissions.xml file >> (external/sepolicy/mac_**permissions.xml) >> maintains a mapping for the various seinfo tags under the protection of the >> apps signature. It could be that your app's sig is not matching any entry >> in the mac_permissions.xml file and thus falling into the default bin with >> seinfo=default. >> > >
