News for hackers. Stuff that matters.
Re:Developing HTTPS Services in Node with Self-Signed Certif... by tootie on Sunday May 13, 2018 @08:37PM (#17061870)
If you own a domain, create a A record for local.mydomain.com and point it to 127.0.0.1 and you can generate a valid cert with Let's Encrypt.
Re:Developing HTTPS Services in Node with Self-Signed Certif... by schoen on Sunday May 13, 2018 @11:57PM (#17062571)
In this case you'll need to use the DNS-01 validation method for the domain issuance, not HTTP-01 (because local.mydomain.com won't be able to receive an inbound validation connection from Let's Encrypt).
Re:Developing HTTPS Services in Node with Self-Signed Certif... by tootie on Monday May 14, 2018 @09:40AM (#17065393)
There's various tricks. You can also assign the domain to a static IP long enough to verify your ownership then change it. Using a TXT record is probably easier to automate renewal though.
Re:Developing HTTPS Services in Node with Self-Signed Certif... by therealmarv on Monday May 14, 2018 @01:33AM (#17062941)
thx for this method. Did not know that there is also another DNS based verification for normal subdomains on letsencrypt.
Re:Developing HTTPS Services in Node with Self-Signed Certif... by zaarn on Monday May 14, 2018 @02:43AM (#17063263)
Alternatively, what I do is to sign a wildcard cert for a subdomain plus *.subdomain valid for a couple years and putting the key and cert on my Nextcloud in an encrypted archive file, that way I always have access to a cert that I trust and can easily install on a local computer.