-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Condition S.S.Cryptography tests on SHA1 signature support #67998
Conversation
Tagging subscribers to this area: @dotnet/area-system-security, @vcsjones Issue DetailsThis gets System.Security.Cryptography and System.Security.Cryptography.OpenSsl tests to pass on RHEL 9 and other similar distributions where SHA1 signatures are no longer permitted. Places where the hash algorithm didn't matter I switched to SHA2. Where SHA1 was explicitly under test, they are now skipped on platforms that don't support it. This does not fix S.S.C.X509Certificates. That is significantly more effort due to a lot of test data that use SHA1, and will be done in a follow up PR. Contributes to #65874
|
Draft to get feedback from CI and I might try to append X509Certificates changes to this, depending on how much additional work it turns out to be. |
I'm going to run this branch through our CI and report the list of test failures. |
These are the failing tests.
|
@vcsjones let me know when it is helpful to run your PR against our rhel9 CI. |
I marked this as ready for review to at least get the Regarding These test projects have a considerable amount of SHA1 use, largely just as test data. We would want to move to SHA256 where feasible, as just doing a blanket "disable what doesn't work" would result in a significant test gap in RHEL9. If we disable the signed signed cert check, a lot of those X509Certificate tests will start working, so I don't want to replace a ton of test data until its been confirmed that is the appropriate thing to do. |
Makes sense. Let's wait for @bartonjs to chime in. |
...braries/Common/tests/System/Security/Cryptography/AlgorithmImplementations/RSA/SignVerify.cs
Show resolved
Hide resolved
src/libraries/System.Security.Cryptography.Csp/tests/RSACryptoServiceProviderProvider.cs
Show resolved
Hide resolved
@tmds I am going to merge this as-is and open further pull requests for other areas. |
This gets System.Security.Cryptography and System.Security.Cryptography.OpenSsl tests to pass on RHEL 9 and other similar distributions where SHA1 signatures are no longer permitted.
Places where the hash algorithm didn't matter I switched to SHA2. Where SHA1 was explicitly under test, they are now skipped on platforms that don't support it.
This does not fix S.S.C.X509Certificates. That is significantly more effort due to a lot of test data that use SHA1, and will be done in a follow up PR.
Contributes to #65874