[
https://issues.apache.org/jira/browse/IGNITE-11298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17401660#comment-17401660
]
Ivan Daschinsky edited comment on IGNITE-11298 at 8/19/21, 12:10 PM:
---------------------------------------------------------------------
[~ilyak] Do you have more info about handling NewSessionTicket? We observe the
same issue with openssl 1.1.1f on C++ or python
[IGNITE-15337|https://issues.apache.org/jira/browse/IGNITE-15337]
was (Author: ivandasch):
[~ilyak] Do you have more info about this ticket? We observe the same issue
with openssl 1.1.1f on C++ or python
[IGNITE-15337|https://issues.apache.org/jira/browse/IGNITE-15337]
> TcpCommunicationSpi does not support TLSv1.3
> --------------------------------------------
>
> Key: IGNITE-11298
> URL: https://issues.apache.org/jira/browse/IGNITE-11298
> Project: Ignite
> Issue Type: Bug
> Components: general
> Affects Versions: 2.7
> Reporter: Ilya Kasnacheev
> Assignee: Vitaliy Biryukov
> Priority: Major
> Labels: Java11
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> When started on Java 11 we cannot form a secure cluster - Discovery will
> happily use the default TLSv1.3 but Communication will fail with its custom
> SSLEngine-using code.
> Need to fix that.
> Until that, nodes may be salvaged by setProtocol("TLSv1.2") on
> SslContextFactory, or by system property -Djdk.tls.client.protocols="TLSv1.2"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
