[GH-ISSUE #31] Allow a custom comment in any generated names #16

New issue

Closed

opened 2026-02-25 22:32:23 +03:00 by kerem · 2 comments

kerem commented

2026-02-25 22:32:23 +03:00

Owner

Originally created by @vrillusions on GitHub (Jul 3, 2018).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/31

I understand wanting to keep mkcert development CA in the name so no shenanigans like Some Big Name Legit Authority CA but it would be useful to add a comment similar to the process of setting up a GPG key. It asks for your Name, Email, and an Optional comment. In GPG world it's so you could have John Doe (Work Correspondence Only) <worker@example.com>.

For here it would be to differentiate my mkcert development CA from someone else's mkcert development CA. Yes, the serial numbers will be different but at glance see a certificate was issued by (don't think you can have parenthesis in a subject name) mkcert development CA - vrillusions dev work or similar would be useful.

User experience could be something similar to GPG process where the mkcert development CA is hardcoded then prompt for an optional comment.

Originally created by @vrillusions on GitHub (Jul 3, 2018). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/31 I understand wanting to keep `mkcert development CA` in the name so no shenanigans like `Some Big Name Legit Authority CA` but it would be useful to add a _comment_ similar to the process of setting up a GPG key. It asks for your Name, Email, and an Optional comment. In GPG world it's so you could have `John Doe (Work Correspondence Only) <worker@example.com>`. For here it would be to differentiate my `mkcert development CA` from someone else's `mkcert development CA`. Yes, the serial numbers will be different but at glance see a certificate was issued by (don't think you can have parenthesis in a subject name) `mkcert development CA - vrillusions dev work` or similar would be useful. User experience could be something similar to GPG process where the `mkcert development CA` is hardcoded then prompt for an optional comment.

kerem closed this issue

2026-02-25 22:32:23 +03:00

kerem commented

2026-02-25 22:32:23 +03:00

Author

Owner

@FiloSottile commented on GitHub (Jul 3, 2018):

Without going into custom comments like GPG which never felt like a good experience to me, would $USER@$HOSTNAME to the subject work?

@FiloSottile commented on GitHub (Jul 3, 2018): Without going into custom comments like GPG which never felt like a good experience to me, would $USER@$HOSTNAME to the subject work?

kerem commented

2026-02-25 22:32:23 +03:00

Author

Owner

@vrillusions commented on GitHub (Jul 3, 2018):

Definitely. TL;DR version is some way to easily tell apart if mkcert development CA is one I put there or one someone else put there, or an old one, etc.

@vrillusions commented on GitHub (Jul 3, 2018): Definitely. TL;DR version is some way to easily tell apart if `mkcert development CA` is one I put there or one someone else put there, or an old one, etc.

kerem referenced this issue

2026-02-25 22:33:15 +03:00

[PR #16] [CLOSED] Update cert.go #358