Re:Show HN: Mkcert – Valid HTTPS certificates for localhost
by mic159 on Monday January 07, 2019 @01:54AM
(#18843316)
What's wrong with Lets Encrypt and DNS challenge?
Then you get a globally recognised cert.
[ Parent
| on HN ]
Re:Show HN: Mkcert – Valid HTTPS certificates for localhost
by alphabettsy on Monday January 07, 2019 @02:05AM
(#18843359)
Nothing, but thats not what this is for at all.
Re:Show HN: Mkcert – Valid HTTPS certificates for localhost
by MehdiHK on Monday January 07, 2019 @02:40AM
(#18843482)
You cannot use them for localhost
Re:Show HN: Mkcert – Valid HTTPS certificates for localhost
by jimdigriz on Monday January 07, 2019 @08:38AM
(#18844947)
Seems a lot easier to register your own domain (useful for so many other things), point localhost.mydomain.com to 127.0.0.1 and run:
sudo apt-get -yy install --no-install-recommends certbot
mkdir -p le
certbot --work-dir ./le --logs-dir le --config-dir le -d localhost.mydomain.com --manual --preferred-challenges dns certonly
Follow the instructions adding the TXT record, you have a valid cert in minutes.
Re:Show HN: Mkcert – Valid HTTPS certificates for localhost
by mic159 on Monday January 07, 2019 @03:58PM
(#18849992)
Yes you can. You control the DNS, just point that subdomain to 127.0.0.1.
Re:Show HN: Mkcert – Valid HTTPS certificates for localhost
by thechriswalker on Monday January 07, 2019 @05:58AM
(#18844270)
That's what I use, Caddy webserver with Gandi DNS (also used Route53 in the past) handling the ACME challenge and a `*.l.mydomain.tld` pointing to 127.0.0.1.
Adding reverse proxies for different local services becomes a piece of cake, but mkcert allows you to use `localhost` directly if needed. Personally I never have and like not having to make any changes to the trust store.