[GH-ISSUE #229] Feature request: customize the name of the Root CA added to the trust store #146

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

Originally created by @dsebastien on GitHub (Dec 30, 2019).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/229

mkcert currently sets the name of the Root CA certificate to "mkcert user@host"; at least that's what I see in my Trusted Root Certification Authorities on Windows.

Would it be possible to customize (even partly) the name (e.g., adding a custom suffix)?
In my case, for isolation purposes, I generate multiple Root CA certificates for each environment of my application. Of course this is only used on the developers machines, but it would be nice for us to be able to distinguish the entries.

Originally created by @dsebastien on GitHub (Dec 30, 2019). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/229 mkcert currently sets the name of the Root CA certificate to "mkcert user@host"; at least that's what I see in my Trusted Root Certification Authorities on Windows. Would it be possible to customize (even partly) the name (e.g., adding a custom suffix)? In my case, for isolation purposes, I generate multiple Root CA certificates for each environment of my application. Of course this is only used on the developers machines, but it would be nice for us to be able to distinguish the entries.
Author
Owner

@arafel commented on GitHub (Jan 10, 2020):

Hi

Please could you try the change in the pullreq, see if it works for you?

Thanks
Paul

<!-- gh-comment-id:573079034 --> @arafel commented on GitHub (Jan 10, 2020): Hi Please could you try the change in the pullreq, see if it works for you? Thanks Paul
Author
Owner

@jjhuff commented on GitHub (Dec 19, 2025):

@arafel I'd love this feature too. Any chance you could reopen your PR (#235)? I'm happy to do it, but I don't want to take credit for your work!

<!-- gh-comment-id:3676632278 --> @jjhuff commented on GitHub (Dec 19, 2025): @arafel I'd love this feature too. Any chance you could reopen your PR (#235)? I'm happy to do it, but I don't want to take credit for your work!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/mkcert#146
No description provided.