-
Notifications
You must be signed in to change notification settings - Fork 32
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
SSL
configuration option enables SSL handshaking regardless of the configuration value
#240
Comments
mp911de
added
type: bug
Something isn't working
and removed
status: waiting-for-triage
An issue we've not yet triaged
labels
Jan 11, 2022
This is a bug in We need to fix this. |
mp911de
changed the title
If "io.netty:netty-tcnative-boringssl-static" in class path, then SSL handshaking is always enabled
Jan 11, 2022
SSL
configuration option enables SSL handshaking regardless of the configuration value
mp911de
added a commit
that referenced
this issue
Jan 11, 2022
We now enable full SSL only when the SSL configuration option is set to true. Previously, SSL was enabled once the SSL option was present regardless of its value. [fixes #240] Signed-off-by: Mark Paluch <mpaluch@vmware.com>
@mp911de Thanks a lot for the fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Versions
Current Behavior
As long as the dependency "io.netty:netty-tcnative-boringssl-static:2.0.40.final" exists in class path, then R2DBC always tries to handshaking with MSSQL with SSLv3, then protocol not supported exception pops up.
Steps to reproduce
Input Code
Expected behavior/code
Set ConnectionFactoryOptions.SSL to false should disable SSL handshaking, even with dependency "io.netty:netty-tcnative-boringssl-static" exists in class path
The text was updated successfully, but these errors were encountered: