Remove TLSv1.1 from default protocols#121731
Merged
tvernum merged 9 commits intoelastic:mainfrom Feb 10, 2025
Merged
Conversation
This commit removes "TLSv1.1" from the list of default protocols in
Elasticsearch (starting with ES9.0)
TLSv1.1 has been deprecated by the IETF since March 2021
This affects a variety of TLS contexts, include
- The HTTP Server (Rest API)
- Transport protocol (including CCS and CCR)
- Outgoing connections for features that have configurable SSL
settings. This includes
- reindex
- watcher
- security realms (SAML, OIDC, LDAP, etc)
- monitoring exporters
- inference services
In practice, however, TLSv1.1 has been disabled in most Elasticsearch
deployments since around 7.12 because most JDK releases have disabled
TLSv1.1 (by default) starting in April 2021
That is, if you run a default installation of Elasticsearch (for any
currently supported version of ES) that uses the bundled JVM then
TLSv1.1 is already disabled.
And, since ES9+ requires JDK21+, all supported JDKs ship with TLSv1.1
disabled by default.
In addition, incoming HTTP connections to Elastic Cloud deployments
have required TLSv1.2 or higher since April 2020
This change simply makes it clear that Elasticsearch does not
attempt to enable TLSv1.1 and administrators who wish to use that
protocol will need to explicitly enable it in both the JVM and in
Elasticsearch.
Resolves: elastic#108057
Collaborator
|
Pinging @elastic/es-security (Team:Security) |
Collaborator
|
Hi @tvernum, I've created a changelog YAML for you. Note that since this PR is labelled |
Contributor
Author
|
I haven't included any docs change here due to the docs freeze. I'll open a draft PR with the proposed changes so that we can be ready to port it to the new docs system. |
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this pull request
Feb 5, 2025
Collaborator
|
Hi @tvernum, I've updated the changelog YAML for you. Note that since this PR is labelled |
Collaborator
|
Hi @tvernum, I've updated the changelog YAML for you. Note that since this PR is labelled |
Collaborator
💚 Backport successful
|
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this pull request
Feb 10, 2025
This commit removes "TLSv1.1" from the list of default protocols in
Elasticsearch (starting with ES9.0)
TLSv1.1 has been deprecated by the IETF since March 2021
This affects a variety of TLS contexts, include
- The HTTP Server (Rest API)
- Transport protocol (including CCS and CCR)
- Outgoing connections for features that have configurable SSL
settings. This includes
- reindex
- watcher
- security realms (SAML, OIDC, LDAP, etc)
- monitoring exporters
- inference services
In practice, however, TLSv1.1 has been disabled in most Elasticsearch
deployments since around 7.12 because most JDK releases have disabled
TLSv1.1 (by default) starting in April 2021
That is, if you run a default installation of Elasticsearch (for any
currently supported version of ES) that uses the bundled JVM then
TLSv1.1 is already disabled.
And, since ES9+ requires JDK21+, all supported JDKs ship with TLSv1.1
disabled by default.
In addition, incoming HTTP connections to Elastic Cloud deployments
have required TLSv1.2 or higher since April 2020
This change simply makes it clear that Elasticsearch does not
attempt to enable TLSv1.1 and administrators who wish to use that
protocol will need to explicitly enable it in both the JVM and in
Elasticsearch.
Resolves: elastic#108057
elasticsearchmachine
pushed a commit
that referenced
this pull request
Feb 10, 2025
This commit removes "TLSv1.1" from the list of default protocols in
Elasticsearch (starting with ES9.0)
TLSv1.1 has been deprecated by the IETF since March 2021
This affects a variety of TLS contexts, include
- The HTTP Server (Rest API)
- Transport protocol (including CCS and CCR)
- Outgoing connections for features that have configurable SSL
settings. This includes
- reindex
- watcher
- security realms (SAML, OIDC, LDAP, etc)
- monitoring exporters
- inference services
In practice, however, TLSv1.1 has been disabled in most Elasticsearch
deployments since around 7.12 because most JDK releases have disabled
TLSv1.1 (by default) starting in April 2021
That is, if you run a default installation of Elasticsearch (for any
currently supported version of ES) that uses the bundled JVM then
TLSv1.1 is already disabled.
And, since ES9+ requires JDK21+, all supported JDKs ship with TLSv1.1
disabled by default.
In addition, incoming HTTP connections to Elastic Cloud deployments
have required TLSv1.2 or higher since April 2020
This change simply makes it clear that Elasticsearch does not
attempt to enable TLSv1.1 and administrators who wish to use that
protocol will need to explicitly enable it in both the JVM and in
Elasticsearch.
Resolves: #108057
Member
|
@tvernum is this PR relevant to the serverless changelog? [FYI this question is based on 9.0 breaking changes] |
Contributor
Author
|
Thanks for the reminder, @leemthompo It is not relevant to Serverless, but I had opened #121732 to draft the docs changes, but never got it converted to the new docs system. |
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this pull request
Apr 16, 2025
In ES9 and later, we do not enable TLSv1.1 by default, even if the JDK supports it. This updates the docs accordingly. Relates: elastic#121731
tvernum
added a commit
that referenced
this pull request
Apr 17, 2025
In ES9 and later, we do not enable TLSv1.1 by default, even if the JDK supports it. This updates the docs accordingly. Relates: #121731
tvernum
added a commit
to tvernum/elasticsearch
that referenced
this pull request
Apr 17, 2025
In ES9 and later, we do not enable TLSv1.1 by default, even if the JDK supports it. This updates the docs accordingly. Relates: elastic#121731
elasticsearchmachine
pushed a commit
that referenced
this pull request
Apr 17, 2025
leemthompo
added a commit
to elastic/docs-content
that referenced
this pull request
Apr 22, 2025
Elasticsearch 9.0 and later require JDK21 This changes the docs regarding TLS versions to reflect the behaviour on modern JDKs. Relates: - elastic/elasticsearch#121731 - elastic/elasticsearch#121732 Co-authored-by: Liam Thompson <32779855+leemthompo@users.noreply.github.com>
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
4 participants
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.
This commit removes "TLSv1.1" from the list of default protocols in Elasticsearch (starting with ES9.0)
TLSv1.1 has been deprecated by the IETF since March 2021
This affects a variety of TLS contexts, include
In practice, however, TLSv1.1 has been disabled in most Elasticsearch deployments since around 7.12 because most JDK releases have disabled TLSv1.1 (by default) starting in April 2021
That is, if you run a default installation of Elasticsearch (for any currently supported version of ES) that uses the bundled JVM then TLSv1.1 is already disabled.
And, since ES9+ requires JDK21+, all supported JDKs ship with TLSv1.1 disabled by default.
In addition, incoming HTTP connections to Elastic Cloud deployments have required TLSv1.2 or higher since April 2020
This change simply makes it clear that Elasticsearch does not attempt to enable TLSv1.1 and administrators who wish to use that protocol will need to explicitly enable it in both the JVM and in Elasticsearch.
Resolves: #108057