Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

key rotation and revocation #5

Open
urbien opened this issue Sep 23, 2020 · 0 comments
Open

key rotation and revocation #5

urbien opened this issue Sep 23, 2020 · 0 comments

Comments

@urbien
Copy link
Member

urbien commented Sep 23, 2020

Problem

Hypercore has an associated static Public / Private key pair. Private keys should never migrate between devices for security. When device is replaced, new keypair is created. Need

Proposed solution

  1. Use Hypercore-multi-key module which allows to switch this Hypercore to a new keypair. We need to add code to sign the new key with the old one to establish safe handoff.

  2. We need to verify this signature on receiving nodes so that they can prove to themselves the legality of key rotation. Perhaps this can be added as a hypercore extension?

  3. After key is rotated, old key is revoked.

Not covered by this issue

Key loss and recovery schemes. This will be addressed by another issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant