Skip to content

Commit e979a46

Browse files
ranbelsdnts
authored andcommitted
post-quantum flag (cloudflare#22764)
1 parent 4dd2aa9 commit e979a46

File tree

1 file changed

+11
-0
lines changed
  • src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/cloudflared-parameters

1 file changed

+11
-0
lines changed

src/content/docs/cloudflare-one/connections/connect-networks/configure-tunnels/cloudflared-parameters/run-parameters.mdx

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -123,6 +123,17 @@ Specifies the [account certificate](/cloudflare-one/connections/connect-networks
123123

124124
Writes the application's process identifier (PID) to this file after the first successful connection. Mainly useful for scripting and service integration.
125125

126+
## `post-quantum`
127+
128+
| Syntax | Environment Variable |
129+
| -------------------------------------------------------- | -------------------- |
130+
| `cloudflared tunnel run --post-quantum <UUID or NAME>` | `TUNNEL_POST_QUANTUM`|
131+
132+
133+
By default, Cloudflare Tunnel connections over [`quic`](#protocol) are encrypted using [post-quantum cryptography (PQC)](/ssl/post-quantum-cryptography/) but will fall back to non-PQ if there are issues connecting. If the `--post-quantum` flag is provided, `quic` connections are only allowed to use PQ key agreements, with no fallback to non-PQ.
134+
135+
Post-quantum key agreements are not supported when using `http2` protocol.
136+
126137
## `protocol`
127138

128139
| Syntax | Default | Environment Variable |

0 commit comments

Comments
 (0)