[
https://issues.apache.org/jira/browse/GEODE-8070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17102043#comment-17102043
]
Bruce J Schuchardt commented on GEODE-8070:
-------------------------------------------
I tried this implementation where we use the default context if "any" is
specified and it didn't like us trying to add our own key manager and trust
manager to the context:
{noformat}
java.security.KeyManagementException: Default SSLContext is initialized
automatically
at
sun.security.ssl.SSLContextImpl$DefaultSSLContext.engineInit(SSLContextImpl.java:931)
at javax.net.ssl.SSLContext.init(SSLContext.java:282)
at
org.apache.geode.internal.net.SocketCreator.createAndConfigureSSLContext(SocketCreator.java:274)
at
org.apache.geode.internal.net.SocketCreator.initialize(SocketCreator.java:225)
{noformat}
I think we need to be able to do that.
> rework handling of "any" in SSLUtils
> ------------------------------------
>
> Key: GEODE-8070
> URL: https://issues.apache.org/jira/browse/GEODE-8070
> Project: Geode
> Issue Type: Bug
> Components: membership
> Reporter: Bruce J Schuchardt
> Priority: Major
>
> SSLUtil has a list of "known" TLS protocols. It should support TLSv1.3.
>
> {noformat}
> // lookup known algorithms
> String[] knownAlgorithms = {"SSL", "SSLv2", "SSLv3", "TLS", "TLSv1",
> "TLSv1.1", "TLSv1.2"};
> for (String algo : knownAlgorithms) {
> try {
> sslContext = SSLContext.getInstance(algo);
> break;
> } catch (NoSuchAlgorithmException e) {
> // continue
> }
> } {noformat}
> We probably can't fully test this change since not all JDKs we test with
> support v1.3 at this time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
