Add /brokenmarriage flag to prevent CANONICALIZE when using opsec #212
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
Contributor
|
Not sure if it's really worth adding another parameter to the gazillion that are already there. By requesting no canonicalization, you've already wandered off what a genuine LSASS login request looks like anyway. Windows always requests canonicalization. |
Author
|
Doesn't matter what Windows does, matters what the EDR tooling actually checks :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Flag could also be renamed to
/nocanonicalizeor something generic.This allows a Kerberos ticket to be created with most of the OPSEC features, but still perform the BM attack.