jaas

20 ms·

181.
by jaas 8y ago
We provide multiple options, including PayPal. The primary option here uses Stripe via DonorBox: https://letsencrypt.org/donate/
182.
by jaas 8y ago
Word is Nvidia overproduced and is sitting on a lot of current gen stock. Miners bought AMD because AMD cards are usually better at mining for the money. They started buying more Nvidia when AMD didn't make enough cards. In any case th
183.
by jaas 8y ago
I think the answer is that low-interest car loans often come from a finance arm of the auto maker. I once got a 0% loan from Volkswagen to buy a Volkswagen. Seems like a way for them to sell more cars to people with good credit who will alm
184.
by jaas 8y ago
The strategy is/was to do both. We started getting our root into browsers immediately and we sought out a cross-sign to let us operate while the ~7-10 year root inclusion and propagation process happens.
185.
by jaas 8y ago
IdenTrust was initially part of a bank consortium, but by the time we (Let's Encrypt) started talking to them they were just an independent company. Now IdenTrust is a division of HID Global via acquisition.
186.
by jaas 8y ago
We switched the Let's Encrypt website from Jekyll to Hugo. We did it primarily for i18n support (Jekyll does not support translation), but it would have been worth it just to avoid Jekyll's ruby dependency nightmare. Hugo is a sin
187.
by jaas 8y ago
I think this is the best answer to your question: https://www.youtube.com/watch?v=QO15S3WC9pg
188.
by jaas 8y ago
So if someone deployed SSLv3 when it was the secure version and left that running for decades, you would describe this as proper and an ideal scenario that we should strive for? I sure hope that's not a lesson we learn in any decade.
189.
by jaas 8y ago
I am not a lawyer or particularly well informed on the subject, but I believe the SCOTUS case you're referencing only applies to public sector unions (i.e. government employees).
190.
by jaas 8y ago
It's not useful, it's grossly misleading. People think it means the site is safe when that is not the case.
191.
by jaas 8y ago
The problem with the lock is that people think it means a site is safe (i.e. contents are safe). That's not what it means and you're never going to educate enough people about what it really means, nor should you have to. It'
192.
by jaas 8y ago
If you enable it you will find that the results are very blurry. It's unusable, to me.
193.
by jaas 8y ago
I'd say there is a 98% chance this is a bug in some firmware and a 2% chance AT&T is intentionally trying to block Cloudflare DNS. I get why people are paranoid about ISPs blocking content and net neutrality, but let's not cry
194.
by jaas 8y ago
Let's Encrypt does not currently validate from multiple perspectives but we're working on it. We're cooperating with a research team at Princeton to make sure our strategy is an effective mitigation against BGP attacks. Any g
195.
by jaas 9y ago
Wildcards are only available via ACMEv2. The post linked to here says that.
196.
by jaas 9y ago
It didn't take us years to implement. We didn't internally decide to support wildcards until around May 2017 - it wasn't a foregone conclusion that we would ever support them. We didn't start technical work on wildcards
197.
by jaas 9y ago
The reason we haven't announced an EOL for ACMEv1 is that we won't announce one until we are confident we won't cause the kind of meltdown you describe.
198.
by jaas 9y ago
I worked down the hall from the XFS team at SGI in 2005. Development had definitely not ceased, and their work did not seem heavily related to Octane systems. They were focused on XFS for Suse and RedHat Linux for enterprise and supercomput
199.
by jaas 9y ago
"it's a race to the bottom for CAs to perform the absolute minimum work necessary" I can assure you that we, Let's Encrypt, are not doing the minimum. We are headed in quite the opposite direction. It's not easy to
200.
by jaas 9y ago
I hope it's not overly pedantic to point out that what you linked to is not a CAB forum thread. That's a thread on the Mozilla security policy list, which many root programs and CAs make use of for disclosure and discussion. CAB f
201.
by jaas 9y ago
According to the article the cache was found in 1992.
202.
by jaas 9y ago
We've now posted more details about the issue and our plans. https://community.letsencrypt.org/t/2018-01-09-issue-with-tl...
203.
by jaas 9y ago
Haven't put much thought into -02 since nobody actually runs it in production but I suspect the same issue applies.
204.
by jaas 9y ago
Josh from Let's Encrypt here. I'm not able to give many more details yet, but here's what I can add now: 1) This isn't a relatively simple issue like a bug in our CA code would be. It's an interaction between the pr
205.
by jaas 9y ago
Let's Encrypt | REMOTE FULLTIME | letsencrypt.org Let’s Encrypt is a free, automated, and open Certificate Authority. Please submit resumes to: it-jobs@linuxfoundation.org Systems Administrator Our operations team has built the infrast
206.
by jaas 9y ago
Good point, thanks. We just pushed a fix for that language, should show up live shortly.
207.
by jaas 9y ago
It's possible, but a couple of points to consider: 1) Wildcards may have a net negative effect on total issuance if subscribers who were getting many non-wildcard certificates before replace them with a single wildcard. I'm not su
208.
by jaas 9y ago
We set that up before we were an operational CA and it has just never been a high enough priority to replace it. The team that would do it has a lot of other things to do. We'll get around to it at some point.
209.
by jaas 9y ago
Good question. We are hoping to have a cross-sign from a widely trusted ECDSA root in place. It's non-trivial to make that happen, and it's part of the reason this feature is taking longer than we had hoped.
210.
by jaas 9y ago
Let's Encrypt | REMOTE | https://letsencrypt.org/ Please submit resumes to: it-jobs@linuxfoundation.org Systems Administrator Our operations team has built the infrastructure needed to operate a secure, high availabili

More ›