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.

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

Revert the MSVAVFLAGS_UNVERIFIED_SPN flag default #68

Merged
merged 1 commit into from
Mar 15, 2022

Conversation

simo5
Copy link
Collaborator

@simo5 simo5 commented Mar 15, 2022

By default SSPI does not set this flag, and setting it causes servers
with restrictive policy to fail authentication. Given no MS client sets
this flag by default, neither should we until there is a clear need.
We trust our calling applications to do the right thing here in any
case just like SSPI trusts their own calling applications.

Fixes #67

By default SSPI does not set this flag, and setting it causes servers
with restrictive policy to fail authentication. Given no MS client sets
this flag by default, neither should we until there is a clear need.
We trust our calling applications to do the right thing here in any
case just like SSPI trusts their own calling applications.

Signed-off-by: Simo Sorce <[email protected]>
@jborean93
Copy link

Can confirm these changes allow gss-ntlmssp to work with a server that's set to verify the SPN from an NTLM exchange.

@simo5 simo5 merged commit 734e522 into gssapi:main Mar 15, 2022
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.

UNTRUSTED_SPN_SOURCE should not be set
2 participants