Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify that mkcert and be used as an infrastructure CA #155

Open
sedalu opened this issue Apr 13, 2019 · 2 comments
Open

Clarify that mkcert and be used as an infrastructure CA #155

sedalu opened this issue Apr 13, 2019 · 2 comments
Labels
enhancement New feature or request

Comments

@sedalu
Copy link

sedalu commented Apr 13, 2019

Filippo, as we discussed as GothamGo, using mkcert as an infrastructure CA to secure internal service-to-service http calls is probably a use case falls within the mission of mkcert. The readme provides enough detail on how to do this manually, but it warns against "production" use. Please clarify that this use case is not discouraged. Thanks.
@FiloSottile FiloSottile added the enhancement New feature or request label Jun 1, 2019
@moritzdietz moritzdietz mentioned this issue Aug 7, 2019
Closed
@sawfi
Copy link

sawfi commented Jul 6, 2020

Hii

@polarathene
Copy link

For anyone else landing here, you might later find this issue which points you in the direction of step as a production grade alternative to mkcert.

A similar issue discussion also has this to say:

  • If you're just looking for a simple tool to create certs that work for local development, use mkcert.
  • If you're testing an ACME integration, use pebble (and step-ca, as a second data point :).
  • If you need something more sophisticated, like an ACME CA that you can bring into staging or run in production for server-to-server mTLS, check out step & step-ca!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@FiloSottile @sedalu @polarathene @sawfi