Skip to content
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

Enable SHA-384 based signature algorithms and SECP384R1 key exchange #509

Merged
merged 2 commits into from
Jun 18, 2024

Conversation

jlaine
Copy link
Contributor

@jlaine jlaine commented Jun 18, 2024

The signature algorithms we offer match those offered by Chromium 126.

Fixes: #499

The signature algorithms we offer match those offered by Chromium 126.

Fixes: aiortc#499
Copy link

codecov bot commented Jun 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (6c5b9db) to head (a5f3b2a).
Report is 2 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #509   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           25        25           
  Lines         4976      4993   +17     
=========================================
+ Hits          4976      4993   +17     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jlaine jlaine changed the title Enable SHA-384 based signature algorithms Enable SHA-384 based signature algorithms and SECP384R1 key exchange Jun 18, 2024
@jlaine
Copy link
Contributor Author

jlaine commented Jun 18, 2024

@rthalley I've pushed a second commit to support SECP384R1 key exchange, still OK with you?

@rthalley
Copy link
Contributor

Still ok w/ it!

@jlaine jlaine merged commit d914a46 into aiortc:main Jun 18, 2024
29 checks passed
@jlaine jlaine deleted the sha384 branch June 18, 2024 15:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

No support for ECC certs with 384 key size, logs doesn't suggest the reason of failure
2 participants