change(https-tls): RFC 10015 retires RSA and FFDHE key exchange in TLS 1.2 - #150
Draft
jdevalk wants to merge 1 commit into
Draft
change(https-tls): RFC 10015 retires RSA and FFDHE key exchange in TLS 1.2#150jdevalk wants to merge 1 commit into
jdevalk wants to merge 1 commit into
Conversation
…S 1.2 RFC 10015 (July 2026) makes RSA key exchange, static FFDH and ephemeral FFDHE a MUST NOT in (D)TLS 1.2, and static ECDH a SHOULD NOT. It updates 17 RFCs including 5246 and the TLS BCP 9325. The page asked for 'forward-secret cipher suites only (ECDHE)', which lands in the right place for the wrong reason: DHE is forward-secret and is now disallowed anyway. Says ECDHE specifically now, and explains the gap between the two rules. Swapped the Qualys SSL Labs entry out of sources for the RFC; it is still linked inline under Verification.
Deploying specification-website with
|
| Latest commit: |
8d4307b
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://5fe025e2.specification-website.pages.dev |
| Branch Preview URL: | https://change-tls12-key-exchange-20.specification-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
src/content/spec/security/https-tls.md:DHEor RSA suites in a TLS 1.2 config written before July 2026.updatedbumped; changelog entry added (changed).Why now
RFC 10015 — Deprecating Obsolete Key Exchange Methods in TLS 1.2 and DTLS 1.2, Standards Track, July 2026 (https://www.rfc-editor.org/rfc/rfc10015.html). It updates 17 RFCs, including RFC 5246 (TLS 1.2 itself) and RFC 9325 (the TLS BCP), and is normative:
DHE) — MUST NOT offer / MUST NOT selectThe
DHEline is the reason this is worth a page edit rather than a citation bump. The page's existing advice — forward-secret suites only — arrives at roughly the right configuration by a rule that is now wrong:DHEis forward-secret and is disallowed regardless. Anyone who wrote their TLS 1.2 config against "forward secrecy" and has not revisited it since is out of step with a Standards Track RFC, and the page was telling them they were fine.This is the misconception-naming rule from CLAUDE.md applied to a rule we ourselves were stating imprecisely.
Status
Unchanged at
required. HTTPS was already required; this sharpens how, not whether.Sources
sources, to stop the list growing further past the 2–4 guidance. It is unchanged as an inline link under Verification, which is where a testing tool belongs.Not done here
RFC 9852 ("New Protocols Using TLS Must Require TLS 1.3", July 2026) also landed this window. It binds people designing new protocols, not people configuring a website, so it does not earn a mention on this page.
🤖 Generated with Claude Code