-
Notifications
You must be signed in to change notification settings - Fork 111
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
Add Certificate::from_der
+ Certificate::from_pem
#274
Comments
Yeah, this API isn't great right now. I've described a plan to improve it in #269 (comment) -- if you want to help implementing that, that would be awesome. Unfortunately with the current API I don't think there's a way around doing a fake self-signing of the CA certificate before using it to sign dependent certificates. |
This would be great to have. It's the reason I can't upgrade to 0.13 right now. I only notized after converting most of my code, which is unfortunate, but I had the opportunity to see the new 0.13 in action. I actually really like the new params/signing API - it's a lot nicer to use than the manual |
I'm in the process of upgrading rcgen and I have to say the new API is much easier to understand, great job!
In reading some of the #62 I can see the idea of adding
Certificate::from_der
andCertificate::from_pem
came up but they don't seem to have made it into the final release.I wanted to know if there is a way to load an existing CA certificate to sign some more certificates without triggering signing.
Right now i'm doing the following:
However, my presumption is that this will sign a new CA certificate on each startup of my application and I would rather just import the existing CA certificate and use it.
I tried to do a PR to add the
Certificate::from_der
+Certificate::from_pem
but i'm kinda lost where thesubject_public_key_info
would come from. I've included what I had below:The text was updated successfully, but these errors were encountered: