Let's Encrypt: How It Works

Re:Let's Encrypt: How It Works by grecy on Friday November 21, 2014 @01:08PM (#8642452)

Sorry for the newbie question....

So if I have apache running http://example.com on port 80 and I follow the instructions ($ lets-encrypt example.com)

Will Apache now be correctly serving encrypted traffic on port 443 with a cert for https://example.com ?

[ Parent | on HN ]

Re:Let's Encrypt: How It Works by bifurcation on Friday November 21, 2014 @02:32PM (#8642899)

The ultimate vision is to make it even easier than that -- you set the "turn on HTTPS" option, and the platform auto-configures HTTPS with a certificate and appropriate ciphers. That will require upgrades to apache, nginx, IIS, etc., though, so in the meantime, we have the "lets-encrypt" script to semi-automate things.

[ Parent | on HN ]

Re:Let's Encrypt: How It Works by ivok on Friday November 21, 2014 @06:01PM (#8643903)

So going from a single command to a different single command? How much simpler could it get?

[ Parent | on HN ]

Re:Let's Encrypt: How It Works by haroldp on Friday November 21, 2014 @01:15PM (#8642478)

That's the idea. It assumes you are using an OS with a package manager, and letting it manage your software and (to some extent) config files.

[ Parent | on HN ]

Re:Let's Encrypt: How It Works by st3fan on Friday November 21, 2014 @01:49PM (#8642629)

And if you don't, or if you don't want to, it is easy to configure Apache or any web server manually.

All you really need are three things:

* the letsencrypt command line tool that will do the API dance to request the certificate

* a file in your web site root with a ownership verification token or a DNS record with said token

* a configuration file snippet for your server

I'm sure all of this will be documented very well.

[ Parent | on HN ]

Re:Let's Encrypt: How It Works by grecy on Friday November 21, 2014 @02:32PM (#8642898)

Nice, thanks. (I'm running on Ubuntu, so should be good)

[ Parent | on HN ]