←back to thread

489 points gslin | 1 comments | | HN request time: 0.215s | source
Show context
mrtksn ◴[] No.42191644[source]
Hands down one of the greatest services out there, stopped a racket and made the internet secure.

I remember a time when having an HTTPS connection was for "serious" projects only because the cost of the certificate was much higher than the domain. You go commando and if it sticks then you purchase a certificate for a 100 bucks or something.

replies(5): >>42191676 #>>42192385 #>>42192827 #>>42192905 #>>42193198 #
dachris ◴[] No.42191676[source]
There's still enough people out there who don't know better, manually (or auto-renew) purchasing new a certificate every year from their hosting provider like it's 2013.
replies(7): >>42191711 #>>42191799 #>>42191800 #>>42191829 #>>42191872 #>>42191976 #>>42192618 #
technion ◴[] No.42191872[source]
I deal with multiple enterprise applications where idea of scripting a renewal involves playing with scripting headless Chrome.

I'm really not a fan of it but I'm happier paying for a one year cert than doing that

replies(1): >>42191950 #
yurishimo ◴[] No.42191950[source]
Sorry if this is a dumb question, but why? If I'm not mistaken, Let's Encrypt supports validation via DNS now so you don't even need to have a working webserver to issue a certificate. Automating a script to perform a renewal should be much simpler than headless Chrome!

If your DNS provider doesn't have an API, that seems like a separate issue but one that is well worth your organization's time if you're working in the enterprise!

replies(3): >>42191989 #>>42192076 #>>42192621 #
1. blipvert ◴[] No.42192076[source]
You can set up the _acme-challenge (or whatever it is)as a CNAME to point to a domain which does support an API for automating the renewal

(looking in to setting this up for a bunch of domains at work)