-
Notifications
You must be signed in to change notification settings - Fork 726
Invert working of SignatureScheme::supported_in_tls13
#2420
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
Conversation
Benchmark resultsInstruction countsSignificant differencesThere are no significant instruction count differences Other differencesClick to expand
Wall-timeSignificant differencesThere are no significant wall-time differences Other differencesClick to expand
Additional informationCheckout details:
|
0205e7c
to
d8d0b66
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2420 +/- ##
=======================================
Coverage 96.00% 96.01%
=======================================
Files 94 94
Lines 22525 22558 +33
=======================================
+ Hits 21626 21659 +33
Misses 899 899 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
Nice!
Maybe there should also be a line or 2 about why not "failing closed" is the better solution here? (Even if that is just "because it aligns more closely with the spec".) |
This was previously an allow-list, which stands in the way of people shipping providers for other algorithms that are not specifically outlawed in RFC8446.
d8d0b66
to
1b46817
Compare
Added a bit to the docstring for this function. |
This was previously an allow-list, which stands in the way of people shipping providers for other algorithms that are not specifically outlawed in RFC8446.
fixes #2419