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.

Sign up for GitHub

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

Jump to bottom

Keymanager: Final steps for policy support #1846

Closed
5 of 9 tasks
Yawning opened this issue Jun 25, 2019 · 2 comments
Closed
5 of 9 tasks

Keymanager: Final steps for policy support #1846

Yawning opened this issue Jun 25, 2019 · 2 comments
Assignees
@Yawning
Labels
c:key management Category: key management c:security Category: security sensitive epic Epic (costed tracking issue) p:1 Priority: core feature

Comments

@Yawning
Copy link
Contributor

Yawning commented Jun 25, 2019 •
edited
Loading

TODO: split into sub-issues

Things that didn't get done as part of #1824...

  • Write a policy signing tool.
  • Reinitialize the enclave more often (keymanager/worker: Be better about re-initializing the enclave state #1812).
  • Figure out how we are going to pass each enclave all of the currently valid MRENCLAVE/MRSIGNER pairs.
  • Figure out how to test/deploy this.
    • Need a mock MRSIGNER/MRENCLAVE for non-sgx enclave builds.
    • Need test threshold-multisig keys.
    • Need to change lots of devops.

Lower priority (can be delayed till we stop doing dump/restore on update):

  • Add key manager policy document submission/validation to the BFT app.
  • Figure out how the BFT app is supposed to validate policy signatures.

Estimated cost: > 14 days (Realistically, no idea, depends on what the new deployment process looks like.)
@Yawning Yawning added p:1 Priority: core feature c:key management Category: key management c:security Category: security sensitive labels Jun 25, 2019
@Yawning Yawning mentioned this issue Jun 25, 2019
Merged
15 tasks
@ravenac95
Copy link
Contributor

Which parts of this, if any, are required before a Testnet deployment?

@kostko kostko added the epic Epic (costed tracking issue) label Jul 30, 2019
@matevz matevz mentioned this issue Sep 5, 2019
Merged
@kostko kostko mentioned this issue Jan 6, 2020
Closed
@Yawning
Copy link
Contributor Author

Yawning commented Jun 10, 2021

This is basically done, and has been done for a long time.

@Yawning Yawning closed this as completed Jun 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Yawning Yawning

Labels
c:key management Category: key management c:security Category: security sensitive epic Epic (costed tracking issue) p:1 Priority: core feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@matevz @kostko @ravenac95 @Yawning