Skip to content

support adding AES keytab entries for Active Directory#484

Open
rilott wants to merge 3 commits intojcmturner:masterfrom
rilott:rilott_ad_aes
Open

support adding AES keytab entries for Active Directory#484
rilott wants to merge 3 commits intojcmturner:masterfrom
rilott:rilott_ad_aes

Conversation

@rilott
Copy link

@rilott rilott commented Aug 25, 2022

Microsoft active directory uses it's own AES salt for keytab entries. This PR adds a new function AddActiveDirectoryComputerAccountEntry which handles this, and doesn't modify the normal AddEntry function.

I tried to add this with minimal code changes/duplication.

Partially fixes #416 (computer accounts only)
All tests pass

Thanks!
Ross

@gaxelac0
Copy link

The methods worked for me as the salt for the tickets emitted by Active Directory comes with the format
DOMAINsamAccountName

And gokrb5 tries to generate a salt with cname.GetSalt method, concatenating all the Names of the SPN which is wrong, ending with something like this:
DOMAINHTTPservicePrincipalName.DOMAIN

With the salt like that, the decryption will fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Keytab created for etype AES256/AES128 does not work with Active Directory

2 participants