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

Revocation of asymmetric master key and symmetric vault keys #39

Closed
robert-cronin opened this issue Jun 4, 2020 · 3 comments
Closed
Assignees
Labels
research Requires research

Comments

@robert-cronin
Copy link
Contributor

We need to start thinking about revocation. Particularly revocation of a vault key and how we would propagate it through a PolyKey network.

It will be less common to revoke the master key of a particular keynode and that keynode would become untrustworthy from that point on. This might happen if a user has many sub-keynodes and one of them becomes compromised.

@robert-cronin robert-cronin added the research Requires research label Jun 4, 2020
@robert-cronin robert-cronin self-assigned this Jun 4, 2020
@robert-cronin
Copy link
Contributor Author

Revocation of vault key is a non-issue because it is never shared, the vaults are shared over a secure wire with transport layer security and then re-encrypted on the other end with that keynodes own derived sym key.

@CMCDragonkai
Copy link
Member

I think this issue can be changed to be about key-rollover. As in rekeying a vault or the master key. This can be done interactively.

@robert-cronin
Copy link
Contributor Author

Closing on account of migration to gitlab

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

No branches or pull requests

2 participants