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 Thexalon on Tuesday September 20 2016, @12:01PM
So let's say we did what you asked, and did an SSL connection to send in passwords to Soylent, and left everything else unencrypted. If we implement your plan, then part of what's unencrypted is your session cookie. Which means that now, anybody who intercepts that session cookie can for the next several hours pretend to be you, change your password, and lock you out of your own account.
Or let's say you're working on a site with some sort of nice WYSIWYG editor, and you accidentally paste in sensitive information from another window. Even if you deleted it, you've just put that out on the open wire, where it can be intercepted. Hope it wasn't something important like your SSN or bank account!
The only thing that stops a bad guy with a compiler is a good guy with a compiler.