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

System.Net.Security.Tests.NegotiateAuthenticationTests.Package_Unsupported_NTLM fails on Ubuntu 24 arm64 #111639

Open
tarekgh opened this issue Jan 20, 2025 · 6 comments
Assignees
Labels
area-System.Net.Security disabled-test The test is disabled in source code against the issue in-pr There is an active PR which will close this issue when it is merged
Milestone

Comments

@tarekgh
Copy link
Member

tarekgh commented Jan 20, 2025

Description

https://github.com/dotnet/runtime/pull/111504/checks?check_run_id=35807668189
https://helixr18s23ayyeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-111504-merge-1928f94a14a8400bac/System.Net.Security.Unit.Tests/3/console.992e600c.log?helixlogtype=result

Failing Configuration
Ubuntu.2410.Arm64.Open

Exception Message
Assert.Equal() Failure: Values differ
Expected: Unsupported
Actual:   ContinueNeeded
CallStack
   at System.Net.Security.Tests.NegotiateAuthenticationTests.Package_Unsupported_NTLM() in /_/src/libraries/System.Net.Security/tests/UnitTests/NegotiateAuthenticationTests.cs:line 94
   at System.Reflection.MethodBaseInvoker.InterpretedInvoke_Method(Object obj, IntPtr* args) in /_/src/mono/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.Mono.cs:line 22
   at System.Reflection.MethodBaseInvoker.InvokeWithNoArgs(Object obj, BindingFlags invokeAttr) in /_/src/libraries/System.Private.CoreLib/src/System/Reflection/MethodBaseInvoker.cs:line 57

Reproduction Steps

Enable the test on CI and watch the Ubuntu 24 leg test results.

Expected behavior

The test should pass on Ubuntu 24.

Actual behavior

The test is failing.

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

@dotnet-policy-service dotnet-policy-service bot added the untriaged New issue has not been triaged by the area owner label Jan 20, 2025
Copy link
Contributor

Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.

@wfurt
Copy link
Member

wfurt commented Jan 20, 2025

whit run is that @tarekgh ? I don't see such queue in runtime ....

@wfurt
Copy link
Member

wfurt commented Jan 20, 2025

I think the problem is here:

Interop.NetSecurityNative.IsNtlmInstalled() && (!PlatformDetection.IsOpenSslSupported || PlatformDetection.OpenSslVersion.Major < 3);

In NTLM used to be broken with OpenSSL 3.x but I guess it is fixed e.g. gssapi/gss-ntlmssp#72 finally rolled in. (or there is some other fix to make it work)

original runtime issue was #67353

@wfurt wfurt removed the untriaged New issue has not been triaged by the area owner label Jan 20, 2025
@wfurt wfurt added this to the 10.0.0 milestone Jan 20, 2025
@tarekgh
Copy link
Member Author

tarekgh commented Jan 20, 2025

@wfurt wfurt added linkable-framework Issues associated with delivering a linker friendly framework disabled-test The test is disabled in source code against the issue and removed linkable-framework Issues associated with delivering a linker friendly framework labels Jan 21, 2025
Copy link
Contributor

Tagging subscribers to 'linkable-framework': @eerhardt, @vitek-karas, @LakshanF, @sbomer, @joperezr, @marek-safar
See info in area-owners.md if you want to be subscribed.

@wfurt
Copy link
Member

wfurt commented Jan 21, 2025

Ubuntu 24 is now in main. We should investigate as time permits.

@rzikm rzikm self-assigned this Mar 12, 2025
@dotnet-policy-service dotnet-policy-service bot added the in-pr There is an active PR which will close this issue when it is merged label Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-System.Net.Security disabled-test The test is disabled in source code against the issue in-pr There is an active PR which will close this issue when it is merged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants