Skip to content

Conversation

@twz123
Copy link

@twz123 twz123 commented Jul 5, 2023

Instead of the generic crypto key types. This is done in the other parse functions as well. The code already does the type assertion.

Instead of the generic crypto key types. This is done in the other parse
functions as well. The code already does the type assertion.

// ParseEdPrivateKeyFromPEM parses a PEM-encoded Edwards curve private key
func ParseEdPrivateKeyFromPEM(key []byte) (crypto.PrivateKey, error) {
func ParseEdPrivateKeyFromPEM(key []byte) (ed25519.PrivateKey, error) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Given these are public functions, and the underlying types are different, I think this would be a breaking change.

We avoid breaking changes in major versions.

I do agree having parity would be nice, but not at the expense of introducing an incompatible change.

@oxisto oxisto mentioned this pull request Aug 14, 2023
6 tasks
@oxisto oxisto added the next The next iteration of development, currently `v6` label Sep 13, 2023
@mfridman mfridman closed this Sep 6, 2024
@mfridman
Copy link
Member

mfridman commented Sep 6, 2024

Closing for now, but we'll add this to #335

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

next The next iteration of development, currently `v6`

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants