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: 0) by Anonymous Coward on Tuesday September 20 2016, @12:34AM
I really don't care if someone hacks my information-only website, it's for my small consulting company. The site exists to inform the curious about what we do, and gives our phone number and an info@... email for someone that is actually interested in using our services. We only work business-to-business and nearly all of our business is generated by personal contact, or by referral. We tend to have one or two big customers and keep them for many years. I think we might have picked up one small job through the website in the last ~15 years.
The only reason we have a website at all is because one of my younger guys insisted that we have one, his comment was,"You don't have a company if you don't have a website." On the plus side, it saved a little on printing costs, we don't hand out brochures anymore at trade shows--that is the info that is on the website. And if it got hacked, we'd probably notice in a day or two and reload it from offline backup. No big deal.
(Score: 0) by Anonymous Coward on Tuesday September 20 2016, @01:14AM
One thing I did with my website is set up a cron job that pulls a couple of pages, makes sure they are a 200 response, compares hashes to known good, and emails if there is a problem. This prevents different attacks from succeeding for long and has caught a hijacking before the hosting company noticed at all and alerted me to a few attacks at the same time I get the email from the hosting company. And yes, after the third one, we got a different host.
(Score: 0) by Anonymous Coward on Tuesday September 20 2016, @07:26AM
Injecting 0-day exploits to your clients. Sounds pretty useful to me.