Podcast
Root Causes 79: Firefox Reinstates Support for Deprecated TLS Versions
Hosted by
Jason Soroko
Fellow
Original broadcast date
March 30, 2020
To enable broadest possible access to valuable information about the COVID-19 epidemic, Firefox has chosen to reinstate support for web sites using TLS 1.0 and 1.1. Join us to learn about this move, why Firefox has made it, and what that says about the state of web site security today.
Podcast transcript
Lightly edited for flow and brevity.
TCTim CallanSo, we're going to discuss a recent news item that, you know, sometimes there are breaking events in the world of PKI and we want to get them while they're going on, just report what they are and offer a little color and the news item today, this actually, the original article that I spotted was from March 20, in Bleeping Computer and the gist of it is that Firefox, which had deprecated its support for old versions of TLS, TLS 1.0. and 1.1, has decided to re-enable that support, to re-allow those versions to work in Firefox, and the reason for that is it turns out that apparently, and I didn't know this, a large number of important and valid COVID-19 information resources, especially from government, are still using those old versions of TLS and the Firefox team has decided that it's more important to give people access to that information then it is to deny the security flaws that exist with those old versions of TLS. So, interesting development, not something I would have anticipated and what do you think of that, Jay?
TCTim CallanThere are for sure. You know and it was - - I don't think either of us disagrees, that it was the right thing to do for Firefox to get rid of those, like in a normal world.
TCTim CallanAnd part of what the browsers recognize is, to some degree, things like old security protocols won't ever go away until they force them to. Right? That that stuff will always exist out there in the wild until the browsers say, you know what, I'm just going to make your website stop resolving. And so. they recognize that that's one of the things that they do, it's one of the roles they play in the ecosystem. And so, they were moving on, you know, what everyone thought was a very reasonable path to do that. And I, you know, and I get your point, which is, on the one hand, yes, we do want to give people information that, you know, access to information. But on the other hand, the security vulnerabilities didn't suddenly go away and knowledge of those security vulnerabilities among the people who would exploit them for bad ends, didn't suddenly go away, either.
TCTim CallanYeah, it's disappointing and alarming, right? I mean, government sites, do lots of critical things. And, you know, government has a lot of information, right? Like, they're the people who have everybody's tax records. Um, it's not a good group to turn out to be, you know, in the back of the class in terms of IT security.
TCTim CallanYeah. I mean - - and that would be I get all of that. I guess the question I would ask is, at the end of the day, though, I mean, is there really a material cost difference in serving TLS, 1.2, or 1.3, as opposed to 1.1? Like, does that mean that you're running old hardware or old server OS that's incapable of running those? Is that why that happens? And if so, what other security vulns are sitting in there?
TCTim CallanYeah.
TCTim CallanYeah.
TCTim CallanYeah.
TCTim CallanYeah. So, agreed on all of that and, you know, maybe that's really the long and the short of it, you know, I thought we were gonna start out talking about Firefox, and we're mostly talking about why did this even have to happen in the first place? I think Firefox, it feels like Firefox did the right thing and made the right choice. Right? And surely, they'll reinstitute those blocks later down the road and surely that'll be trivially easy for them to do when the time comes.
TCTim CallanYep.
TCTim CallanYeah, yeah. I mean, this certainly was one of those lesser evil situations for Firefox and, you know, but yeah, it does bring - - it does highlight something that's got to be fixed down the road for sure.
TCTim CallanI haven't, you know, I was thinking about that exact question while we were talking. I haven't seen an announcement from anyone else, but then the other thing is, I'm not sure the other browsers got around to deprecating that support yet. In which case, maybe they just put the brakes on that, you know, everybody was planning to, but oftentimes we see Firefox leading the way on this kind of thing. And so, it wouldn't be surprising if Firefox were the first one to put that into effect. And if that's the case, then it might be that the other major browsers who intended to do that had a, you know, sprint on the roadmap for that this year, just kind of said, well, you know, put a hold button on that for now. And we’ll do that when it makes sense. That's worth a little bit of looking into, but that couldn't be how it all went down.
TCTim CallanI love it.
TCTim CallanI love it. So, we'll do that for a future podcast and think this is a good place to leave this today. So, thank you, Jay, for the insights.
TCTim CallanThank you, Listeners. This has been Root Causes.