System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported failing with CryptographicException

[amanasifkhalid]

Build Information

Build: https://dev.azure.com/dnceng-public/public/_build/results?buildId=1029669&view=results
Build error leg or test failing:

Error Message

Fill the error message using step by step known issues guidance.

{
  "ErrorMessage": "System.Security.Cryptography.CryptographicException",
  "BuildRetry": false,
  "ExcludeConsoleLog": false
}

Known issue validation

Build: 🔎 https://dev.azure.com/dnceng-public/public/_build/results?buildId=1029669
Error message validated: [System.Security.Cryptography.CryptographicException]
Result validation: ✅ Known issue matched with the provided build.
Validation performed at: 4/29/2025 6:23:08 PM UTC

Report

Build	Definition	Test	Pull Request
1030189	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#115166
1030072	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported
1030138	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#114861
1030101	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#115163
1030044	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#115161
1030025	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#114285
1030028	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#115068
1030016	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#114040
1029989	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#113930
1029985	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#115134
1029970	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#115157
1029964	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#114881
1030022	dotnet/runtime	System.Security.Cryptography.Cose.Tests.SignVerify.TestSignVerifySingleSignerAllAlgorithms	#115158
1029890	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#115132
1029857	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#114862
1029844	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#113988
1029792	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#114982
1029780	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#114800
1029669	dotnet/runtime	System.Security.Cryptography.X509Certificates.Tests.PfxTests.ReadMLKem512PrivateKey_NotSupported	#115150

Summary

24-Hour Hit Count	7-Day Hit Count	1-Month Count
19	19	19

[dotnet-policy-service]

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

[vcsjones]

Windows-2016Server-10.0.14393-SP0

Yet another another issue with PFX/PKCS12 and only running select changes on Windows 10 RTM.

I will file a separate issue to see if we can close this CI discrepancy separately, after I fix this.

[vcsjones]

Fix is merged; going to leave this open for a few days and the hit count should be at zero.

[vcsjones]

System.Security.Cryptography.Cose.Tests.SignVerify.TestSignVerifySingleSignerAllAlgorithms

Was not actually affected by this issue - that is a draft PR that is throwing a different CryptographicException but it got swept up in this issue's ErrorMessage.