Fix issue with checksum calculations for PA-FOR-USER#2192
Open
jfjallid wants to merge 1 commit into
Open
Conversation
…dows Server 2025 KDCs. Checksum type is now determined by session key enctype
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
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.
Certain Windows server 2025 KDCs reject PA-FOR-USER checksums that use the hardcoded HMAC-MD5 algorithm.
They require that the checksum match the enctype for the session key and using HMAC-MD5 when the session key is AES128 or AES256 will result in a KRB_AP_ERR_MODIFIED response to the TGS REQ.