Fix implementation of NegotiateAuthentication.Wrap for Kerberos on Windows#91152
Fix implementation of NegotiateAuthentication.Wrap for Kerberos on Windows#91152wfurt merged 1 commit intodotnet:mainfrom
Conversation
|
Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones Issue DetailsFixes PowerShell/PowerShell#20168 The bug existed in .NET 7 but it was not uncovered until #86948 exposed it through Unfortunately, we lack testing infrastructure for testing Kerberos on Windows. NegotiateStreamKerberosTest outer loop test is supposed to cover it but I am not sure if it's even executed in any reasonable fashion. Thanks to @jborean93 for manually testing it on the affected use case in PowerShell.
|
|
/azp run runtime libraries-coreclr-outerloop |
|
No pipelines are associated with this pull request. |
|
/azp list |
|
/azp run runtime-libraries-coreclr outerloop |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
CI failures are unrelated, we are good to merge. I will give @wfurt a chance to have a look at this before merging. Thanks, Filip! |
|
Thanks for review and running the tests! |
|
should we try to take it to 8.0 @filipnavara? The fact that it impacts Powershell is concerning IMHO @karelz |
Almost certainly yes. |
|
@filipnavara is there a summary explanation, why we the bug is now exposed more in 8.0? (that will help to decide if we should take it for 8.0) |
|
Sure. Here's the simple explanation, I can stretch it out if necessary... ;-) In .NET 7 the
|
|
/backport to release/8.0 |
|
Started backporting to release/8.0: https://github.com/dotnet/runtime/actions/runs/6021734007 |
Fixes PowerShell/PowerShell#20168
The bug existed in .NET 7 but it was not uncovered until #86948 exposed it through
NegotiateStreamAPIs.Unfortunately, we lack testing infrastructure for testing Kerberos on Windows. NegotiateStreamKerberosTest outer loop test is supposed to cover it but I am not sure if it's even executed in any reasonable fashion. Thanks to @jborean93 for manually testing it on the affected use case in PowerShell.