News for hackers. Stuff that matters.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by Wingy on Wednesday March 20, 2024 @11:53AM (#39768297)
Why modify the trust stores with the personal CA? Is there any risk to just publishing a globally valid wildcard cert for *.lcl.host, since it always resolves to 127.0.0.1 anyway?
Re:Lcl.host: fast, easy HTTPS in your local dev environment by 8organicbits on Wednesday March 20, 2024 @12:29PM (#39768838)
Some sites have tried this before, but I dont think they stay online long. The certificates are "leaked" when they are shared, so the CA will revoke them.

I think a better approach is to get a domain name and a Let's Encrypt certificate. There's lots of tooling for this, and it matches production. I built https://www.getlocalcert.net/ to act as free, Let's Encrypt compatible subdomain service specifically for these sorts of challenges.

Re:Lcl.host: fast, easy HTTPS in your local dev environment by extraduder_ire on Wednesday March 20, 2024 @12:58PM (#39769232)
Cool. I was hoping something like this existed, and glad to see you got it into the public suffix list. I'd been considering doing something like it for some time.
Re:Lcl.host: fast, easy HTTPS in your local dev environment by benburkert on Wednesday March 20, 2024 @12:08PM (#39768504)
We install the CA certificates into the trust stores so that the certificates are trusted by your browsers and clients, otherwise they will (rightfully!) get connection errors. We also set the CAA records for all lcl.host subdomains to anchor.dev, so no public CA will issue certificates for *.lcl.host. The only valid certs for lcl.host subdomains you will encounter are for your account's CAs. If we gave everyone a cert+key for *.lcl.host, besides the security concerns, we'd have to keep redistributing them every ~45 days, but with lcl.host you can setup ACME to automatically renew certs before they expire.