2 ms·
>This worked well and was easy because Cloudflare could manage the certificates and connection security from incoming browsers. As a result of that work, the nu
by LEisthereason 2y ago
>This worked well and was easy because Cloudflare could manage the certificates and connection security from incoming browsers. As a result of that work, the number of encrypted HTTPS connections on the entire Internet doubled at that time. However, the connections made from Cloudflare to origin servers still required manual configuration of the encryption modes to let Cloudflare know the capabilities of the origin.
Is Cloudflare actually trying to take credit for Let's Encrypt or am I misunderstanding what they're trying to say here?
- javawizard 2y agoThe work they're talking about in that sentence[0] launched ~2 months before Let's Encrypt was publicly announced, and almost a year before Let's Encrypt signed their first certificate. So no, this was a separate effort. [0] https://blog.cloudflare.com/introducing-universal-ssl#:~:text=we%27ll%20have%20doubled%20that https://blog.cloudflare.com/introducing-universal-ssl#:~:tex...
- prdonahue 2y agoYou’re misunderstanding. LE went GA in April 2016 and Cloudflare is talking about ~2 years prior to that (where they used GlobalSign and Comodo, not LE).