jaas

22 ms·

241.
by jaas 10y ago
We had a better word for it at Mozilla: deCOMtamination
242.
by jaas 10y ago
We just added the PayPal button back to letsencrypt.org, it's near the bottom of each page now.
243.
by jaas 10y ago
We just added the PayPal button back to our site, it's near the bottom of each page now.
244.
by jaas 10y ago
Thanks for your support! I'd also like to point out that even if you never get a certificate from us yourself we're still helping to protect you when you browse any of the millions of sites we help to secure.
245.
by jaas 10y ago
Diversifying income is something every responsible non-profit should be doing, and that's what this is. If I were you I'd be more worried if we didn't do something like this. The bulk of our support comes from corporate spons
246.
by jaas 10y ago
I think you're missing a number of important things here. We operate on a pretty small budget for what we provide. I doubt you'd be happy with a CA that operated with a smaller budget. 1) Our software is already open source. That
247.
by jaas 10y ago
We have a lot of email addresses provided for certificate accounts but we'd prefer to use them only when necessary, because that's what people had in mind when they gave them to us. When we collect email addresses via marketing ef
248.
by jaas 10y ago
That's where we'd like to see things go as well. Same for Apache. -Josh, head of Let's Encrypt
249.
More than 50% of page loads were encrypted with HTTPS yesterday(twitter.com)
1 points by jaas 10y ago|0 comments
250.
by jaas 10y ago
You probably have to restart because the web rendering engine (WebKit) used by your browser (Safari) is used all over the rest of the system as well (in webviews). Just a guess though.
251.
by jaas 10y ago
It is ten (I made the budget), but I apologize for not making that more clear in the blog post. We have eight employees now, and have budgeted for ten in 2017.
252.
by jaas 10y ago
The 2M staffing budget in 2017 is for ten people, not eight. Was not clear enough in the blog post initially, apologies.
253.
by jaas 10y ago
Going to repeat this comment here since people are doing the math: That's for ten employees, not eight. Salary + benefits. Could have been more clear in the post initially, but we have eight employees now and have budgeted for ten in 2
254.
by jaas 10y ago
That's for ten employees, not eight. Salary + benefits. Could have been more clear in the post, but we have eight employees now and have budgeted for ten in 2017.
255.
by jaas 10y ago
We have been working on Blackberry 10 support for a while. While we can't commit to a date yet, we have good reason to believe that your issue will be solved with a software update soon.
256.
by jaas 10y ago
Let's Encrypt | Remote (US & Canada) | FULLTIME | Systems Administrator https://letsencrypt.org/jobs/ In the past year our operations team has built the infrastructure needed to operate a secure, high availabi
257.
by jaas 10y ago
This is a pretty misleading title for a couple of reasons: 1) WoSign may face revocation (I doubt it but I don't know), but there is no evidence of that in this article. This is just one person not affiliated with a root program "
258.
by jaas 10y ago
HSM signing capacity is not infinite, and HSMs are expensive, but the real issue is just general DOS attacks. We aren't anywhere near our HSM capacity at the moment. It's easy to set up tons of subdomains and request gobs of certs
259.
by jaas 10y ago
Yeah, I hear that frequently and I get it. The important thing, really, is that you have a cert and that you deploy HTTPS. If you can afford it and it's what you need to do to deploy HTTPS, then whether or not you get your cert from Le
260.
by jaas 10y ago
Regarding your experience getting and managing certificates, I'm sorry to hear that you're having a difficult time. Our goal is to encrypt the entire Web, and that means working with an almost innumerable combination of operating
261.
by jaas 10y ago
We could very easily make the cert lifetimes one year, or anything else. We chose 90 days for the reasons outlined here: https://letsencrypt.org/2015/11/09/why-90-days.html Additionally, long cert lifetimes a
262.
by jaas 10y ago
We have also applied to the Apple, Microsoft, Oracle, Blackberry, and Google root programs. We had hoped to be accepted by all major programs by the end of this year, but even if that happened it would still take years for our root to suffi
263.
by jaas 10y ago
Just to clarify re: the DCs - they did/do support IPv6, but actually getting the addresses we needed provisioned was kind of a pain. That was a blocker for a bit. There were some other factors on our side that contributed to the delay
264.
by jaas 10y ago
It's clearly not just Let's Encrypt doing this, though I think Let's Encrypt is contributing a lot in terms of both issuance and changing expectations. Let's Encrypt is up to almost 4.5M active certificates now, and I ha
265.
by jaas 10y ago
There are some good reasons not to use it. Primarily the lack of API stability and that, as you mention, the people making it caution against it. But to answer your question, why would someone choose to use it anyway? One reasonable justifi
266.
by jaas 10y ago
We do, in limited cases for large providers (we can only handle so many requests), adjust rate limits. Such adjustments are never dependent on sponsorship, though sponsorship is nice.
267.
by jaas 10y ago
Head of Let's Encrypt here. Our automated mail system had a bug that accidentally exposed about 1.9% of subscriber email addresses to the same 1.9% of recipients. Our sincerest apologies for this mistake. We will be doing a thorough po
268.
by jaas 10y ago
"Given that IdenTrust grew from "<0.1%" to 5.6% since the launch of Let's Encrypt, and the shape is roughly the same as https://letsencrypt.org/stats/ , I strongly suspect that the 5.6% market sh
269.
by jaas 10y ago
"I think these audits are released to the public as I remember Let's Encrypt doing so, but that may just be because i) they aren't a full blown directly browser trusted CA or ii) LE just decided to do so as it fits their etho