Stories
Slash Boxes
Comments

SoylentNews is people

Let's Encrypt Won its Comodo Trademark Battle - but Now Fan Tools Must Rename

posted by takyon on Monday September 19 2016, @08:26PM   Printer-friendly
from the let's-rename dept.

Arthur T Knackerbracket has found the following story:

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

Original Submission

 
This discussion has been archived. No new comments can be posted.
Let's Encrypt Won its Comodo Trademark Battle - but Now Fan Tools Must Rename | Log In/Create an Account | Top | 47 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by edIII on Tuesday September 20 2016, @09:33PM

    by edIII (791) on Tuesday September 20 2016, @09:33PM (#404505)

    Even before Let's Encrypt, StartSSL had been offering free certs for years. I'm still using them, because they're a bit more convenient to set up than Let's Encrypt (they just sign your CSR - Let's Encrypt assumes a particular server setup and the docs seemed to be entirely recipes that were very difficult to adapt if your server wasn't set up exactly how they expected).

    I wish I'd heard of them before. After thinking about a bit more, yeah, LE has one hell of a learning curve.

    You're correct about the difficulties with the "recipes". I don't think LE can solve it either. In other words, its better to configure your web server yourself and point to the certs, then use LE in certificate only mode. LE took on the ambitious task of "point and click" SSL cert generation and installation. So far, I haven't seen it work myself. Ever. I tried on basic nginx configurations on OpenBSD, but LE just failed.

    You can get it to work, but it involves you creating your own buildsheet for your particular setup and then automating it. For what it's worth, I haven't found an easy way to do that without interrupting services.

    --
    Technically, lunchtime is at any moment. It's just a wave function.
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2