Hi Team,
I'm evaluating TLS 1.3 support in "cassandra-cpp-driver" and noticed that the
current implementation appears to cap the maximum TLS version at TLS 1.2
("SSL_CTX_set_max_proto_version(..., TLS1_2_VERSION)").
>From the commit history and JIRA references, it looks like TLS 1.3 support was
>previously addressed under CPP-786, but later restricted in CPP-922 due to
>handshake issues. I couldn't find any follow-up changes in the 2.16.x or
>2.17.x releases that revisit this limitation.
Could you please provide some guidance on the following?
1. Is there any active work, planned release, or proposal to re-enable TLS
1.3 support?
2. Is there a tentative target version or timeframe for this work, if
planned?
3. Is the handshake issue that led to the TLS 1.2 restriction still known to
affect current OpenSSL versions (3.x), or was it specific to older OpenSSL
releases?
4. For users who require TLS 1.3 today, is there a recommended workaround or
supported approach?
Environment
* Cassandra C++ Driver: 2.17.1
* OpenSSL: 3.5.6
If this inquiry would be better addressed elsewhere, please let me know the
appropriate mailing list, forum, or issue-tracking process, or feel free to
forward it to the relevant maintainers.
Thanks for your time and for maintaining the driver. Any insight into the
current status or roadmap for TLS 1.3 support would be greatly appreciated.
Thanks,
Chintan Pansuriya
The information contained in this communication from the sender is
confidential. It is intended solely for use by the recipient and others
authorized to receive it. If you are not the recipient, you are hereby notified
that any disclosure, copying, distribution or taking action in relation of the
contents of this information is strictly prohibited and may be unlawful. The
information contained in this communication from the sender is confidential. It
is intended solely for use by the recipient and others authorized to receive
it. If you are not the recipient, you are hereby notified that any disclosure,
copying, distribution or taking action in relation of the contents of this
information is strictly prohibited and may be unlawful.
