This repository has been archived by the owner on Dec 6, 2023. It is now read-only.
Fix kerberos authentication #655
Merged
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
|
Hello, this is awesome I like it 🥇 Can you review the change I made ? :) |
zblurx
commented
Oct 20, 2022
|
did you test with mssql @zblurx ? I notice there is a kerberoslogin in impacket for mssql also ! |
|
I did not know. Gonna test this :) |
|
done @zblurx |
|
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Hey,
This PR fix kerberos authentication, previously working only with tickets in KRB5CNAME.
Now, -k is use to specify that the authentication flow should use kerberos, so it is working with cleartext, nthash and obviously aesKey
A new option --use-kcache is used to specify that the authentication should use KRB5CNAME.
Very useful when working on domain with Protected Users :)