Let's Encrypt

"Let’s Encrypt is a new Certificate Authority: It’s free, automated, and open."[1]

The idea would be to integrate the openSUSE/SLE support into the Let's Encrypt Client.

"The Let's Encrypt Client is a tool to automatically receive and install X.509 certificates to<br> enable TLS on servers. The client will interoperate with the Let's Encrypt CA which will be<br> issuing browser-trusted certificates for free."[2]

Let's Encrypt uses the Automated Certificate Management Environment (ACME) protocol[3]<br> to distribute certificates easily. Part of this project idea would be to understand the protocol<br> in detail.

From the Let's Encrypt blog[4]:

Nov 12, 2015
Public Beta: December 3, 2015
Let’s Encrypt will enter Public Beta on December 3rd, 2015. Once 
we’ve entered Public Beta our systems will be open to anyone who
would like to request a certificate.

Looking for mad skills in:

x509 certificate tls encryption acme

This project is part of:

Hack Week 13

Activity

  • almost 3 years ago: thardeck disliked Let’s Encrypt integration into openSUSE/SLE
  • almost 4 years ago: vbabka liked Let’s Encrypt integration into openSUSE/SLE
  • almost 4 years ago: fcrozat liked Let’s Encrypt integration into openSUSE/SLE
  • almost 4 years ago: joachimwerner liked Let’s Encrypt integration into openSUSE/SLE
  • almost 4 years ago: thardeck liked Let’s Encrypt integration into openSUSE/SLE
  • Show History

    Comments

    • Jedibeeftrix
      almost 4 years ago by Jedibeeftrix | Reply

      this would be an immensely valuable project for leap users. setting up an owncloud (or similar) server is trivial. enabling https is an ugly and painful process right now. this would help greatly.

    • osukup
      almost 4 years ago by osukup | Reply

      i added for Letsencrypt bootstrap for openSUSE, but in SLE isn't python-virtualenv package:(

    • abergmann
      almost 4 years ago by abergmann | Reply

      Yah, I've managed to pull my first Let's Encrypt certificate last night. ;-)

       Issuer: C=US, O=Let's Encrypt, CN=Let's Encrypt Authority X1
       Validity
           Not Before: Dec  3 21![add-emoji](https://assets-cdn.github.com/images/icons/emoji/29.png)00 2015 GMT
           Not After : Mar  2 21![add-emoji](https://assets-cdn.github.com/images/icons/emoji/29.png)00 2016 GMT
      

    • lnussel
      almost 4 years ago by lnussel | Reply

      http://blog.fefe.de/?ts=a89f4ed6 https://community.letsencrypt.org/t/list-of-client-implementations/2103 Might be worth to look at e.g. https://github.com/lukas2511/letsencrypt.sh and do a clean and small C implementation

    • abergmann
      almost 4 years ago by abergmann | Reply

      It's true, the python footprint of the official tools is quite intense to say the least. So a slender implementation would be a better approach to get this on as many platforms as possible. Digging into this... ;-)

    • msmeissn
      almost 4 years ago by msmeissn | Reply

      320148: integrate letsencrypt

    • msmeissn
      almost 4 years ago by msmeissn | Reply

      (I also opened: FATE#320148: integrate letsencrypt)

    • bmwiedemann
      almost 4 years ago by bmwiedemann | Reply

      I had good success with https://github.com/diafygi/acme-tiny and my helper /suse/bwiedemann/Export/contrib/Makefile

    • dmolkentin
      about 2 years ago by dmolkentin | Reply

      It's done. SLE/openSUSE 15 will have letsencrypt support through dehydrated, a client that comes with less baggage than the official one, as well as a bunch of useful enabler scripts.

    Similar Projects

    This project is one of its kind!