-
Notifications
You must be signed in to change notification settings - Fork 456
CDRIVER-6045 Support TLS v1.3 in Secure Channel #2118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This reverts commit 9c62ea9.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with minor comments. Suggested adding a test in Evergreen to add some CI coverage for TLS v1.3 to Atlas, but that may be better done later since it needs renegotiation implemented to pass.
src/libmongoc/src/mongoc/mongoc-stream-tls-secure-channel-private.h
Outdated
Show resolved
Hide resolved
|
||
DWORD enabled_protocols = SP_PROT_TLS1_1_CLIENT | SP_PROT_TLS1_2_CLIENT; | ||
|
||
/* TLS 1.3 is supported on Windows Server 2022 and newer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Evergreen tasks do not appear to test TLS 1.3 against cloud-dev (even when enabled). I expect that is why when TLS 1.3 was enabled without renegotiation, Evergreen still passed.
The authentication-tests-winssl task that tests connecting to cloud-dev here
Suggest (either here or in later PR) adding an Evergreen task to test cloud-dev with TLS 1.3. I expect that would mean:
- Copy the VS 2017 variant to test VS 2022. Limit it to testing
".authentication-tests .winssl"
. - Regenerate the Evergreen config (see docs)
Summary
Enable TLS 1.3 in the C driver when using Windows Secure Channel as the TLS implementation (default on Windows).
Changes
Used libcurl as a reference.
(In a second PR)
Secure Channel with TLS 1.3 may use the renegotiate status for internal use; instructions on how to handle this are given in Windows documentation.