-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
6 changed files
with
61 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
--- | ||
title: "RFC 9578: Privacy Pass Issuance Protocols" | ||
year: 2024 | ||
location: Internet Research Task Force (IRTF). 2024. | ||
authors: | ||
- Sofía Celi | ||
- alex-davidson | ||
- Steven Valdez | ||
- christopher-wood | ||
url: https://datatracker.ietf.org/doc/rfc9578/ | ||
related_interests: | ||
- cryptography | ||
- protocols | ||
--- | ||
|
||
This document specifies two variants of the two-message issuance protocol for Privacy Pass tokens: one that produces tokens that are privately verifiable using the Issuer Private Key and one that produces tokens that are publicly verifiable using the Issuer Public Key. Instances of "issuance protocol" and "issuance protocols" in the text of this document are used interchangeably to refer to the two variants of the Privacy Pass issuance protocol. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
--- | ||
title: "RFC 9576: The Privacy Pass Architecture" | ||
year: 2024 | ||
location: Internet Research Task Force (IRTF). 2024. | ||
authors: | ||
- alex-davidson | ||
- Jana Iyengar | ||
- christopher-wood | ||
url: https://datatracker.ietf.org/doc/rfc9576/ | ||
related_interests: | ||
- privacy | ||
- cryptography | ||
- protocols | ||
--- | ||
|
||
This document specifies the Privacy Pass architecture and requirements for its constituent protocols used for authorization based on privacy-preserving authentication mechanisms. It describes the conceptual model of Privacy Pass and its protocols, its security and privacy goals, practical deployment models, and recommendations for each deployment model, to help ensure that the desired security and privacy goals are fulfilled. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
--- | ||
title: "RFC 9577: The Privacy Pass HTTP Authentication Scheme" | ||
year: 2024 | ||
location: Internet Research Task Force (IRTF). 2024. | ||
authors: | ||
- Tommy Pauly | ||
- Steven Valdez | ||
- christopher-wood | ||
url: https://datatracker.ietf.org/doc/rfc9577/ | ||
related_interests: | ||
- privacy | ||
- cryptography | ||
- protocols | ||
--- | ||
|
||
This document defines an HTTP authentication scheme for Privacy Pass, a privacy-preserving authentication mechanism used for authorization. | ||
|
||
The authentication scheme specified in this document can be used by Clients to redeem Privacy Pass tokens with an Origin. It can also be used by Origins to challenge Clients to present Privacy Pass tokens. |