You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Igor Sapego (Jira)" <ji...@apache.org> on 2022/01/16 23:35:00 UTC

[jira] [Commented] (IGNITE-15337) Thin client using TLS 1.3 may freeze on connection to server

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

Igor Sapego commented on IGNITE-15337:
--------------------------------------

The issue was reproduced by adding delays in specific places and stopped appearing with this fix. Still, I'm not sure how to implement a proper test for this case.

> Thin client using TLS 1.3 may freeze on connection to server
> ------------------------------------------------------------
>
>                 Key: IGNITE-15337
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15337
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Ivan Daschinsky
>            Assignee: Igor Sapego
>            Priority: Major
>         Attachments: debug_ssl.patch, odbc-trace.log, python_tls_1_3.patch, test.log
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
>  ODBC ssl tests randomly (ubuntu 20.04) or constantly (win 10) fails on openssl 1.1.1k with failed handshake. 
> On openssl without tls 1.3 support all works flawlessly.
> WA: disable TLS 1.3 on ignite side 
> {code}
> -Djdk.tls.server.protocols=TLSv1.2
> {code}
> It will be also great to implement an ability to set TLS version on C++,  nowadays default one is choosen. 



--
This message was sent by Atlassian Jira
(v8.20.1#820001)