Remove the TDSENCRYPTION Guard Clause #20743
Open
+0
−12
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that #18745 is closed, this guard clause is no longer required. TDSENCRYPTION is compatible with sessions now, so we should allow users to configure it.
I should have included this change in #20677 but I didn't run into it because I was focused on the issue that'd occur when TDSENCRYPTION was false but the server required it.
Verification
List the steps needed to make sure this thing works
msfconsoleuse auxiliary/scanner/mssql/mssql_loginTDSENCRYPTIONandCreateSessionto true