You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: