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
Section 4.3.1 of the CONIKS paper and section 5 of the CONIKS 2.0 report describes a mechanism for making name-to-key mappings in the server private. This is mostly to protect the visibility of public keys via encryption, but could potentially be extended to hiding usernames as well. Only a whitelisted group of users could then access the private mappings. Implementing this requires a whitelisting protocol as well as a corresponding verification protocol.
The text was updated successfully, but these errors were encountered:
Section 4.3.1 of the CONIKS paper and section 5 of the CONIKS 2.0 report describes a mechanism for making name-to-key mappings in the server private. This is mostly to protect the visibility of public keys via encryption, but could potentially be extended to hiding usernames as well. Only a whitelisted group of users could then access the private mappings. Implementing this requires a whitelisting protocol as well as a corresponding verification protocol.
The text was updated successfully, but these errors were encountered: