-
Notifications
You must be signed in to change notification settings - Fork 5k
Enable revocation list tests for ML-DSA and SLH-DSA #115254
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
base: main
Are you sure you want to change the base?
Enable revocation list tests for ML-DSA and SLH-DSA #115254
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR extends the supported revocation list tests to include the ML-DSA and SLH-DSA algorithms by updating key factory definitions and certificate-related functions.
- Introduces a new key factory for SLH-DSA.
- Updates the build variant factories to include both ML-DSA and SLH-DSA.
- Enhances certificate creation and signature generation to support the new SLH-DSA algorithm.
Tagging subscribers to this area: @dotnet/area-system-security, @bartonjs, @vcsjones |
...libraries/Common/tests/System/Security/Cryptography/X509Certificates/CertificateAuthority.cs
Outdated
Show resolved
Hide resolved
Looks like this is introducing some test failures (a few SslStream tests seem to be waking up to ML-DSA and SLH-DSA? Though that seems surprising...):
If it's that PQC certs are making it into the tests, we can either make those tests pick RSA (sad) or insert the ML-DSA/SLH-DSA calls into Lines 70 to 72 in dd75c45
|
Especially because as far as I know, nothing in CI has OpenSSL 3.5 yet (does it?) so it feels like an |
Add ML-DSA and SLH-DSA to the list of tested algorithms for revocation.