Skip to content

If client fails to connect using Win_SSPI plugin with Negotiate security package, try again using NTLM security package. #8274

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

Merged
merged 2 commits into from
Sep 30, 2024

Conversation

hvlad
Copy link
Member

@hvlad hvlad commented Sep 29, 2024

This allows new client connect to the old server that uses legacy NTLM security package.
This fixes #8256 finally.

…ity package, try again using NTLM security package.

This allows new client connect to the old server that uses legacy NTLM security package.
@hvlad hvlad requested a review from AlexPeshkoff September 29, 2024 21:23
@hvlad hvlad self-assigned this Sep 29, 2024
@hvlad hvlad merged commit f62f133 into master Sep 30, 2024
48 checks passed
hvlad added a commit that referenced this pull request Sep 30, 2024
If client fails to connect using Win_SSPI plugin with Negotiate security package, try again using NTLM security package.
hvlad added a commit that referenced this pull request Sep 30, 2024
If client fails to connect using Win_SSPI plugin with Negotiate security package, try again using NTLM security package.
@hvlad hvlad deleted the work/win_sspi_reconnect branch September 30, 2024 20:34
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.

Win_sspi plugin uses NTLM
2 participants