-
Notifications
You must be signed in to change notification settings - Fork 5.3k
fix regression in ChannelBinding/NTLM auth #40222
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
Conversation
|
Tagging subscribers to this area: @dotnet/ncl |
src/libraries/Common/src/Interop/Windows/SspiCli/SecuritySafeHandles.cs
Outdated
Show resolved
Hide resolved
|
Aside from that, LGTM |
* fix regression in ChannelBinding/NTLM auth * fix index
|
@wfurt can you confirm if this change is already in .NET 5 preview 8? |
|
It does not seems to @SteveL-MSFT. Looks like the fix missed the train and I don't see it in preview8 branch. |
|
@wfurt thanks for the confirmation. The reported issues in the PowerShell web cmdlets repro'd with a build with .NET 5 preview 8 and was concerned that this PR didn't fix it. Looks like I'll have to see if it's fixed with RC1. |
|
unfortunately, yes. You can always grab daily build if you have local repro outside of production. |
This regression caused by #32008. The old security buffer had dedicated size property. With the PR, we switched to using Span and Span.Length. However that is not correct for TokenBinding. For that the span is empty e.g.
cbBufferbecomes 0 and OS will reject ChannelBinding buffer.Alternatively we can convert the UnmanagedToken to Span as well. But since currently doing not have any good test infrastructure for this, I would prefer to limit the changes.
This effectively solves #39011 but I will leave it open until we have tests to prevent regression like this.
contributes to #39011.