News for hackers. Stuff that matters.
Re:Entering Public Beta by necessity on Thursday December 03, 2015 @03:10PM (#10672227)
I'm a layman when it comes to secure websites and certificates. I remember reading that the "free https" provided by Cloudflare meant Cloudflare owned the private keys to something and was able to see all traffic. Is that the case with Let's Encrypt? Because if it is I don't see as an improvement at all.
Re:Entering Public Beta by pfg on Thursday December 03, 2015 @03:13PM (#10672249)
You create your own private key (or rather, the client does that for you, if you use the official one) and send them a Certificate Signing Request (CSR) which only includes your public key. The private key stays on your server.
Re:Entering Public Beta by ianlevesque on Thursday December 03, 2015 @03:13PM (#10672251)
It is not the case with letsencrypt
Re:Entering Public Beta by atonse on Thursday December 03, 2015 @04:28PM (#10672782)
No, you never send your private key to anyone, with any HTTPS certificate generating scheme.

All they do is sign your public key.

Re:Entering Public Beta by ge0rg on Thursday December 03, 2015 @05:21PM (#10673158)
At least you should not. StartSSL (and probably other CAs) has a prominent feature to create your key pair for you, which you need to skip to use a signing request. Always use the latter!