OOB + signature
rogeliomita at activitycentral.com
Wed Feb 13 08:00:04 EST 2013
2013/2/8 Rogelio Mita <rogeliomita at activitycentral.com>
> Thanks a lot Martín!.
> Perfect the answer!, then... we understand that the contents manifest file
> that is the result of build (ussualy .toc, that is used to update method,
> olpc-update) will also be affected by this process, is this right?.
> Because we no found place to verify this assertion in some documentation,
> only the specification of contents manifest, but found nothing about it,
> only the following lines that do not answer to our question:
> A contents manifest is just a convenience object for bundling a number of
>> related directory objects; it should not be directly signed. Instead, the
>> root directory object in the contents manifest should be the element which
>> receives a signature.
> Thanks again!
2013/2/8 Martin Langhoff <martin.langhoff at gmail.com>
>> On Thu, Feb 7, 2013 at 9:45 AM, Rafael Ortiz <rafael at activitycentral.com>
>> > and how its resulting files are signed (for instance the content
>> > file, specifically for the upgrade files), OOB uses some method when the
>> > signature module is activated ?, you have to sing them in an special
>> If you have the signing keys in the build machine, it's really easy.
>> Set the .ini file to use the signing modules, tell it where the keys
>> are, and it'll do it automagically for you.
>> Any suggestions on this =) ? Thanks!
> See in OOB sources, modules/signing/README. Skip the "external signing"
>> martin.langhoff at gmail.com
>> martin at laptop.org -- Software Architect - OLPC
>> - ask interesting questions
>> - don't get distracted with shiny stuff - working code first
>> - http://wiki.laptop.org/go/User:Martinlanghoff
> Activity Central <http://activitycentral.com/>
Activity Central <http://activitycentral.com/>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel