jaas

Fixed!

We didn't go with the 64-core chips because they have significantly lower clock speeds.

Dual 32-core chips give us plenty of cores while keeping clocks higher for single-threaded performance.

You are correct that the price of the CPUs is almost irrelevant to the overall cost of a system with this much memory and storage. We were picking the ideal CPU, not selecting on CPU price.

It's great that they took the time to write this up even though the conclusion is that it doesn't work.

Too much valuable information is lost because people don't value negative results enough.

Let's Encrypt & Prio Services (ISRG) | Full-time | 100% Remote (United States or Canada) | Software Engineer (SRE)

We’re looking for an additional software engineer for our Site Reliability Engineering (SRE) team. Maybe that’s you!

Our SRE team works on both Let's Encrypt and Prio Services. At any given time you may work on one or the other.

With Let's Encrypt, we’re making HTTPS easier for developers to use and we’re doing it at scale. We’re a first-of-our-kind Certificate Authority (CA). We make certificates available to anyone, for free, and we offer an API to do it. This means more people can enable HTTPS on their websites, with less work. That protects everyone’s web traffic from snoops, and makes us all safer.

With Prio Services, we're helping organizations collect the metrics they need while fully respecting user privacy.

https://www.abetterinternet.org/careers/isrg-sre-sw/

It's easy, we have no trouble at all. Training more is simple once you have one or two people with experience. No luck needed.

If a page doesn't use HTTPS, even if it is cats, you cannot trust that the traffic has not been modified in transit. You try to load a cat but a network attacker can add malware or mining code or a worse exploit.

Every page needs HTTPS because you can't trust any content sent to you over HTTP. You don't know if it's "just a cat picture."

The Intel chip in that comparison was released in Q1 2018, almost three years ago now. How is this a helpful comparison?

https://ark.intel.com/content/www/us/en/ark/products/130411/...

Let's Encrypt| letsencrypt.org | Software Engineer (SRE) | Remote (US or Canada) | Full-Time

We’re making HTTPS easier for developers to use, we’re doing it at scale, and we need your help. We’re a first-of-our-kind Certificate Authority (CA). We make certificates available to anyone, for free, and we offer an API to do it. This means more people can enable HTTPS on their websites, with less work. That protects everyone’s web traffic from snoops, and makes us all safer.

More details here:

https://www.abetterinternet.org/careers/le-sre-sw2/

To apply, please submit your resume to: careers@letsencrypt.org

EFF is a strong supporter but Let's Encrypt is not an EFF project. Let's Encrypt is owned and run by Internet Security Research Group:

https://www.abetterinternet.org/

Chuck Feeney is not "officially broke." Per this story he has a couple million set aside for retirement and is living a perfectly happy life with all of his needs met. It seems disrespectful to Feeney's vision for his own life - he can give away so much and still be fine. Not broke.

I don't know why the author had to cross the line into falsehood with the title. It's a great story about a great person, why sacrifice your integrity with an utterly false headline, particularly when the story doesn't need it?

Because she's a U.S. Senator who may be the Vice President soon. That's why people care, even if you don't. You know that already so please spare us the personal commentary masked as a question.

I see a couple of replies saying something like "plain HTTP [still] works fine."

Sure, it works in the sense that most of the time the page will load as expected, but it's not safe or reliable. I don't want our standard for technology to be that it "works" for some shoddy definition of works - I want it to be safe and reliable. Plain HTTP is neither safe nor reliable.

Even if you don't care about the privacy benefits of HTTPS, plain HTTP can be modified. This means that when you load an HTTP page you cannot be confident that what you're seeing is what the server sent. The content could have been manipulated, ads or malicious script could have been inserted. This has been exploited in real world attacks many times.

Sites that do not use HTTPS put their users at risk during every page load because the users are forced to load content that can be tampered with. Paul Graham (and everyone else using plain HTTP for their site) should not be putting their users at risk like this. All sites should use HTTPS.

I don't understand what you're asking for. Can you explain?

Just to be a little more clear - I believe the original lock-in agreement with GF has expired, but they negotiated a new one. So they have an agreement about chip purchasing, but they aren't still in the agreement from the spinoff.

Let's Encrypt| letsencrypt.org | Senior Software Engineer | Remote (US or Canada) | Full-Time

We’re making HTTPS easier for developers to use, we’re doing it at scale, and we need your help. We’re a first-of-our-kind Certificate Authority (CA). We make certificates available to anyone, for free, and we offer an API to do it. This means more people can enable HTTPS on their websites, with less work. That protects everyone’s web traffic from snoops, and makes us all safer.

More details here:

https://www.abetterinternet.org/careers/le-sr-sw-eng/

To apply, please submit your resume to: careers@letsencrypt.org

Yes it does. Quantum is not new from scratch, it's (excellent) improvement and reorganization of largely the same code base. Some code and components are new, but that's rare all in all.

It says "for personal reasons," which is not text I would expect if he was just going to another company.

But hopefully you care about one much, much more than the other. They are not comparable in terms of needing discussion at this moment in history.

(Edit: In the event that you honestly don't know which one is the more important topic, right now or pretty much any other time - police frequently murdering black people or some store windows getting smashed and merch stolen - it's the police murdering black people.)

Yes, most roads should be toll roads. The benefits to society would be enormous.

Let's Encrypt | Senior Software Engineer | Full-time | REMOTE from U.S. or Canada

We’re making HTTPS easier for developers to use, we’re doing it at scale, and we need your help. We’re a first-of-our-kind Certificate Authority (CA). We make certificates available to anyone, for free, and we offer an API to do it. This means more people can enable HTTPS on their websites, with less work. That protects everyone’s web traffic from snoops, and makes us all safer.

https://www.abetterinternet.org/careers/le-sr-sw-eng/

No there aren't. All HTTP traffic can be modified, which means it can deliver any malicious payload to the server or client. It's dangerous not to use HTTPS, period.

Head of Let's Encrypt here.

We have an on-call rotation and a system for getting others notified and online quickly when necessary. We make sure not to bring too many people online so that some people are fresh and can rotate in later if the incident lasts longer.

It's not often that staff have to put in time at night or on weekends, and when it happens we work hard to make sure the problem doesn't happen again.

Probably because it includes pre-certificates. I have to run so I don't have time to explain, but basically at a certain point we started submitting each certificate twice, the first one being a "pre-cert." You can probably Google for more info.

It's surprisingly hard to tell which certificate was the billionth issued. You'd have to decide on a source of truth, and CT is probably not a good one for this purpose. Submissions to CT are not necessarily made and processed in issuance order. The goal is to get all certs into CT as quickly as possible, but ordering isn't particularly important (maybe one submission from our CA starts a second before another but the network request is delayed until after the second one).

At the heart of things, our certificate signing infrastructure includes multiple HSMs, each one with multiple signing cores. This means that we're signing certificates in parallel all the time.

The signed certificates are inserted into our internal database in a serialized order, but due to how we optimize our database it's not easy for us to just ask "what is the billionth one." That kind of query is usually not a very useful one for us to make.

This is correct. We currently serve about 195 million websites, where website is defined as a unique Fully Qualified Domain Name.

"If you looked at that table and went like "Oh, just 0.2% for me, great! No need to worry!" you are a terrible person."

Or, with a bit more empathy, they just haven't put it in the right context yet.

Any death from this is unfortunate, but many things can kill you and many people have accepted a low mortality percentage for lots of things. They may just initially perceive that smallish number as another one among many (e.g. the normal flu, biking). It may be a big number compared to other stuff, but it looks small and I can see how people might be dismissive. That doesn't make them terrible people, they just don't (yet?) have the perspective that you do.

If operating systems had taken care of the problem already then Mozilla might not have to. I'm glad Mozilla isn't waiting around for them to protect my privacy.

It doesn't "resolve" BGP attacks. The point is an attacker would have to pull off three or four successful attacks at once, which is harder than pulling off just one, especially if they hope to go unnoticed.

The blog post is probably more understandable and relevant for readers here:

https://letsencrypt.org/2020/02/19/multi-perspective-validat...

Maybe we can get the link changed?

This math is off because the vast majority of Silver sponsors are at $10k, and some of the sponsors at all levels are in-kind, meaning we get something other than cash from them.

In 2019 we spent $3.35M in cash (we came in a little under our projected budget of $3.6M). We raised $3.82M in cash between sponsors, grants, and individual giving.