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.

Sign up for GitHub

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

Jump to bottom

System.ComponentModel.Win32Exception thrown in System.Net.Security.Tests #52361

Closed
VincentBu opened this issue May 6, 2021 · 18 comments
Closed

System.ComponentModel.Win32Exception thrown in System.Net.Security.Tests #52361

VincentBu opened this issue May 6, 2021 · 18 comments
Labels
arch-arm64 area-System.Net.Security JitStress CLR JIT issues involving JIT internal stress modes os-windows test-run-core Test failures in .NET Core test runs
Milestone
7.0.0

Comments

@VincentBu
Copy link

Run: runtime-coreclr libraries-jitstress 20210505.1

Failed tests:

net6.0-windows-Release-arm64-CoreCLR_checked-no_tiered_compilation-Windows.10.Arm64v8.Open
 -System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success(serverProtocol: Ssl3)
 -System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success(clientProtocol: Ssl3)
 -System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_EachSupportedProtocol_Success(protocol: Ssl3)

Error message:

System.ComponentModel.Win32Exception : The client and server cannot communicate, because they do not possess a common algorithm.


Stack trace
   at System.Net.SSPIWrapper.AcquireCredentialsHandle(ISSPIInterface secModule, String package, CredentialUse intent, SCH_CREDENTIALS* scc) in /_/src/libraries/Common/src/Interop/Windows/SspiCli/SSPIWrapper.cs:line 138
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(CredentialUse credUsage, SCH_CREDENTIALS* secureCredential) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 527
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandleSchCredentials(X509Certificate certificate, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 231
   at System.Net.Security.SecureChannel.AcquireServerCredentials(Byte[]& thumbPrint) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 711
   at System.Net.Security.SecureChannel.GenerateToken(ReadOnlySpan`1 inputBuffer, Byte[]& output) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 779
   at System.Net.Security.SecureChannel.NextMessage(ReadOnlySpan`1 incomingBuffer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 723
   at System.Net.Security.SslStream.ProcessBlob(Int32 frameSize) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs:line 579
   at System.Net.Security.SslStream.ReceiveBlobAsync[TIOAdapter](TIOAdapter adapter) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs:line 541
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs:line 358
   at System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncSslHelper(SslProtocols clientSslProtocols, SslProtocols serverSslProtocols, Boolean expectedToFail) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ServerAsyncAuthenticateTest.cs:line 397
   at System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success(SslProtocols serverProtocol) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ServerAsyncAuthenticateTest.cs:line 71
--- End of stack trace from previous location ---
@VincentBu VincentBu added arch-arm64 area-System.Net.Security os-windows JitStress CLR JIT issues involving JIT internal stress modes labels May 6, 2021
@ghost
Copy link

ghost commented May 6, 2021

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

Issue Details

Run: runtime-coreclr libraries-jitstress 20210505.1

Failed tests:

net6.0-windows-Release-arm64-CoreCLR_checked-no_tiered_compilation-Windows.10.Arm64v8.Open
 -System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success(serverProtocol: Ssl3)
 -System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success(clientProtocol: Ssl3)
 -System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_EachSupportedProtocol_Success(protocol: Ssl3)

Error message:

System.ComponentModel.Win32Exception : The client and server cannot communicate, because they do not possess a common algorithm.


Stack trace
   at System.Net.SSPIWrapper.AcquireCredentialsHandle(ISSPIInterface secModule, String package, CredentialUse intent, SCH_CREDENTIALS* scc) in /_/src/libraries/Common/src/Interop/Windows/SspiCli/SSPIWrapper.cs:line 138
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(CredentialUse credUsage, SCH_CREDENTIALS* secureCredential) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 527
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandleSchCredentials(X509Certificate certificate, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 231
   at System.Net.Security.SecureChannel.AcquireServerCredentials(Byte[]& thumbPrint) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 711
   at System.Net.Security.SecureChannel.GenerateToken(ReadOnlySpan`1 inputBuffer, Byte[]& output) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 779
   at System.Net.Security.SecureChannel.NextMessage(ReadOnlySpan`1 incomingBuffer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 723
   at System.Net.Security.SslStream.ProcessBlob(Int32 frameSize) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs:line 579
   at System.Net.Security.SslStream.ReceiveBlobAsync[TIOAdapter](TIOAdapter adapter) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs:line 541
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](TIOAdapter adapter, Boolean receiveFirst, Byte[] reAuthenticationData, Boolean isApm) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs:line 358
   at System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncSslHelper(SslProtocols clientSslProtocols, SslProtocols serverSslProtocols, Boolean expectedToFail) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ServerAsyncAuthenticateTest.cs:line 397
   at System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success(SslProtocols serverProtocol) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ServerAsyncAuthenticateTest.cs:line 71
--- End of stack trace from previous location ---
Author: VincentBu
Assignees: -
Labels:

JitStress, arch-arm64, area-System.Net.Security, os-windows
Milestone: -

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label May 6, 2021
@karelz karelz added this to the Future milestone May 6, 2021
@karelz karelz removed the untriaged New issue has not been triaged by the area owner label May 6, 2021
@VincentBu

This comment has been minimized.

Sign in to view
@karelz
Copy link
Member

karelz commented May 20, 2021 •
edited
Loading

Kusto - methods to query:

  or Method == 'ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success'
  or Method == 'ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success'
  or Method == 'ClientAsyncAuthenticate_EachSupportedProtocol_Success'

Failures 3/18-9/2 (incl. PRs):

Date Build OS Test
5/5 no_tiered_compilation Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
5/19 jitstress2_tiered Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
6/9 jitstress2_tiered Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
6/13 zapdisable Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
6/14 no_tiered_compilation Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
6/15 zapdisable Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
6/22 jitstress2_tiered Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
6/26 jitstress2_jitstressregs4 Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
7/4 tailcallstress Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
7/5 jitstress1 Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
7/8 PR #55298 Windows.10.Amd64.Client21H1.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
7/11 jitstressregs0x1000 Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
7/21 no_tiered_compilation Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
7/23 PR #55298 Windows.10.Amd64.Client21H1.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
7/31 tailcallstress Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
8/1 jitstressregs0x80 Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
8/4 tailcallstress Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
8/15 jitstress2 Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
8/15 defaultpgo Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
8/15 dynamicpgo Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
8/15 nopgo Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
9/1 jitstress1_tiered Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
9/2 jitstress2 Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
9/4 jitstress1_tiered Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success
9/6 jitstress2_tiered Windows.10.Arm64v8.Open ServerAsyncAuthenticate_AllClientVsIndividualServerSupportedProtocols_Success
ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success
ClientAsyncAuthenticate_EachSupportedProtocol_Success

It is suspicious that it fails only with JitStress and all tests at once, also always together with test failures in #52362 -- perhaps some kind of environmental problem?

@karelz karelz mentioned this issue May 20, 2021
Closed
@geoffkizer geoffkizer mentioned this issue May 20, 2021
Open
@VincentBu

This comment has been minimized.

Sign in to view
@VincentBu

This comment has been minimized.

Sign in to view
@VincentBu

This comment has been minimized.

Sign in to view
@VincentBu

This comment has been minimized.

Sign in to view
@VincentBu

This comment has been minimized.

Sign in to view
@danmoseley
Copy link
Member

@BruceForstall another one that seems unique to jitstress.

@karelz karelz added the test-run-core Test failures in .NET Core test runs label Aug 24, 2021
@BruceForstall
Copy link
Member

The same comment I wrote in #52362 applies here.

@VincentBu

This comment has been minimized.

Sign in to view
@danmoseley
Copy link
Member

It is suspicious that it fails only with JitStress and all tests at once, also always together with test failures in #52362 -- perhaps some kind of environmental problem?

Again, jitstress + #52362...

@kunalspathak kunalspathak mentioned this issue Dec 13, 2021
Merged
@wfurt
Copy link
Member

wfurt commented Feb 8, 2022

It seems like all the linked occurrences fail with Ssl3 ... that is old and should not be used. Is it possible that some of the stress machines are configure in different way?
I feel it would be OK to drop SSL3 from the list if that creates too much noise. Especially if we can do that for stress only.
cc: @rzikm

@VincentBu
Copy link
Author

Failed again in: runtime-coreclr libraries-jitstress 20220323.2

Failed test:

net7.0-windows-Release-arm64-CoreCLR_checked-no_tiered_compilation-Windows.10.Arm64v8.Open

- System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success(clientProtocol: Ssl3)
- System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_EachSupportedProtocol_Success(protocol: Ssl3)

Error message:

System.Security.Authentication.AuthenticationException : Authentication failed, see inner exception.
---- System.ComponentModel.Win32Exception : The client and server cannot communicate, because they do not possess a common algorithm.


Stack trace
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(SslStreamCertificateContext certificateContext, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 160
   at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 610
   at System.Net.Security.SecureChannel.GenerateToken(ReadOnlySpan`1 inputBuffer, Byte[]& output) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 785
   at System.Net.Security.SecureChannel.NextMessage(ReadOnlySpan`1 incomingBuffer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 727
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](Boolean receiveFirst, Byte[] reAuthenticationData, CancellationToken cancellationToken) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs:line 0
   at System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncSslHelper(EncryptionPolicy encryptionPolicy, SslProtocols clientSslProtocols, SslProtocols serverSslProtocols, RemoteCertificateValidationCallback certificateCallback) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ClientAsyncAuthenticateTest.cs:line 157
   at System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncSslHelper(EncryptionPolicy encryptionPolicy, SslProtocols clientSslProtocols, SslProtocols serverSslProtocols, RemoteCertificateValidationCallback certificateCallback) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ClientAsyncAuthenticateTest.cs:line 176
   at System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success(SslProtocols clientProtocol) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ClientAsyncAuthenticateTest.cs:line 82
--- End of stack trace from previous location ---
----- Inner Stack Trace -----
   at System.Net.SSPIWrapper.AcquireCredentialsHandle(ISSPIInterface secModule, String package, CredentialUse intent, SCH_CREDENTIALS* scc) in /_/src/libraries/Common/src/Interop/Windows/SspiCli/SSPIWrapper.cs:line 138
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(CredentialUse credUsage, SCH_CREDENTIALS* secureCredential) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 605
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandleSchCredentials(SslStreamCertificateContext certificateContext, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 305
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(SslStreamCertificateContext certificateContext, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 147

@rzikm
Copy link
Member

rzikm commented Mar 31, 2022 •
edited
Loading

I expect this is connected with #65098 (all failures have SSL3 on Windows 2022 server in common)

@VincentBu
Copy link
Author

Failed again in: runtime-coreclr libraries-jitstressregs 20220403.1

Failed test:

net7.0-windows-Release-arm64-CoreCLR_checked-jitstressregs4-Windows.10.Arm64v8.Open

- System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success(clientProtocol: Ssl3)
- System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_EachSupportedProtocol_Success(protocol: Ssl3)

Error message:

System.Security.Authentication.AuthenticationException : Authentication failed, see inner exception.
---- System.ComponentModel.Win32Exception : The client and server cannot communicate, because they do not possess a common algorithm.


Stack trace
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(SslStreamCertificateContext certificateContext, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 160
   at System.Net.Security.SecureChannel.AcquireCredentialsHandle(SslAuthenticationOptions sslAuthenticationOptions) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 723
   at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 610
   at System.Net.Security.SecureChannel.GenerateToken(ReadOnlySpan`1 inputBuffer, Byte[]& output) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 834
   at System.Net.Security.SecureChannel.NextMessage(ReadOnlySpan`1 incomingBuffer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 776
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](Boolean receiveFirst, Byte[] reAuthenticationData, CancellationToken cancellationToken) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs:line 0
   at System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncSslHelper(EncryptionPolicy encryptionPolicy, SslProtocols clientSslProtocols, SslProtocols serverSslProtocols, RemoteCertificateValidationCallback certificateCallback) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ClientAsyncAuthenticateTest.cs:line 157
   at System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncSslHelper(EncryptionPolicy encryptionPolicy, SslProtocols clientSslProtocols, SslProtocols serverSslProtocols, RemoteCertificateValidationCallback certificateCallback) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ClientAsyncAuthenticateTest.cs:line 176
   at System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success(SslProtocols clientProtocol) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ClientAsyncAuthenticateTest.cs:line 82
--- End of stack trace from previous location ---
----- Inner Stack Trace -----
   at System.Net.SSPIWrapper.AcquireCredentialsHandle(ISSPIInterface secModule, String package, CredentialUse intent, SCH_CREDENTIALS* scc) in /_/src/libraries/Common/src/Interop/Windows/SspiCli/SSPIWrapper.cs:line 138
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(CredentialUse credUsage, SCH_CREDENTIALS* secureCredential) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 605
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandleSchCredentials(SslStreamCertificateContext certificateContext, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 305
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(SslStreamCertificateContext certificateContext, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 147

@VincentBu
Copy link
Author

Failed again in: runtime-coreclr libraries-jitstressregs 20220424.1

Failed test:

net7.0-windows-Release-arm64-CoreCLR_checked-jitstressregs1-Windows.10.Arm64v8.Open

- System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success(clientProtocol: Ssl3)

Error message:

System.Security.Authentication.AuthenticationException : Authentication failed, see inner exception.
---- System.ComponentModel.Win32Exception : The client and server cannot communicate, because they do not possess a common algorithm.


Stack trace
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(SslStreamCertificateContext certificateContext, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 160
   at System.Net.Security.SecureChannel.AcquireCredentialsHandle(SslAuthenticationOptions sslAuthenticationOptions) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 723
   at System.Net.Security.SecureChannel.AcquireClientCredentials(Byte[]& thumbPrint) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 610
   at System.Net.Security.SecureChannel.GenerateToken(ReadOnlySpan`1 inputBuffer, Byte[]& output) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 834
   at System.Net.Security.SecureChannel.NextMessage(ReadOnlySpan`1 incomingBuffer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SecureChannel.cs:line 776
   at System.Net.Security.SslStream.ForceAuthenticationAsync[TIOAdapter](Boolean receiveFirst, Byte[] reAuthenticationData, CancellationToken cancellationToken) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStream.Implementation.cs:line 0
   at System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncSslHelper(EncryptionPolicy encryptionPolicy, SslProtocols clientSslProtocols, SslProtocols serverSslProtocols, RemoteCertificateValidationCallback certificateCallback) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ClientAsyncAuthenticateTest.cs:line 157
   at System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncSslHelper(EncryptionPolicy encryptionPolicy, SslProtocols clientSslProtocols, SslProtocols serverSslProtocols, RemoteCertificateValidationCallback certificateCallback) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ClientAsyncAuthenticateTest.cs:line 176
   at System.Net.Security.Tests.ClientAsyncAuthenticateTest.ClientAsyncAuthenticate_AllServerVsIndividualClientSupportedProtocols_Success(SslProtocols clientProtocol) in /_/src/libraries/System.Net.Security/tests/FunctionalTests/ClientAsyncAuthenticateTest.cs:line 82
--- End of stack trace from previous location ---
----- Inner Stack Trace -----
   at System.Net.SSPIWrapper.AcquireCredentialsHandle(ISSPIInterface secModule, String package, CredentialUse intent, SCH_CREDENTIALS* scc) in /_/src/libraries/Common/src/Interop/Windows/SspiCli/SSPIWrapper.cs:line 138
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(CredentialUse credUsage, SCH_CREDENTIALS* secureCredential) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 605
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandleSchCredentials(SslStreamCertificateContext certificateContext, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 305
   at System.Net.Security.SslStreamPal.AcquireCredentialsHandle(SslStreamCertificateContext certificateContext, SslProtocols protocols, EncryptionPolicy policy, Boolean isServer) in /_/src/libraries/System.Net.Security/src/System/Net/Security/SslStreamPal.Windows.cs:line 147

@rzikm
Copy link
Member

rzikm commented Jul 15, 2022

No recent hits, closing as not actionable

@rzikm rzikm closed this as completed Jul 15, 2022
@karelz karelz modified the milestones: Future, 7.0.0 Jul 19, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Aug 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
arch-arm64 area-System.Net.Security JitStress CLR JIT issues involving JIT internal stress modes os-windows test-run-core Test failures in .NET Core test runs
Projects
None yet
Milestone
7.0.0
Development

No branches or pull requests
6 participants
@karelz @danmoseley @BruceForstall @wfurt @rzikm @VincentBu