we_are_coded.by CODE · The world, decoded
БГ

Cloudflare · Builders

Cloudflare: post-quantum Privacy Pass and the cost of 2,420 bytes

Privacy Pass protects sites from abuse, but it stands on classical cryptography: a quantum attacker will be able to forge tokens at will. Post-quantum signatures are 2,420 bytes against 64, and MOLE hides who issued the token too.

Source
Cloudflare
Published
The event
Checked on
Responsible editor
Cvetelin Ivanov
How we work
MethodCorrections

You get a token that cannot be linked back to you. Then you hand it over and you are in. That is Privacy Pass, and Cloudflare uses it to protect applications from abuse. No single client can eat everyone's resources. Until now the choice was between friction and lost privacy: CAPTCHA, accounts, fingerprinting. Privacy Pass removes that choice.

Fact

The facts: on 6 November 2026 Cloudflare published a look at the post-quantum future of Privacy Pass. Privacy Pass is a protocol used by site operators like Cloudflare to help protect applications from abuse. It still relies on classical cryptography like RSA and elliptic curves, and according to Cloudflare a quantum attacker will be able to forge tokens at will and use them to bypass whatever security mechanism the site operator wants to implement, such as rate limiting. On the other side, Privacy Pass is unconditionally private: no attacker, quantum or not, can link the redemption of a token to its issuance. The company says it has 10 years of deployment experience with it, including for privacy proxies like iCloud Private Relay and relays like Privacy Gateway. ML-DSA-44 signatures are 2,420 bytes, while ECDSA-P256 signatures are just 64 bytes. The new thing Cloudflare describes is called MOLE, short for Moderation Of unLinkable Endorsements. An endorsement is issued by an anchor and redeemed by a moderator. The goal is for the token to hide the identity of the issuer altogether, so that tokens cannot be treated differently based on who issued them.

The number that says it all is 2,420 against 64. The post-quantum signature is nearly 38 times larger than the classical one. That is not something a setting patches. Systems get re-engineered to bear the cost.

The token hides who you are. MOLE hides who gave it to you.

Why this matters to a builder. Until now the verifier had to know the issuer's public key, and so necessarily learned the identity of the issuer. For some cases that is exactly what you want: the issuer tells you what kind of client is connecting. For others it is more than you need. It is enough that the token came from someone you trust.

Cloudflare does not hide that the work is ongoing. It says it is in better shape than one might think, and that the new capabilities will be built so the same guarantee holds even after Q-day. When MOLE enters real use and with exactly what parameters, the text does not say.

Nothing breaks today. Tokens work and no one can link them back to you. The bill comes later, and Cloudflare is already writing it.

The visual is generated code-art, no third-party images.