Skip to content
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.

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

Remove default TLS 1.0/1.1 support #83249

Closed
tylersmalley opened this issue Nov 12, 2020 · 3 comments · Fixed by #90511
Closed

Remove default TLS 1.0/1.1 support #83249

tylersmalley opened this issue Nov 12, 2020 · 3 comments · Fixed by #90511
Labels
Breaking Change discuss Team:Operations Team label for Operations Team Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Comments

@tylersmalley
Copy link
Contributor

As part of the Node 12.0 upgrade, we are specifying --tls-min-v1.0 to maintain backward compatibility for any user relying on TLS 1.0. or 1.1.

Elasticsearch dropped TLS 1.0 by default in 7.0. It would be good to understand if we can or should make the breaking change to drop TLS 1.0 or 1.1 by default in 8.0.

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@tylersmalley tylersmalley changed the title Remove TLS 1.0/1.1 support Remove default TLS 1.0/1.1 support Nov 12, 2020
@tylersmalley tylersmalley added the Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! label Nov 12, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@legrego
Copy link
Member

legrego commented Nov 12, 2020

I think this is something we should absolutely do for 8.0.

ESS has dropped support altogether for all inbound connections, so making this change within Kibana would make us consistent with our hosted offering by default.

My feeling is that if ESS can drop support at that scale altogether, then we can safely remove these as defaults in 8.0. On-prem administrators can always opt back in if they really need to support a legacy client.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Breaking Change discuss Team:Operations Team label for Operations Team Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants