mirror of
https://github.com/FiloSottile/mkcert.git
synced 2026-04-25 13:36:02 +03:00
[GH-ISSUE #72] customise key and cert names #38
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#38
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 @kishaningithub on GitHub (Aug 30, 2018).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/72
Ability to customise the names of output key and cert files would be a great usability feature
I suggest flags like
--o-key-file--o-cert-fileSo
would generate
my-cert.pemandmy-key.peminstead of the random looking./example.com+5.pem./example.com+5-key.pem@liamdawson commented on GitHub (Oct 8, 2018):
Alternatively, maybe the
openssl reqsyntax?Either way, the feature would be greatly appreciated! (I might look into doing it, but I know nothing about Golang yet)
@adamdecaf commented on GitHub (Oct 9, 2018):
I'd suggest avoiding adopting flag naming conventions from
openssl.--cert-fileand--key-file?@sleagon commented on GitHub (Oct 10, 2018):
I just add a PR to fix this, #77 . Just notice that, you should put the params before arguments insead of after them.
This will not work.
This works.
@sleagon commented on GitHub (Oct 10, 2018):
@kishaningithub @adamdecaf It will be nice if you guys could just try this PR.
@FiloSottile commented on GitHub (Jan 6, 2019):
Not a fan of adding flags, but giving in to this after seeing scripts reimplement the naming logic to find the certificates after they are generated.
@FiloSottile commented on GitHub (Jan 7, 2019):
Fixed in #77