Micro forwarder: Sign the Chrome extension
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 Wentao Shang almost 5 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?