Skip to content

[CF1] clarify cipher suite usage in Cloudflare Tunnel TLS connections #25994

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Oct 29, 2025
+2 −2
Merged

[CF1] clarify cipher suite usage in Cloudflare Tunnel TLS connections #25994

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6612f4e
[CF1] clarify cipher suite usage in Cloudflare Tunnel TLS connections
deadlypants1973 Oct 22, 2025
3687130
Update src/content/docs/cloudflare-one/networks/connectors/cloudflare…
deadlypants1973 Oct 22, 2025
d13c13a
Removing noTLSVerify explanation since it's irrelevant to cipher suites
nikitacano Oct 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...e-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cipher-suites.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,9 @@ pcx_content_type: reference
title: Cipher suites
---

Cloudflare Tunnel connections use the cipher suites supported by `cloudflared`, which relies on the Go TLS library for its TLS implementation. When establishing a TLS connection to your origin, `cloudflared` will negotiate the most secure cipher suite supported by both sides.
Cloudflare Tunnel connections use the cipher suites supported by `cloudflared`, which relies on the Go TLS library for its TLS implementation. These cipher suites apply to both the TLS connection between Cloudflare's network and `cloudflared`, and the HTTPS connection between `cloudflared` and your origin, even when [`noTLSVerify`](/cloudflare-one/networks/connectors/cloudflare-tunnel/configure-tunnels/cloudflared-parameters/origin-parameters/#notlsverify) is set to `false`. In both cases, `cloudflared` negotiates the most secure cipher suite supported by both sides.
Copy link
Contributor

@nikitacano nikitacano Oct 22, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about "even when noTLSVerify" wording.


The following table lists the cipher suites supported by cloudflared:
The following table lists the cipher suites supported by `cloudflared`:

| Protocol support | Cipher suites |
|------------------|----------------|
Expand Down
Loading