enumuser salt extraction #35
Open
Conversation
This file contains 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
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.
I'm sure there are a few ways to do this, but this was my dirty first attempt to get it working. Essentially Kerberos AES salts used for AS-REQs are case sensitive. See here for more info: GhostPack/Rubeus#36
Obviously the "correct" approach would be to perform a hollow AS-REQ first, extract the salt, then build the encrypted timestamp. That seems like a pain, so I've just altered the
enumusercommand to return the case-sensitive result in place of the user-supplied name.Happy to tweak, make changes, but I figured it might be valuable functionality to other people. I assume if it will get merged, a note in the docs/help would be in order.