Arstechnica reports
In July of 2017, the nonprofit certificate authority Let's Encrypt promised to deliver something that would put secure websites and Web applications within reach of any Internet user: free "wildcard" certificates to enable secure HTTP connections for entire domains. Today, Let's Encrypt took that promised service live, in addition to a new version of the Automated Certificate Management Environment (ACME) protocol, an interface that can be used by a variety of client software packages to automate verification of certificate requests.
[....]Many hosting providers already support the registration of Let's Encrypt certificates to varying degrees. But Let's Encrypt's free certificate offering hasn't been snapped up by some larger hosting providers—such as GoDaddy—who also sell SSL certificates to their customers.
(Score: 1, Touché) by Anonymous Coward on Wednesday March 14 2018, @03:43PM (8 children)
Whichever system you're using, if you can't automate a simple cert renew, the dumbass clearly is you.
(Score: 0) by Anonymous Coward on Wednesday March 14 2018, @04:08PM (7 children)
Says the dipshit that has never tried to automate something other than a simple HTTPd cert renewal. There simply is no way to automate renewals in some scenarios. Can't listen on port 80 or 443? Don't run your own public DNS servers? NO AUTOMATION FOR YOU!
(Score: 0) by Anonymous Coward on Wednesday March 14 2018, @04:19PM (1 child)
OMG I can't paint with this screwdriver! OMG I can't cook with this hammer! OMG this brush doesn't charge my cellphone!
Keep complaining about the tools you have, incompetent dumbass.
(Score: 0) by Anonymous Coward on Wednesday March 14 2018, @04:36PM
Just a fair warning since you're clearly a dipshit: don't smoke around your strawman. Strawmen are flammable.
(Score: 0) by Anonymous Coward on Wednesday March 14 2018, @04:31PM (2 children)
If you can do it on the command line, you can automate it. It may take some work, but it is possible.
(Score: 0) by Anonymous Coward on Wednesday March 14 2018, @04:34PM (1 child)
And if you can't do it from the command line?
(Score: 1, Touché) by Anonymous Coward on Wednesday March 14 2018, @05:28PM
Then learn how to do it.
(Score: 2) by NotSanguine on Thursday March 15 2018, @08:16AM
As someone who has implemented/automated PKI in large enterprise environments as well as small environments, I agree with the other AC.
This stuff is pretty easy to automate. Which is why stuff like 802.1x [wikipedia.org] authentication with certificates is pretty widespread.
Sure there are edge cases which make things a little more complicated, but so what?
Let's Encrypt's value is *specifically* in the web server certificate environment. In fact, it was rolled out to encourage more websites to support TLS. And you're disparaging it because it does what it was intended to do? Please.
No, no, you're not thinking; you're just being logical. --Niels Bohr
(Score: 2) by NotSanguine on Thursday March 15 2018, @08:16AM
As someone who has implemented/automated PKI in large enterprise environments as well as small environments, I agree with the other AC.
This stuff is pretty easy to automate. Which is why stuff like 802.1x [wikipedia.org] authentication with certificates is pretty widespread.
Sure there are edge cases which make things a little more complicated, but so what?
Let's Encrypt's value is *specifically* in the web server certificate environment. In fact, it was rolled out to encourage more websites to support TLS. And you're disparaging it because it does what it was intended to do? Please.
No, no, you're not thinking; you're just being logical. --Niels Bohr