-
Notifications
You must be signed in to change notification settings - Fork 812
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
Cassandra: Fix TLS host verification #2109
Cassandra: Fix TLS host verification #2109
Conversation
Do you think implementing and testing the above cases would be sufficient? I am a little bit concerned about the possibility of unknowingly breaking existing setups... |
Refs #2007 Signed-off-by: Joshua Mühlfort <[email protected]>
Signed-off-by: Joshua Mühlfort <[email protected]>
I just rebased and squashed the previous commits to fewer ones and removed the draft status from the PR. Please note the updated PR description. I hadn't the time to test all cases but can't think of a way this code could break these untested cases. Would you like to wait for implementation of #2137 or review this PR right away? Are there some other things to consider? |
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.
Thanks for working on it! LGTM. I just left a minor comment.
Signed-off-by: Joshua Mühlfort <[email protected]>
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.
Thank you for your contribution! Please take a look at comments I've left.
Signed-off-by: Joshua Mühlfort [email protected]
What this PR does:
Enable TLS host verification for the cassandra storage backend while handling other setups as well.
Which issue(s) this PR fixes:
Fixes #2007
Refs #2013
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
Cases to cover
According to my understanding, the following case will not work with the current gocql API design: