Skip to content

Commit 3e160b6

Browse files
Fix TLS 1.3 hex values in supported-cipher-suites table
1 parent d312efa commit 3e160b6

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

src/content/docs/ssl/edge-certificates/additional-options/cipher-suites/supported-cipher-suites.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -33,13 +33,13 @@ Cloudflare supports the following cipher suites by default. If needed, you can [
3333
| AES256-SHA256 | TLS 1.2 | Legacy | \[0x3d] | TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA256 |
3434
| AES256-SHA | TLS 1.0 | Legacy | \[0x35] | TLS\_RSA\_WITH\_AES\_256\_CBC\_SHA |
3535
| DES-CBC3-SHA | TLS 1.0 | Legacy | \[0x0a] | TLS\_RSA\_WITH\_3DES\_EDE\_CBC\_SHA |
36-
| AEAD-AES128-GCM-SHA256 \* | TLS 1.3 | Modern | {0x13,0x01} | TLS\_AES\_128\_GCM\_SHA256 |
37-
| AEAD-AES256-GCM-SHA384 \* | TLS 1.3 | Modern | {0x13,0x02} | TLS\_AES\_256\_GCM\_SHA384 |
38-
| AEAD-CHACHA20-POLY1305-SHA256 \* | TLS 1.3 | Modern | {0x13,0x03} | TLS\_CHACHA20\_POLY1305\_SHA256 |
36+
| AEAD-AES128-GCM-SHA256 \* | TLS 1.3 | Modern | \{0x13,0x01} | TLS\_AES\_128\_GCM\_SHA256 |
37+
| AEAD-AES256-GCM-SHA384 \* | TLS 1.3 | Modern | \{0x13,0x02} | TLS\_AES\_256\_GCM\_SHA384 |
38+
| AEAD-CHACHA20-POLY1305-SHA256 \* | TLS 1.3 | Modern | \{0x13,0x03} | TLS\_CHACHA20\_POLY1305\_SHA256 |
3939

4040
:::note[* TLS 1.3 minimum protocol]
4141

4242
Ciphers `AEAD-AES128-GCM-SHA256`, `AEAD-AES256-GCM-SHA384`, and `AEAD-CHACHA20-POLY1305-SHA256` are automatically supported by your zone if you [enable TLS 1.3](/ssl/edge-certificates/additional-options/tls-13/#enable-tls-13).
4343

44-
TLS 1.3 uses the same cipher suite space as previous versions of TLS, but defines these cipher suites differently. TLS 1.3 only specifies the symmetric ciphers and cannot be used for TLS 1.2. Similarly, TLS 1.2 and lower cipher suites cannot be used with TLS 1.3 (IETF TLS 1.3 draft 21). BoringSSL also hard-codes cipher preferences in this order for TLS 1.3.
44+
TLS 1.3 uses the same cipher suite space as previous versions of TLS, but defines these cipher suites differently. TLS 1.3 only specifies the symmetric ciphers and cannot be used for TLS 1.2. Similarly, TLS 1.2 and lower cipher suites cannot be used with TLS 1.3 (IETF TLS 1.3 draft 21). BoringSSL also hard-codes cipher preferences in this order for TLS 1.3.
4545
:::

0 commit comments

Comments
 (0)