[
https://issues.apache.org/jira/browse/CASSCPP-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bret McGuire updated CASSCPP-16:
--------------------------------
Fix Version/s: 2.17.2
(was: 2.18.0)
> Revisit support for TLS 1.3
> ---------------------------
>
> Key: CASSCPP-16
> URL: https://issues.apache.org/jira/browse/CASSCPP-16
> Project: Apache Cassandra C/C++ driver
> Issue Type: Improvement
> Components: Core
> Reporter: Bret McGuire
> Priority: Normal
> Fix For: 2.17.2
>
> Attachments: client.cpp
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> 2.17.1 caps the supported TLS version at 1.2 rather than 1.3 (see
> [here|https://github.com/apache/cassandra-cpp-driver/blob/2.17.1/src/ssl/ssl_openssl_impl.cpp#L541-L544]).
> This was apparently a consequence of work done on
> [CPP-786|https://datastax-oss.atlassian.net/browse/CPP-786] and
> [CPP-922|https://datastax-oss.atlassian.net/browse/CPP-922]. The trail seems
> to indicate that the problem was that a recent Ubuntu release had broken
> mockssandra.
> Good news is that a lot has changed since then. It's worthwhile taking
> another look at this to see if we're still stuck. Apache Cassandra 5.0.x has
> introduced explicit support for TLS 1.3 so we should be able to test directly
> in integration tests rather than rely on mockssandra.
> This issue was prompted by a series of question raised by Chintan Pansuriya
> in [a
> question|https://lists.apache.org/thread/66scpszqprgn9v16ronfflnlx731hkk0]
> sent to dev@.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
