[GH-ISSUE #81] feature request: ability to specify org name #45

New issue

Closed

opened 2026-02-25 22:32:27 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @ldayananda on GitHub (Oct 24, 2018).
Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/81

Currently the following will use UserAndHostname for certificate subject and Issuer OrganizationalUnit:

github.com/FiloSottile/mkcert@fcebdc9845/cert.go (L34-L39)

It would be nice to be able to specify a different OrganizationalUnit, maybe with -org-unit=

Originally created by @ldayananda on GitHub (Oct 24, 2018). Original GitHub issue: https://github.com/FiloSottile/mkcert/issues/81 Currently the following will use UserAndHostname for certificate subject and Issuer OrganizationalUnit: https://github.com/FiloSottile/mkcert/blob/fcebdc9845560b3945005932dfc0651ac06d6b98/cert.go#L34-L39 It would be nice to be able to specify a different OrganizationalUnit, maybe with `-org-unit=`

kerem closed this issue

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

kerem commented

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

Author

Owner

@adamdecaf commented on GitHub (Oct 24, 2018):

I'm not a fan of this. mkcert is for local dev certificates.

Can you explain the use-case a bit more? If you need a certificate with real details why not get one from a CA?

@adamdecaf commented on GitHub (Oct 24, 2018): I'm not a fan of this. `mkcert` is for local dev certificates. Can you explain the use-case a bit more? If you need a certificate with real details why not get one from a CA?

kerem commented

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

Author

Owner

@ldayananda commented on GitHub (Oct 24, 2018):

This is more for sharing with a team for a locally run tool. The hostname being tied to a user is awkward, but not a showstopper.

@ldayananda commented on GitHub (Oct 24, 2018): This is more for sharing with a team for a locally run tool. The hostname being tied to a user is awkward, but not a showstopper.

kerem commented

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

Author

Owner

@FiloSottile commented on GitHub (Jan 6, 2019):

mkcert has as few configuration options as possible by design. I don't think we should add one for this. I understand it's not great to have a username in a team root, but in a sense it helps remember that you are trusting whoever generated it with full MitM capabilities (as they might have a copy of the private key).

@FiloSottile commented on GitHub (Jan 6, 2019): mkcert has as few configuration options as possible by design. I don't think we should add one for this. I understand it's not great to have a username in a team root, but in a sense it helps remember that you are trusting whoever generated it with full MitM capabilities (as they might have a copy of the private key).

kerem referenced this issue

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

[GH-ISSUE #106] Integrated server #58

kerem referenced this issue

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

[GH-ISSUE #378] install esdsa root ca not supported #250

kerem referenced this issue

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

[PR #46] [MERGED] Add Windows Support #369