[ https://issues.apache.org/jira/browse/THRIFT-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13956088#comment-13956088 ]
Hudson commented on THRIFT-2258: -------------------------------- FAILURE: Integrated in Thrift #1105 (See [https://builds.apache.org/job/Thrift/1105/]) THRIFT-2258:Add TLS v1.1/1.2 support to TSSLSocket.cpp (jfarrell: rev 02c95c1c4008e72592251c85f8ce68b8b09ad77f) * lib/cpp/src/thrift/transport/TSSLSocket.h * lib/cpp/src/thrift/transport/TSSLSocket.cpp > Add TLS v1.1/1.2 support to TSSLSocket.cpp > ------------------------------------------ > > Key: THRIFT-2258 > URL: https://issues.apache.org/jira/browse/THRIFT-2258 > Project: Thrift > Issue Type: Improvement > Components: C++ - Library > Affects Versions: 0.9.1 > Reporter: Chris Stylianou > Assignee: Chris Stylianou > Labels: c++, ssl, thrift, tls > Fix For: 0.9.2 > > Attachments: thrift-2258.patch, updated-thrift-2258.patch > > > At the moment TSSLSocket.cpp hard-codes the SSL/TLS protocol to TLSv1.0, > which does not allow any other protocols to be used instead (SSL v3, TLS > v1.0, v1.1, v1.2, *ignores SSLv2 as horribly insecure*). > Could a method be provided on the TSSLSocketFactory to set the required > protocol (like how there is already a cipher() function available), so that > when SSL_CTX_new, it is called with the specified SSL/TLS protocol. > Sorry to label this as a bug, but being unable to select the highest availabe > security protocol for communication is a bug in my eyes. -- This message was sent by Atlassian JIRA (v6.2#6252)