Fix enterprise linux build

[sbomer]

Ensure a recent lld is available on the build host. See dotnet/dotnet-buildtools-prereqs-docker#843.

Attempting to fix the issue mentioned in #84148 (comment).

Fixes#85035

[ghost]

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

Issue Details

---

Ensure a recent lld is available on the build host.

Attempting to fix the issue mentioned in #84148 (comment).

Author:	sbomer
Assignees:	sbomer
Labels:	area-System.Net.Security
Milestone:	-

[sbomer]

/azp run runtime-libraries enterprise-linux

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[rzikm]

 System.Net.Security.Enterprise.Tests.NegotiateStreamLoopbackTest.StreamToStream_InvalidAuthentication_Failure(creds: NetworkCredential { Domain = "", Password = "PLACEHOLDERwong", SecurePassword = SecureString { Length = 15 }, UserName = "user1" }, target: "HOST/localhost") [FAIL]
System.Security.Authentication.AuthenticationException : Authentication failed, see inner exception.
---- System.ComponentModel.Win32Exception : GSSAPI operation failed with error - Unspecified GSS failure. Minor code may provide more information (Crypto routine failure).

does perhaps Ubuntu 22 come with a different libgss version than Ubuntu 18?

[sbomer]

I believe this is the same issue hit in #67353. Ubuntu 22.04 comes with openssl 3, which doesn't include md4 (except as a legacy provider) that gss-ntlmssp depends on. gss-ntlmssp was updated with a fix that lets it use the legacy provider, but the fix was released in version 1.1.0, while ubuntu 22.04 only has 0.7.0 available. Even the latest Ubuntu (22.10) only has 1.0.0.

Would it be acceptable to enable the legacy provider in the openssl config for this test (this workaround: #67353 (comment))? @wfurt

[rzikm]

Sounds reasonable to me

[rzikm]

LGTLM

[wfurt]

I guess it is too late but I'm wondering if we could just jump to 20.04 to avoid all the OpenSSL 3 mess.