You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ilya Kasnacheev (JIRA)" <ji...@apache.org> on 2019/05/22 10:00:10 UTC

[jira] [Commented] (IGNITE-11298) TcpCommunicationSpi does not support TLSv1.3

    [ https://issues.apache.org/jira/browse/IGNITE-11298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845736#comment-16845736 ] 

Ilya Kasnacheev commented on IGNITE-11298:
------------------------------------------

[~VitaliyB] do you have plans to continue work on this issue?

> 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
>          Time Spent: 10m
>  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
(v7.6.3#76005)