Privacy Pass

Protocolo de Identidade

A privacy-preserving authorization protocol that lets a client prove it has passed some check, such as solving a challenge or being a legitimate user of a device, without being tracked across requests. A server issues tokens that are cryptographically blinded, so that when a token is later redeemed the issuer cannot link it to the issuance. It is now an IETF standards-track family: RFC 9576 describes the architecture, RFC 9577 the HTTP authentication scheme, and RFC 9578 the issuance protocols (published June 2024). The original deployment was a browser extension that let people skip CAPTCHA challenges at sites behind Cloudflare .

Padrão Aberto
Links
Visitar Website Ver esta ferramenta no grafo Sugerir uma correção

Detalhes

Licença Open source: the original extension and server code are on the project's GitHub pages; the standards are IETF RFCs. https://github.com/privacypass; https://github.com/ietf-wg-privacypass/base-drafts
Status de Dev 🟢 Ativo
Proprietário IETF Privacy Pass Working Group (standards); the RFC authors include people from Cloudflare, Fastly, Apple, Brave Software and NOVA LINCS (Universidade NOVA de Lisboa)
Órgão de Governança IETF Privacy Pass Working Group (Internet Engineering Task Force)
Órgão de Governança - Lista
  • Internet Engineering Task Force
País International (IETF working group; authors across several organisations and countries)
Ano de Início 2017
Stack Verifiable, oblivious pseudorandom functions (VOPRFs) over elliptic curves in the original protocol; the standardised issuance protocols (RFC 9578) define two token types, VOPRF (P-384, SHA-384) and Blind RSA (2048-bit); HTTP authentication scheme
Financiamento Not stated by the project.
Última Investigação 29 de out. de 2026

Visão de topologia

Esta ferramenta no centro e o que se relaciona diretamente com ela. Cada linha nomeia o tipo de relação.

Visão de topologia: Privacy PassEsta ferramenta no centro e o que se relaciona diretamente com ela. Cada linha nomeia o tipo de relação.PrivacyPassInternet Engineering Task Force (Hospedado em, Padronizado em, Administrado por)InternetEngineering…
  • Internet Engineering Task Force (Organização): Hospedado em, Padronizado em, Administrado por

Abrir no Explorador de grafo

Domínios de Caso de Uso

Identidade e Confiança

Capacidades

Prova de humanidade Divulgação contextual

Protocolo de Identidade Atributos

Origens Reduce the burden of internet challenges (CAPTCHAs) for users, especially those on shared or anonymising networks, by letting them redeem blindly signed tokens anonymously; standardised through the IETF to support wider use cases such as device attestation
Banco de Dados N/A
Linguagem de Consulta N/A
Formatos de Dados Tokens carried in an HTTP Authorization header with its own authentication scheme; token challenge and token structures defined in RFC 9577; issuance request and response structures in RFC 9578
Suporte Móvel Via platform implementations that adopted the standard (the cited sources name no specific mobile client beyond the protocol authors' employers)
Suporte Web Yes: browser extension and an HTTP authentication scheme
Aplicativos Nativos Library and platform-level; the browser extension is the project's own client
Termos Free and open: IETF RFCs and open-source reference code
Fundos Not stated by the project.
Baseado Em VOPRFs and blind RSA signatures; the RFCs reference the original Privacy Pass work and related IETF cryptographic standards
Órgão de Governança - Lista
  • Internet Engineering Task Force
Permissões Origins choose which issuers to trust; clients choose which tokens to present
Autenticação e Identidade No identity is revealed: a token proves only that the issuer's checks were passed; issuers and attesters decide what that means
Modelo de Armazenamento Clients store unspent tokens locally; issuers and origins keep spent-token state to prevent reuse
Interoperabilidade A common HTTP scheme and issuance protocols let any compliant client, attester, issuer and origin interoperate
Portabilidade de Dados Tokens are bearer instruments held by the client and redeemable at any origin that accepts that issuer; they are not portable between issuers
Governança e Tomada de Decisão IETF working-group consensus process, with the architecture, authentication scheme and issuance protocols as separate documents
Maturidade / Padronização do Protocolo IETF standards track: RFC 9577 and RFC 9578 are Standards Track and RFC 9576 is Informational, all published June 2024
Padrões de Identidade IETF RFCs 9576, 9577 and 9578; not a W3C DID or Verifiable Credentials scheme
Métodos DID Suportados N/A
Gestão de Chaves The issuer holds a signing key and publishes the public key; clients hold unspent tokens; the architecture discusses key rotation and issuer directories
Tipos de Credenciais Anonymous bearer tokens bound to a challenge; not identity credentials
Método de Verificação The origin verifies the token against the issuer's public key and rejects reuse
Recursos de Privacidade Unlinkability between issuance and redemption through blinding; the architecture discusses the remaining risks (for example from small anonymity sets and colluding parties)
Métodos de Autenticação Blind-signed tokens redeemed over an HTTP Authorization header
Mecanismo de Revogação Not a revocation model: tokens are single-use and expire by issuer key rotation
Tipos de Agentes Suportados Clients (people and devices), attesters, issuers and origins
Tipos de Carteira/Cliente Browsers and other HTTP clients; the original extension
Mecanismos de Recuperação N/A: tokens are disposable
Conformidade / Regulamentações Not stated by the project.
Protocolos de Troca de Credenciais HTTP authentication scheme for redemption (RFC 9577) and issuance protocols (RFC 9578)
Estrutura de Confiança Trust in issuers and attesters chosen by the origin; the architecture requires them to be separable to protect privacy
Modelo de Custo Free to use; costs fall on the issuer and attester
Resistência à Censura Low to moderate: issuance depends on issuers that a few large operators run today

Relacionamentos

Como esta ferramenta se conecta a outras ferramentas e organizações, a partir de relacionamentos revisados pelo responsável pelos dados do OpenHaven. Descrevem como os projetos se conectam, não a qualidade deles.

Administrado por
  • Internet Engineering Task Force
Hospedado em
  • Internet Engineering Task Force
Padronizado em
  • Internet Engineering Task Force