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

WebSocketClient.upgradeSocketToSSL is enforcing TLS 1.2 #1382

Closed
pavel-treutner opened this issue Jan 4, 2024 · 3 comments · Fixed by #1387
Closed

WebSocketClient.upgradeSocketToSSL is enforcing TLS 1.2 #1382

pavel-treutner opened this issue Jan 4, 2024 · 3 comments · Fixed by #1387

Comments

@pavel-treutner
Copy link

Describe the bug
Is there any reason for enforcing TLS 1.2 in WebSocketClient.upgradeSocketToSSL()? Replacing SSLContext.getInstance("TLSv1.2") with SSLSocketFactory.getDefault() would honor the well-known property jdk.tls.client.protocols allowing unified configuration.

Environment(please complete the following information):

  • Version used: 1.5.5
@marci4
Copy link
Collaborator

marci4 commented Jan 15, 2024

Hey,
I changed this like 6 years ago
4094e3d#diff-86950b5c3b9c35d3dbd2c1b6ecdeb1e23fa5bd0b20adeb05d54ac4b94080ff6a

Sonarqube reported it as an error.
But I do not recall it any more.

If this is an issue for you, feel free to open a pull request.

Best regards,
Marcel

@pavel-treutner
Copy link
Author

Probably because TLS v1.2 was disabled in early Java 7 versions. This was a common workaround. Not needed any longer. Java 7 has reached EOL and recent JREs have sensible defaults (TLS 1.2 and 1.3): #1387

@marci4
Copy link
Collaborator

marci4 commented Jan 16, 2024

We do have to keep the android world in mind here.
The play store still supports KitKat which does not have any support for java 7 apis (e.g. see #1209)

@marci4 marci4 added this to the Release 1.5.6 milestone Jan 18, 2024
@marci4 marci4 added the Bug label Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants