mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 13:36:02 +03:00
[GH-ISSUE #69] Is there a way to generate PKCS#1 RSA keys? #36
Labels
No labels
TLS stack issue
Windows
bug
duplicate
duplicate
enhancement
help wanted
help wanted
pull-request
question
question
root store
waiting for info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mkcert#36
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @drusellers on GitHub (Aug 25, 2018).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/69
basically looking to generate a key with the header
-----BEGIN RSA PRIVATE KEY-----Something that is similar to what is generated by this: https://github.com/SergioBenitez/Rocket/blob/master/examples/tls/private/gen_cert.sh
Thank you for this work!
@FiloSottile commented on GitHub (Aug 25, 2018):
What software do you need it for? Most should recognize the PKCS#8 keys that mkcert generates, as these days it's even the default generated by openssl.
Anyway you can convert them like this:
I'd rather not add a flag to mkcert unless there is a lot of requests for the feature.
@drusellers commented on GitHub (Aug 25, 2018):
@FiloSottile the rust web project Rocket is apparently using a lib that was expecting it. I don't have all of the terminology down so I was surprised it didn't work out of the box. Knowing how many options
opensslhas I thought a few different output options might be on the horizon. :) but i totally appreciate keeping your project simple!@FiloSottile commented on GitHub (Aug 25, 2018):
Thanks for understanding and I hope the command above worked to convert it.
You might want to consider opening an issue with Rocket to support PKCS#8 encoded private keys?
@lopezator commented on GitHub (Nov 27, 2020):
I have a related issue.
Sometimes I'm given certs that use the:
"PRIVATE RSA KEY" header and want to import them using mkcert.
I ended up by editing manually the headers to "PRIVATE KEY".
Changing this condition:
https://github.com/FiloSottile/mkcert/blob/master/cert.go#L301-L303
To:
Would this have any sense? Or the formats are just incompatible and wouldn't work?
@den-is commented on GitHub (Nov 22, 2021):
Encounter same issue when certificate starts with the
-----BEGIN RSA PRIVATE KEY-----