874
edits
Labs/Jetpack/Reboot/JEP/106: Difference between revisions
added a strawman proposal.
(added more stuff) |
(added a strawman proposal.) |
||
| Line 8: | Line 8: | ||
=== | === Problem Statement === | ||
Every file in a Jetpack package needs a unique identifier for a variety of reasons: | Every file in a Jetpack package needs a unique identifier for a variety of reasons: | ||
| Line 25: | Line 25: | ||
* The host environment needs a way of telling that one Jetpack is an upgrade for another, while guaranteeing that the upgrade isn't a forgery. | * The host environment needs a way of telling that one Jetpack is an upgrade for another, while guaranteeing that the upgrade isn't a forgery. | ||
=== Proposal === | |||
Jetpacks are accessible through the <tt>jetpack:</tt> protocol. Each Jetpack has a keypair associated with it, and a Jetpack's ID is the SHA-1 hash of its public key. Jetpacks must be signed using their private key, and will not be loaded unless signed; thus a Jetpack ID, if present in the system, is guaranteed to be unforgeable. | |||
=== Key Issues === | === Key Issues === | ||
| Line 40: | Line 44: | ||
=== Internal Methods === | === Internal Methods === | ||
=== API Methods === | === API Methods === | ||