I used command mm -B in external/sepolicy directory. We are still using
4.1.1 code base.
I¹m currently looking into the insertKeys.py to troubleshoot this issue.

Tai

On 1/24/14, 3:11 PM, "Stephen Smalley" <[email protected]> wrote:

>On 01/24/2014 02:56 PM, Tai Nguyen (tainguye) wrote:
>> All,
>> 
>> It seems that the external/sepolicy/Android.mk uses the keys.conf to
>>generate different mac_permissions.xml file for different builds.
>> However, although I use different keys in keys.conf
>> 
>> [@PLATFORM]
>> ENG       : build/target/product/security/platform.x509.pem
>> USERDEBUG : build/target/product/security/platform.x509.pem
>> USER      : build/target/product/security/MyPlatform.x509.pem
>> 
>> [@MEDIA]
>> ENG       : build/target/product/security/media.x509.pem
>> USERDEBUG : build/target/product/security/media.x509.pem
>> USER      : build/target/product/security/MyMedia.x509.pem
>> 
>> 
>> [@SHARED]
>> ENG       : build/target/product/security/shared.x509.pem
>> USERDEBUG : build/target/product/security/shared.x509.pem
>> USER      : build/target/product/security/MyShared.x509.pem
>> 
>> # Example of ALL TARGET_BUILD_VARIANTS
>> [@RELEASE]
>> ENG       : build/target/product/security/testkey.x509.pem
>> USERDEBUG : build/target/product/security/testkey.x509.pem
>> USER      : build/target/product/security/MyRelease.x509.pem
>> 
>> 
>> However, when I set TARGET_BUILD_VARIANT=user or eng and do mm ­B, I
>>got the same mac_permissions.xml output.
>> What am I missing?
>
>Can you clarify exactly what commands you are executing, and what branch
>you are building?  It seems to be working for me.
>


_______________________________________________
Seandroid-list mailing list
[email protected]
To unsubscribe, send email to [email protected].
To get help, send an email containing "help" to 
[email protected].

Reply via email to