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.

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

Support creating random self-signed SSL certificates for development purposes #642

Closed
kamadorueda opened this issue Sep 29, 2021 · 5 comments

Comments

@kamadorueda
Copy link
Contributor

We have this utility: https://gitlab.com/fluidattacks/product/-/tree/3e81d4681fde4912cc36dfe25cc16f64f7675d7f/makes/utils/ssl-certs
that we use for adding SSL certs to local versions of web servers. It would be nice to have it embedded on Makes

@kamadorueda kamadorueda removed their assignment Oct 12, 2021
@jpverde
Copy link
Collaborator

jpverde commented Nov 12, 2021

Done at #773

@jpverde jpverde closed this as completed Nov 12, 2021
@blaggacao
Copy link
Contributor

I'm not sure if this has been overlooked but mkcert also knows how to (temporarily!) import self signed certs into the relevant syst paths so that the browser, for example, would accept them as valid certs and not show the annoying unknown cert screen + other benefits.

But maybe the main use case here is for generating production root CA.

I just wondered. 😄

@jpverde
Copy link
Collaborator

jpverde commented Nov 17, 2021

@blaggacao hmm, we can give mkcert a try for our specific use case. In the meantime, we can give this a separate issue to keep this on track, since the main issue here was to embed a utility we're using right now.

@blaggacao
Copy link
Contributor

no worries, I just had the feeling the true greatness of mkcert somehow slipped 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants