Skip to content

Conversation

reaperhulk
Copy link
Member

@reaperhulk reaperhulk commented May 16, 2025

We now support loading EC keys with explicit encodings of named curves. This requires that the explicit curve encoding match exactly (but allows the omission of the seed parameter to maintain compatibility with the -no_seed OpenSSL flag). This is only supported for secp256r1, secp384r1, secp521r1, and secp256k1 at this time.

This is not arbitrary explicit curve support; we still have no plans to implement that.

This PR also updates MSRV to 1.83 as we need that version for Option::unwrap() in const contexts and thus is blocked until we feel comfortable with that bump (As of late May 2025 75% of our sdist downloads have 1.83+)

@reaperhulk
Copy link
Member Author

We're going to need a 1.83 MSRV due to needing Option::unwrap in const context or else we'll have to change the approach to avoid use const values.

We now support loading EC keys with explicit encodings of named
curves.  This requires that the explicit curve encoding match
exactly (but allows the omission of the seed parameter to maintain
compatibility with the -no_seed OpenSSL flag). This is only supported
for secp256r1, secp384r1, secp521r1, and secp256k1 at this time.

This is not arbitrary explicit curve support; we still have no plans to
implement that.

This PR also updates MSRV to 1.83 as we need that version for
Option::unwrap() in const contexts.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants