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

Fixed key model #12

Open
martinthomson opened this issue Aug 16, 2021 · 1 comment
Open

Fixed key model #12

martinthomson opened this issue Aug 16, 2021 · 1 comment

Comments

@martinthomson
Copy link
Collaborator

The fixed key model is not as crazy as the draft makes out. It only requires that the systems for updating the thing that contains the key (such as an endpoint software release) has adequate update mechanisms.

I would then observe that this means that the update mechanism has a dependency on KCCS also. That is, you need to ensure that everyone gets the same update.

Therefore, I might recast this text as saying that: a fixed key either doesn't work, or shifts the KCCS problem to another component in the system.
@chris-wood
Copy link
Collaborator

Therefore, I might recast this text as saying that: a fixed key either doesn't work, or shifts the KCCS problem to another component in the system.

👍

martinthomson added a commit to martinthomson/key-consistency that referenced this issue Jun 27, 2022
@martinthomson
(K)CCS applies to software and configurations too
0bd60d9 
An attempt at addressing the fundamental problem with choosing a fixed
key.

Closes ietf-wg-privacypass#12.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@martinthomson @chris-wood