SoylentNews is people
SoylentNews
Popular Bash shell script LetsEncrypt.sh, which is used to manage free SSL/TLS certificates from the Let's Encrypt project, has renamed this week to avoid a trademark row. This comes in the wake of Let's Encrypt successfully fending off Comodo, which tried to cynically snatch "Let's Encrypt" for itself.
LetsEncrypt.sh, written by Germany-based Lukas Schauer, is now known as Dehydrated. If you have scripts or apps that rely on pulling in his code and running it, they may stop working as a result of the name change. Dehydrated is developed independently by Schauer and is not officially affiliated with Let's Encrypt.
"This project was renamed from letsencrypt.sh because the original name was violating Let's Encrypt's trademark policy. I know that this results in quite a lot of installations failing but I didn't have a choice," reads the new Dehydrated README.
[...] Full disclosure: This article's author uses Let's Encrypt to provide HTTPS encryption for his personal websites. And you should use it too.
Our Previous Story: 800-Pound Comodo Tries to Trademark Upstart Rival's "Let's Encrypt" Name
(Score: 2) by edIII on Monday September 19 2016, @09:50PM
All of that stuff is automated. The only thing that *may* be a PITA are the rate limiting and thresholds set for those automated activities.
One platform is a bit more complicated (Zimbra ZCS) but I've still got all the instructions now in my buildsheet to attempt an automated renewal of my certs during the next round. If all you have is a simple nginx website, everything you just mentioned can be automated even easier since renewing those took all of 5 minutes.
For the wildcard certs you have a point, but almost every use case is covered Lets Encrypt. Where it isn't, then you're still a customer of the SSL Mafia I suppose.
Technically, lunchtime is at any moment. It's just a wave function.
(Score: 0) by Anonymous Coward on Tuesday September 20 2016, @01:18AM
Wildcard certs are a terrible idea anyway for multiple reasons (including security ones), so I'm not too broken up about Let's Encrypt not supporting them.