Skip to content

Commit 769a0df

Browse files
Fill in Cf to origin and review titles and headings
1 parent 501a6d5 commit 769a0df

File tree

3 files changed

+15
-13
lines changed

3 files changed

+15
-13
lines changed

src/content/docs/ssl/post-quantum-cryptography/index.mdx

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,12 +10,12 @@ head: []
1010
description: Get an overview of how Cloudflare is implementing post-quantum cryptography to protect you against store now, decrypt later.
1111
---
1212

13-
For years, Cloudflare has been researching and [writing about post quantum](https://blog.cloudflare.com/tag/post-quantum/).
13+
For years, Cloudflare has been researching and [writing about post-quantum](https://blog.cloudflare.com/tag/post-quantum/).
1414

15-
To protect you against the risk of [store now, decrypt later](https://en.wikipedia.org/wiki/Harvest_now,_decrypt_later), and considering all the [connections](#three-connections-in-the-life-of-a-request) that take place when your website or application is on Cloudflare, we have deployed and are actively expanding the use of post-quantum hybrid key agreement.
15+
To protect you against the risk of [store now, decrypt later](https://en.wikipedia.org/wiki/Harvest_now,_decrypt_later), and considering all the [connections](#three-connections-in-the-life-of-a-request) that take place when your website or application is on Cloudflare, we have deployed and are actively expanding the use of [post-quantum hybrid key agreement](#hybrid-key-agreement).
1616

1717
:::caution[TLS 1.3]
18-
Post-quantum key agreements are only supported in protocols based on TLS 1.3 (including HTTP/3) and are disabled for websites in [FIPS mode](/cloudflare-one/policies/gateway/http-policies/tls-decryption/#fips-compliance).
18+
Cloudflare post-quantum key agreements are only supported in protocols based on TLS 1.3 (including HTTP/3) and are disabled for websites in [FIPS mode](/cloudflare-one/policies/gateway/http-policies/tls-decryption/#fips-compliance).
1919
:::
2020

2121
## Three building blocks of TLS
@@ -41,7 +41,7 @@ Cloudflare has deployed the following hybrid key agreements:
4141
- [X25519Kyber768Draft00](https://datatracker.ietf.org/doc/draft-tls-westerbaan-xyber768d00/) (Obsolete)
4242
- TLS identifier: `0x6399`
4343

44-
A hybrid key agreement lays the groundwork as more and more [clients](#visitor-to-cloudflare) adopt post-quantum cryptography, while also maintaining the current security provided by X25519. It is a safer path in case of an unexpected breakthrough that renders all variants of ML-KEM insecure.
44+
A hybrid key agreement lays the groundwork as more and more [clients](#1-visitor-to-cloudflare) adopt post-quantum cryptography, while also maintaining the current security provided by X25519. It is a safer path in case of an unexpected breakthrough that renders all variants of ML-KEM insecure.
4545

4646
## Three connections in the life of a request
4747

@@ -73,3 +73,6 @@ As announced in [September 2023](https://blog.cloudflare.com/post-quantum-crypto
7373

7474
### 3. Cloudflare to your origin
7575

76+
Finally, Cloudflare also supports [hybrid key agreements](#hybrid-key-agreement) when connecting to origins. In this case, post-quantum secured connections will depend on the origin servers also supporting PQC.
77+
78+
Refer to [Post-quantum cryptography between Cloudflare and origin servers](/ssl/post-quantum-cryptography/pqc-to-origin/) for details.

src/content/docs/ssl/post-quantum-cryptography/pqc-support.mdx

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,22 +2,20 @@
22
pcx_content_type: reference
33
title: PQC support
44
sidebar:
5-
order: 3
5+
order: 2
66
head: []
77
description: Consider information about post-quantum cryptography at Cloudflare - deployed key agreements and software support.
88
---
99

10-
Cloudflare's deployment of post-quantum hybrid key agreements is supported by the following [third-parties](#software-support) and is in use within the following [Cloudflare products](#cloudflare-products).
10+
Cloudflare's deployment of post-quantum hybrid key agreements is supported by different software as listed below.
1111

12-
## Software support
13-
14-
### X25519MLKEM768
12+
## X25519MLKEM768
1513
- Default for [Firefox 132+](https://www.mozilla.org/firefox/channel/desktop/) (Beta)
1614
- Default for [Chrome 131+](https://www.google.com/chrome/beta/) (Beta)
1715
- Cloudflare's [fork of Go](https://github.com/cloudflare/go)
1816
- [BoringSSL](https://boringssl.googlesource.com/boringssl/)
1917

20-
### X25519Kyber768Draft00
18+
## X25519Kyber768Draft00
2119

2220
- Default for [Chrome 124-130](https://www.google.com/chrome/) on Desktop
2321
- For older Chrome or on mobile, toggle _TLS 1.3 hybridized Kyber support_ (`enable-tls13-kyber`) in `chrome://flags`.
Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,10 @@
11
---
22
pcx_content_type: how-to
3-
title: Enable PQC to your origin
3+
title: Post-quantum between Cloudflare and origin servers
44
sidebar:
5-
order: 2
5+
order: 3
66
label: PQC to your origin
77
head: []
88
description: Learn how to enable post-quantum cryptography in connections from Cloudflare to your origin servers.
9-
---
9+
---
10+

0 commit comments

Comments
 (0)