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

Challenges don't need to be unique #462

Merged
merged 1 commit into from
Sep 5, 2023
Merged

Challenges don't need to be unique #462

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 1 addition & 2 deletions draft-ietf-privacypass-auth-scheme.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,8 +214,7 @@ value. This document follows the default padding behavior described in
As an Authentication Parameter (`auth-param` from {{!RFC9110, Section 11.2}}),
the value can be either a token or a quoted-string, and might be required to
be a quoted-string if the base64url string includes "=" characters. This
challenge value MUST be unique for every 401 HTTP response to prevent replay
attacks. This parameter is required for all challenges.
parameter is required for all challenges.

- "token-key", which contains a base64url encoding of the public key for
use with the issuance protocol indicated by the challenge. See {{ISSUANCE}}
Expand Down