-
Notifications
You must be signed in to change notification settings - Fork 712
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
Add s2n_signature_preferences_20240521 #4565
Conversation
&s2n_rsa_pkcs1_sha256, | ||
&s2n_rsa_pkcs1_sha384, | ||
&s2n_rsa_pkcs1_sha512, | ||
&s2n_rsa_pkcs1_sha224, |
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.
Just want to confirm that leaving RSA+224 in is intentional?
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.
waffled on this, decided to keep it since the likelihood of usage is ~slightly higher than ECDSA+SHA224.
This preference list is to allow ECDSA sigalgs to be prioritized for policies that need legacy sigalg(SHA1) support. This change is needed because TLS1.3 is reliant on the sigalg preferences to drive server certificate preference selection.
I think this is ready, unless someone sees a blocker. |
This preference list is to allow ECDSA sigalgs to be prioritized for policies that need legacy sigalg(SHA1) support.
This change is needed because TLS1.3 is reliant on the sigalg preferences to drive server certificate preference selection.
Call-outs:
The list used in this change will be added to security_policy later.