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

Allow loading ECDSA private key from PKCS8 file missing public key #2134

Closed
wants to merge 1 commit into from

Conversation

aj-bagwell
Copy link

PKCS8 encoded pem files have an option to have the public key in the same file as the private key.

Not all pem files will have it, and the public key can be derived from the private key anyway.

Fixes #2133

I agree to license my contributions to each file under the terms given at the top of each file I changed.

PKCS8 encoded pem files have an option to have the public key in the
same file as the private key.

Not all pem files will have it, and the public key can be derived from
the private key anyway.

Fixes briansmith#2133

I agree to license my contributions to each file under the terms given
at the top of each file I changed.
@briansmith
Copy link
Owner

Thanks for the PR. I'm going to close the PR for the reasons I mentioned in #2133 (comment), but I will be happy to review a new PR that meets the design requirements.

@briansmith briansmith closed this Sep 28, 2024
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.

Ring is unable to load ECDSA private key from a PKCS8 pem file which does not have the public key.
2 participants