ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaliy Biryukov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11298) TcpCommunicationSpi does not support TLSv1.3
Date Thu, 23 May 2019 20:54:00 GMT

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

Vitaliy Biryukov commented on IGNITE-11298:
-------------------------------------------

[~ilyak], Yes, I'll try to fix it by the end of this week. 

> 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)

Mime
View raw message