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

Murray's exception rationale #497

Merged
merged 1 commit into from
Oct 3, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions draft-ietf-privacypass-protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -508,7 +508,10 @@ ensure that the truncated form of new key IDs do not collide with other
truncated key IDs in rotation. Collisions can cause the Issuer to use
the wrong Issuer Private Key for issuance, which will in turn cause the
resulting tokens to be invalid. There is no known security consequence of
using the the wrong Issuer Private Key.
using the the wrong Issuer Private Key. A possible exception to this constraint
would be a colliding key that is still in use but in the process of being
rotated out, in which case the collision cannot reasonably be avoided but it
is expected to be transient.

# Issuance Protocol for Publicly Verifiable Tokens {#public-flow}

Expand Down Expand Up @@ -741,7 +744,10 @@ ensure that the truncated form of new key IDs do not collide with other
truncated key IDs in rotation. Collisions can cause the Issuer to use
the wrong Issuer Private Key for issuance, which will in turn cause the
resulting tokens to be invalid. There is no known security consequence of
using the the wrong Issuer Private Key.
using the the wrong Issuer Private Key. A possible exception to this constraint
would be a colliding key that is still in use but in the process of being
rotated out, in which case the collision cannot reasonably be avoided but it
is expected to be transient.

# Security considerations {#security}

Expand Down