--- title: Post-quantum authentication to origins is now supported description: Cloudflare has added post-quantum (PQ) authentication support to its Authenticated Origin Pulls (AOP) and Custom Origin Trust Store (COTS) products, using... canonical: https://daily.dev/posts/post-quantum-authentication-to-origins-is-now-supported-ch7qnx5uf twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Post-quantum authentication to origins is now supported | daily.dev og:description: Cloudflare has added post-quantum (PQ) authentication support to its Authenticated Origin Pulls (AOP) and Custom Origin Trust Store (COTS) products, using... og:url: https://daily.dev/posts/post-quantum-authentication-to-origins-is-now-supported-ch7qnx5uf og:image: https://api.daily.dev/og/posts/ch7QNX5uF.png og:image:alt: Post-quantum authentication to origins is now supported og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Post-quantum authentication to origins is now supported **[Cloudflare](https://daily.dev/sources/cloudflare)** · 13 min read · 1 upvotes · 0 comments ## Summary Cloudflare has added post-quantum (PQ) authentication support to its Authenticated Origin Pulls (AOP) and Custom Origin Trust Store (COTS) products, using ML-DSA (Module-Lattice-Based Digital Signature Algorithm) signatures. This enables fully post-quantum secure mutual TLS connections between Cloudflare and customer origin servers. The post covers configuration steps using OpenSSL 3.5+, including generating ML-DSA certificate chains, uploading them via the Cloudflare API, and configuring NGINX. Engineering details include how Go's lack of native ML-DSA support required using Cloudflare's CIRCL library (until Go 1.27 ships in August 2026), and how updating BoringSSL after a four-year lag caused a brief incident due to stricter KeyUsage enforcement. The post also explains downgrade attack risks and how to avoid them, and situates this milestone within Cloudflare's broader roadmap targeting full post-quantum security by 2029. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I enable post-quantum authentication for Cloudflare's connection to my origin server? Enable it through Cloudflare's Authenticated Origin Pulls (AOP) and Custom Origin Trust Store (COTS) products, which now support ML-DSA signatures under FIPS 204. Generate ML-DSA certificate chains with OpenSSL 3.5.0 or later using the seed-only key format, upload the origin CA to COTS and the client certificate to AOP via the Cloudflare API, then set SSL/TLS mode to Full (strict) and configure NGINX to present and verify the certificates. _Teams rolling out post-quantum TLS to origins can track real configuration steps like this via daily.dev._ ### Which ML-DSA parameter set does Cloudflare recommend for post-quantum origin authentication? ML-DSA-44 is recommended for most applications since it is the most performant of the three FIPS 204 parameter sets (ML-DSA-44, ML-DSA-65, ML-DSA-87) while still attaining a comfortable NIST security category 2 strength. All three are supported by Cloudflare's Custom Origin Trust Store and Authenticated Origin Pulls products. _Engineers weighing ML-DSA parameter tradeoffs can follow post-quantum cryptography guidance on daily.dev._ ### Why did Cloudflare's BoringSSL update cause an outage in June 2026? Cloudflare had delayed updating Pingora Origin's BoringSSL dependency for four years, maintaining an internal fork instead, until post-quantum authentication support landed in BoringSSL in April 2026 prompted the upgrade. A commit within those four years of changes enforced stricter KeyUsage rules in TLS certificates per RFC 5280, causing a small number of customers' technically non-compliant RSA certificates to be rejected, triggering an incident on June 10, 2026 that was rolled back and later patched to retain support for those certificates. _Anyone managing long-deferred TLS library upgrades can learn from incidents like this via daily.dev._ ## Similar posts on daily.dev - [1.1.1.1 now supports post-quantum DNSSEC, all 2,420 bytes of it](https://daily.dev/posts/1-1-1-1-now-supports-post-quantum-dnssec-all-2-420-bytes-of-it-c7xuhmdzz) · Cloudflare · 3 upvotes · 0 comments - [Who Goes There? Post-Quantum Authentication – IPsec Series, Part 6](https://daily.dev/posts/who-goes-there-post-quantum-authentication-ipsec-series-part-6-iskqiozsb) · Cisco · 0 upvotes · 0 comments - [Cloudflare Measures Origin TLS Preferences, Cutting Handshake Retries from 52% to 3.7%](https://daily.dev/posts/cloudflare-measures-origin-tls-preferences-cutting-handshake-retries-from-52-to-3-7--imenahndh) · InfoQ · 0 upvotes · 0 comments - [The State of Post-Quantum Cryptography](https://daily.dev/posts/the-state-of-post-quantum-cryptography-hjfyungt7) · Feisty Duck · 0 upvotes · 0 comments --- Tags: [#quantum-computing](https://daily.dev/tags/quantum-computing), [#cloudflare](https://daily.dev/tags/cloudflare) [View this post on daily.dev](https://daily.dev/posts/post-quantum-authentication-to-origins-is-now-supported-ch7qnx5uf) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Post-quantum authentication to origins is now supported","url":"https://daily.dev/posts/post-quantum-authentication-to-origins-is-now-supported-ch7qnx5uf","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/post-quantum-authentication-to-origins-is-now-supported-ch7qnx5uf"},"datePublished":"2026-07-29T13:11:21.620Z","dateModified":"2026-09-14T09:18:25.772Z","description":"Cloudflare has added post-quantum (PQ) authentication support to its Authenticated Origin Pulls (AOP) and Custom Origin Trust Store (COTS) products, using...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e9603ae44d8d1f7426faebfd5bf09719?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/e9603ae44d8d1f7426faebfd5bf09719?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Cloudflare","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Cloudflare","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/38522e1d11354cd6b7af66f9d4316735","url":"https://daily.dev/sources/cloudflare"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/post-quantum-authentication-to-origins-is-now-supported-ch7qnx5uf","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"quantum-computing,cloudflare","timeRequired":"PT13M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Cloudflare","item":"https://daily.dev/sources/cloudflare"},{"@type":"ListItem","position":3,"name":"Post-quantum authentication to origins is now supported"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/post-quantum-authentication-to-origins-is-now-supported-ch7qnx5uf#faq","mainEntity":[{"@type":"Question","name":"How do I enable post-quantum authentication for Cloudflare's connection to my origin server?","acceptedAnswer":{"@type":"Answer","text":"Enable it through Cloudflare's Authenticated Origin Pulls (AOP) and Custom Origin Trust Store (COTS) products, which now support ML-DSA signatures under FIPS 204. Generate ML-DSA certificate chains with OpenSSL 3.5.0 or later using the seed-only key format, upload the origin CA to COTS and the client certificate to AOP via the Cloudflare API, then set SSL/TLS mode to Full (strict) and configure NGINX to present and verify the certificates. Teams rolling out post-quantum TLS to origins can track real configuration steps like this via daily.dev."}},{"@type":"Question","name":"Which ML-DSA parameter set does Cloudflare recommend for post-quantum origin authentication?","acceptedAnswer":{"@type":"Answer","text":"ML-DSA-44 is recommended for most applications since it is the most performant of the three FIPS 204 parameter sets (ML-DSA-44, ML-DSA-65, ML-DSA-87) while still attaining a comfortable NIST security category 2 strength. All three are supported by Cloudflare's Custom Origin Trust Store and Authenticated Origin Pulls products. Engineers weighing ML-DSA parameter tradeoffs can follow post-quantum cryptography guidance on daily.dev."}},{"@type":"Question","name":"Why did Cloudflare's BoringSSL update cause an outage in June 2026?","acceptedAnswer":{"@type":"Answer","text":"Cloudflare had delayed updating Pingora Origin's BoringSSL dependency for four years, maintaining an internal fork instead, until post-quantum authentication support landed in BoringSSL in April 2026 prompted the upgrade. A commit within those four years of changes enforced stricter KeyUsage rules in TLS certificates per RFC 5280, causing a small number of customers' technically non-compliant RSA certificates to be rejected, triggering an incident on June 10, 2026 that was rolled back and later patched to retain support for those certificates. Anyone managing long-deferred TLS library upgrades can learn from incidents like this via daily.dev."}}]} ```