| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
This PR fixes the BuildChainCustomTrustStore test that started failing in Alpine 3.22 due to the expiration of the Baltimore CyberTrust Root certificate on May 12, 2025. The certificate was subsequently removed from the system trust store, causing the test to fail when it expected the certificate to be available.
Sorry, something went wrong.
|
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones |
Sorry, something went wrong.
Sorry, something went wrong.
|
/backport to release/9.0-staging |
Sorry, something went wrong.
|
/backport to release/8.0-staging |
Sorry, something went wrong.
|
Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/16347511153 |
Sorry, something went wrong.
|
Started backporting to release/9.0-staging: https://github.com/dotnet/runtime/actions/runs/16347508992 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The test BuildChainCustomTrustStore started failing in Alpine 3.22.
This is failing because the root certificate of the chain, "C=IE, O=Baltimore, OU=CyberTrust, CN=Baltimore CyberTrust Root" expired May 12 23:59:00 2025. Since the root certificate is expired, it was completely removed from the trust store in an update to Alpine.
This unit test was relying on the certificate being in the system trust store, which is no longer true.
This pull request changes the "use the system trust store" case to permit an untrusted root. This is consistent with what we are doing in other tests that use this chain:
runtime/src/libraries/System.Security.Cryptography/tests/X509Certificates/ChainTests.cs
Lines 46 to 49 in a436284
Contributes to #117723