TLS::Text_Policy::allowed_signature_schemes() - #5773
Merged
Conversation
reneme
force-pushed
the
rene/tls_text_policy_for_signature_schemes
branch
from
July 29, 2026 10:58
7659074 to
6b64c77
Compare
This was referenced Jul 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This adds overrides for
allowed_signature_schemesandacceptable_signature_schemesinTLS::Text_Policy(addressing an API short-coming pointed out here). That way, users can specify exactly what signature schemes they wish to use. Before, users could only specify the allowed hash function and allowed signature algorithm. That made it impossible to restrict ECDSA to just the brainpool curves in TLS 1.3, for instance.As a by-product this allows simplifying the RFC 8448 test somewhat by using this new policy feature.