Confirmed users
19
edits
Talk:Extension Manager:Addon Update Security: Difference between revisions
Jump to navigation
Jump to search
Talk:Extension Manager:Addon Update Security (view source)
Revision as of 09:43, 15 September 2007
, 15 September 2007PHP implementation
(→Update Scenarios: XPI signing) |
The RedBurn (talk | contribs) (PHP implementation) |
||
| Line 55: | Line 55: | ||
# Provide updateHash for each xpi in updates.rdf (that has been signed by your private key). | # Provide updateHash for each xpi in updates.rdf (that has been signed by your private key). | ||
--[[User:Silfreed|Silfreed]] 19:36, 16 July 2007 (PDT) | --[[User:Silfreed|Silfreed]] 19:36, 16 July 2007 (PDT) | ||
== PHP implementation == | |||
Will there be a PHP implementation of the tool (used to hash the xpi, add it to the update.rdf file and sign it) ?<br /> | |||
I'm part of an extensions translation team, who hosts some of our translations on our site (I'm not talking about BabelZilla, which is used when the extension author collaborates). If each of us has to use the xulrunner tool to make the updates work, we'll have to create a private key and make it public so every translators can upload their translations. Of course, this is insecure, but it's the only way to avoid breaking extension updates (translator change, key lost...).<br /> | |||
A PHP implementation would make it easier for us and would increase the security of the updates. [[User:The RedBurn|The RedBurn]] 02:43, 15 September 2007 (PDT) | |||