Lets Encrypt Enters Public Beta
-
We’re happy to announce that Let’s Encrypt has entered Public Beta. Invitations are no longer needed in order to get free certificates from Let’s Encrypt.
It’s time for the Web to take a big step forward in terms of security and privacy. We want to see HTTPS become the default. Let’s Encrypt was built to enable that by making it as easy as possible to get and manage certificates.
We’d like to thank everyone who participated in the Limited Beta. Let’s Encrypt issued over 26,000 certificates during the Limited Beta period. This allowed us to gain valuable insight into how our systems perform, and to be confident about moving to Public Beta.
We’d also like to thank all of our sponsors for their support. We’re happy to have announced earlier today that Facebook is our newest Gold sponsor.
We have more work to do before we’re comfortable dropping the beta label entirely, particularly on the client experience. Automation is a cornerstone of our strategy, and we need to make sure that the client works smoothly and reliably on a wide range of platforms. We’ll be monitoring feedback from users closely, and making improvements as quickly as possible.
Instructions for getting a certificate with the Let’s Encrypt client can be found here.
Let’s Encrypt Community Support is an invaluable resource for our community, we strongly recommend making use of the site if you have any questions about Let’s Encrypt.
Let’s Encrypt depends on support from a wide variety of individuals and organizations. Please consider getting involved, and if your company or organization would like to sponsor Let’s Encrypt please email us at [email protected].
https://letsencrypt.org/2015/12/03/entering-public-beta.html
-
Installing Let’s Encrypt
Note: Let’s Encrypt is in beta. Please don’t use it unless you’re comfortable with beta software that may contain bugs.If your operating system includes a packaged copy of letsencrypt, install it from there and use the letsencrypt command. Otherwise, you can use our letsencrypt-auto wrapper script to get a copy quickly:
$ git clone https://github.com/letsencrypt/letsencrypt $ cd letsencrypt $ ./letsencrypt-auto --helpletsencrypt-auto accepts the same flags as letsencrypt; it installs all of its own dependencies and updates the client code automatically (but it’s comparatively slow and large in order to achieve that).
-
@scottalanmiller When will you have a guide written for CentOS7? Will Mangolassi being using it?
-
@anonymous said:
@scottalanmiller When will you have a guide written for CentOS7? Will Mangolassi being using it?
We'll been Ubuntu for ML. The hope is to use it. Jared has actually done some work here to prepare. Yes, if at all possible, we plan to move to it, but not until it exits beta. We tend to run on "just released" here (OS, application, etc.) but we draw the line at outright betas
We need to see what we can do to start leveraging CloudFlare too, especially now that HTTP/2 is starting to work. Both encryption and CF present issues or risks to how the site works because of socket.io so we have to be cautious.
-
I need to get in on this at some point
-
@scottalanmiller said:
@anonymous said:
@scottalanmiller When will you have a guide written for CentOS7? Will Mangolassi being using it?
We'll been Ubuntu for ML. The hope is to use it. Jared has actually done some work here to prepare. Yes, if at all possible, we plan to move to it, but not until it exits beta. We tend to run on "just released" here (OS, application, etc.) but we draw the line at outright betas
We need to see what we can do to start leveraging CloudFlare too, especially now that HTTP/2 is starting to work. Both encryption and CF present issues or risks to how the site works because of socket.io so we have to be cautious.
CloudFlare is working just fine for me with NodeBB behind an NginX proxy. I have a StartSSL cert on the proxy and nothing on the NodeBB instance itself.
-
I'm running LetsEncrypt @ my C@C Host. Works great so far!
