8,288
edits
Changes
Jump to navigation
Jump to search
mLine 1:
Line 1: − + + + Line 16:
Line 18: − + − + Line 27:
Line 29: − + − + Line 41:
Line 43: − − [[Category:Feature Page Incomplete]] − [[Category:Feature]]
Features/Signed Bundles (view source)
Revision as of 01:36, 18 October 2009
, 01:36, 18 October 2009no edit summary
<noinclude>{{GoogleTrans-en}}{{TOCright}}</noinclude>
<noinclude>{{GoogleTrans-en}}{{TOCright}}
[[Category:Feature Page Incomplete]]
[[Category:Feature|Signed Bundles]]</noinclude>
== Summary ==
== Summary ==
== Benefit to Sugar ==
== Benefit to Sugar ==
Signed bundles would allow deployments to ensure that bundles were created by
Signed bundles would allow deployments to guarantee that bundles were created by the holder of specific key.
== Scope ==
== Scope ==
The signing tools are available at http://dev.laptop.org/git/projects/olpc-contents/
The signing tools are available at http://dev.laptop.org/git/projects/olpc-contents/
Support for parsing the format, maintaining "root keys", and displaying the keys via some user interface would need to be implemented into Sugar.
Support for parsing the format, maintaining "root keys", and displaying the keys via some user interface would need to be implemented in Sugar.
== How To Test ==
== How To Test ==
== User Experience ==
== User Experience ==
This needs to be fleshed out. But, when a bundle is signed the user would likely see some information in the Journal indicating who signed it.
This needs to be fleshed out. But, when a bundle is signed, the user would likely see some information in the Journal indicating who signed it.
== Dependencies ==
== Dependencies ==
== Contingency Plan ==
== Contingency Plan ==
We could switch from .xo to .rpm or another format with built in support for signing.
We could switch from .xo to .rpm or another format with built-in support for signing.
== Documentation ==
== Documentation ==
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]
* See [[{{TALKPAGENAME}}|discussion tab for this feature]]
----
----
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''
''You can add categories to tie features back to real deployments/schools requesting them, for example <nowiki>[[</nowiki>Category:Features requested by School Xyz]]''