> We pride ourselves on being an efficient organization. In 2018 Let’s Encrypt will secure a large portion of the Web with a budget of only $3.0M.<p>I sincerely hope that they don't become like Wikimedia with their ever-increasing scope and bureaucracy. And it might work because Let's Encrypt has a rather specific mission (free TLS certs for everyone), whereas Wikimedia has a rather broad mission (free knowledge/data for everyone).
Letsencrypt has made my live easier... So, don't forget to donate, if it helps you: <a href="https://letsencrypt.org/donate/" rel="nofollow">https://letsencrypt.org/donate/</a><p>Don't forget the past :)
> the Web went from 46% encrypted page loads to 67% according to statistics from Mozilla - a gain of 21% in a single year<p>No no no... That's a gain of 50% (give or take) or 21 percentage points; not a gain of 21%.
Are full ECDSA chains going to depend on the upcoming Let's Encrypt ECDSA root being in the client trust store or is there going to be cross-signing?
Funny trivia. Recently, our firewall was blocking a ton of smaller websites. Wasn't sure why. Finally got on the phone with Sophos (our firewall manufacturer) to figure out what was going on. Support guy led me through some troubleshooting steps, we discovered that it's blocking Lets Encrypt certificates for whatever reason. He agreed with me that's strange and he'll look into why Lets Encrypt is getting blocked. So strange. Not related to anything at all, just topical trivia.
I wonder why they do not user their own certificates?<p><a href="https://letsencrypt.org" rel="nofollow">https://letsencrypt.org</a> reports Identrust.
I know they are planning wildcard already (as per article), I'm just keeping my fingers crossed we will see code signing and others before too long...<p>I understand though, code signing will be much harder to automate and maybe not so fit for purpose...