Fix encoding for non-ascii char in kerberos authentication #51
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.
With the hack.lu CTF this year and therefore a swedish AD environment it was reported that Kerberos authentication does not work with special chars (e.g.
öäü) that are present in some localized environments: Pennyw0rth/NetExec#963The problem is that kerberos uses
utf-8encoding for Kerberos Strings. However, as of now both minikerberos as well as impacket both uselatin1as its encoding, resulting in failed authentication with users that contain special chars.See:
A PR to fix the issue in impacket has been opened: fortra/impacket#2068
With both fixes applied, pfx authentication (which uses minikerberos as well as impacket) works as intended now (Before&After):

Be aware that i have not tested the kerberos protokoll on its own with minikerberos, but i expect the same result as in impacket (failed auth for usernames with
öäüetc in the name)!