Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

dns lookups shouldn't be used as-is for case sensitive principal names #465

Closed
snqk opened this issue May 28, 2022 · 0 comments · Fixed by #466
Closed

dns lookups shouldn't be used as-is for case sensitive principal names #465

snqk opened this issue May 28, 2022 · 0 comments · Fixed by #466

Comments

@snqk
Copy link
Contributor

snqk commented May 28, 2022

spnego.Client currently re-uses the exact response from CNAME lookups for principal names.

This can sometimes result in a KDC_ERR_S_PRINCIPAL_UNKNOWN error when DNS returns a mixed case (or upper case) response.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

spnego: case sensitive principal name resolution snqk/gokrb5
1 participant
@snqk