Project

General

Profile

Actions

Task #3582

closed

Micro forwarder: Sign the Chrome extension

Added by Anonymous almost 8 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
Normal
Assignee:
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:

https://developer.chrome.com/extensions/packaging


Related issues 2 (0 open2 closed)

Blocked by NDN in the browser - Task #3579: Micro forwarder: Status page to show faces and FIBClosedWentao Shang04/01/2016

Actions
Blocked by NDN in the browser - Task #3580: Micro forwarder: Button to register a routeClosed04/01/2016

Actions
Actions #1

Updated by Anonymous almost 8 years ago

  • Blocked by Task #3579: Micro forwarder: Status page to show faces and FIB added
Actions #2

Updated by Anonymous almost 8 years ago

  • Blocked by Task #3580: Micro forwarder: Button to register a route added
Actions #3

Updated by Wentao Shang almost 8 years ago

I can help with signing the extension for Chrome.

Actions #4

Updated by Wentao Shang almost 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?

Actions #5

Updated by Anonymous almost 8 years ago

You can keep the key. If we need to change it later, I'm sure we can.

Actions #6

Updated by Wentao Shang almost 8 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Signed Chrome extension package was commited.

Actions

Also available in: Atom PDF