signature clause in mac_permisions

signature clause in mac_permisions

[William Roberts]

[-- Attachment #1: Type: text/plain, Size: 332 bytes --]

How did you guys generate the hex encoded x509 string for a
signature clause in mac_permissions.xml?

Did you use the Android "dumpkey.jar"?

I have the signed apk's, the keystore used to sign them, .pem files which
have all the pub keys in them and a p12 and p8 file.

Which one should I use?

-- 
Respectfully,

William C Roberts

[-- Attachment #2: Type: text/html, Size: 471 bytes --]

Re: signature clause in mac_permisions

[Robert Craig]

[-- Attachment #1: Type: text/plain, Size: 575 bytes --]

Just run the setool host tool. To build just 'make setool' and then to run
just 'setool'. The help usage statement will guide you.

On Mon, Sep 17, 2012 at 2:34 PM, William Roberts
<bill.c.roberts@gmail.com>wrote:

> How did you guys generate the hex encoded x509 string for a
> signature clause in mac_permissions.xml?
>
> Did you use the Android "dumpkey.jar"?
>
> I have the signed apk's, the keystore used to sign them, .pem files which
> have all the pub keys in them and a p12 and p8 file.
>
> Which one should I use?
>
> --
> Respectfully,
>
> William C Roberts
>
>
>

[-- Attachment #2: Type: text/html, Size: 1017 bytes --]

Re: signature clause in mac_permisions

[William Roberts]

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

I should have RTFM, it is right on the wiki under install time mac
http://selinuxproject.org/page/SEAndroid



On Mon, Sep 17, 2012 at 4:22 PM, Robert Craig <robertpcraig@gmail.com>wrote:

> Just run the setool host tool. To build just 'make setool' and then to run
> just 'setool'. The help usage statement will guide you.
>
>
> On Mon, Sep 17, 2012 at 2:34 PM, William Roberts <bill.c.roberts@gmail.com
> > wrote:
>
>> How did you guys generate the hex encoded x509 string for a
>> signature clause in mac_permissions.xml?
>>
>> Did you use the Android "dumpkey.jar"?
>>
>> I have the signed apk's, the keystore used to sign them, .pem files which
>> have all the pub keys in them and a p12 and p8 file.
>>
>> Which one should I use?
>>
>> --
>> Respectfully,
>>
>> William C Roberts
>>
>>
>>
>


-- 
Respectfully,

William C Roberts

[-- Attachment #2: Type: text/html, Size: 1678 bytes --]

Re: signature clause in mac_permisions

[Joshua Brindle]

If you want to go straight from cert to hex encoding without having to 
sign an app (i.e., you are generating certs and policies at the same 
time) you can use this:

$openssl x509 -inform PEM -in <certname>.x509.pem -outform DER

Script to encode:

#!/usr/bin/env python

import sys
content = sys.stdin.read().strip()
foo = content.encode("hex")
sys.stdout.write(foo)


The script to encode has to be very careful about padding or null 
terminating, hence why I couldn't just use some random command line tool.

William Roberts wrote:
> I should have RTFM, it is right on the wiki under install time mac
> http://selinuxproject.org/page/SEAndroid
>
>
>
> On Mon, Sep 17, 2012 at 4:22 PM, Robert Craig <robertpcraig@gmail.com
> <mailto:robertpcraig@gmail.com>> wrote:
>
>     Just run the setool host tool. To build just 'make setool' and then
>     to run just 'setool'. The help usage statement will guide you.
>
>
>     On Mon, Sep 17, 2012 at 2:34 PM, William Roberts
>     <bill.c.roberts@gmail.com <mailto:bill.c.roberts@gmail.com>> wrote:
>
>         How did you guys generate the hex encoded x509 string for a
>         signature clause in mac_permissions.xml?
>
>         Did you use the Android "dumpkey.jar"?
>
>         I have the signed apk's, the keystore used to sign them, .pem
>         files which have all the pub keys in them and a p12 and p8 file.
>
>         Which one should I use?
>
>         --
>         Respectfully,
>
>         William C Roberts
>
>
>
>
>
>
> --
> Respectfully,
>
> William C Roberts
>
>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

Re: signature clause in mac_permisions

[William Roberts]

[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]

Thanks,
I was playing with opensll myself but couldn't come up with he correct
commandline foo for it.
Bill

On Tue, Sep 18, 2012 at 10:01 AM, Joshua Brindle <method@manicmethod.com>wrote:

> If you want to go straight from cert to hex encoding without having to
> sign an app (i.e., you are generating certs and policies at the same time)
> you can use this:
>
> $openssl x509 -inform PEM -in <certname>.x509.pem -outform DER
>
> Script to encode:
>
> #!/usr/bin/env python
>
> import sys
> content = sys.stdin.read().strip()
> foo = content.encode("hex")
> sys.stdout.write(foo)
>
>
> The script to encode has to be very careful about padding or null
> terminating, hence why I couldn't just use some random command line tool.
>
> William Roberts wrote:
>
>> I should have RTFM, it is right on the wiki under install time mac
>> http://selinuxproject.org/**page/SEAndroid<http://selinuxproject.org/page/SEAndroid>
>>
>>
>>
>> On Mon, Sep 17, 2012 at 4:22 PM, Robert Craig <robertpcraig@gmail.com
>> <mailto:robertpcraig@gmail.com**>> wrote:
>>
>>     Just run the setool host tool. To build just 'make setool' and then
>>     to run just 'setool'. The help usage statement will guide you.
>>
>>
>>     On Mon, Sep 17, 2012 at 2:34 PM, William Roberts
>>     <bill.c.roberts@gmail.com <mailto:bill.c.roberts@gmail.**com<bill.c.roberts@gmail.com>>>
>> wrote:
>>
>>         How did you guys generate the hex encoded x509 string for a
>>         signature clause in mac_permissions.xml?
>>
>>         Did you use the Android "dumpkey.jar"?
>>
>>         I have the signed apk's, the keystore used to sign them, .pem
>>         files which have all the pub keys in them and a p12 and p8 file.
>>
>>         Which one should I use?
>>
>>         --
>>         Respectfully,
>>
>>         William C Roberts
>>
>>
>>
>>
>>
>>
>> --
>> Respectfully,
>>
>> William C Roberts
>>
>>
>>


-- 
Respectfully,

William C Roberts

[-- Attachment #2: Type: text/html, Size: 2912 bytes --]