Actions
Task #3582
closedMicro forwarder: Sign the Chrome extension
Start date:
04/01/2016
Due date:
% Done:
100%
Estimated time:
Description
When the extension is stable enough, should sign the Chrome extension and include it in the NDN-JS repository. I (Jeff T) don't know much about signing Chrome extensions, so if this could be assigned to someone else that would be great. Some info on packaging Chrome extensions is here:
Updated by Anonymous over 8 years ago
- Blocked by Task #3579: Micro forwarder: Status page to show faces and FIB added
Updated by Anonymous over 8 years ago
- Blocked by Task #3580: Micro forwarder: Button to register a route added
Updated by Wentao Shang over 8 years ago
I can help with signing the extension for Chrome.
Updated by Wentao Shang over 8 years ago
- Assignee set to Wentao Shang
Packing and signing the extension is easy. The only question is the management of the signing key: it is generated then first time we sign the package; and we need that to update the extension package or upload the package to Chrome Web Store. Where should I put the pem private key?
Updated by Anonymous over 8 years ago
You can keep the key. If we need to change it later, I'm sure we can.
Updated by Wentao Shang over 8 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Signed Chrome extension package was commited.
Actions