feat: TLS1.2 support for RSA-PSS certificates #4927
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release Summary:
Added TLS1.2 support for RSA-PSS certificates. Previously, RSA-PSS certificates could only be used with TLS1.3.
Resolved issues:
resolves #4804
Description of changes:
Supporting RSA-PSS certificates with TLS1.2 turned out to be as simple as just removing the TLS1.3-only restrictions. Previously, we specifically restricted RSA-PSS-PSS to TLS1.3.
Call-outs:
Testing:
I added a new end-to-end test to clearly assert that we support all certificates where we expect to.
I also updated the integration tests to use TLS1.2 + RSA-PSS. It's hard to tell that's working, so I dumped the output of a successful test_s2n_client_signature_algorithms run into a file and searched it. It looks like:
The commands I ran, and the results:
That looks correct to me, given the full set of ciphers:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.