Mozilla re-enables TLS 1.0 and 1.1 because of Coronavirus (and Google)
1–10 of 37 posts
Re: Mozilla re-enables TLS 1.0 and 1.1 because of Coronavirus (and Google)
#2We need back to HTTP because of Coronavirus.
Re: Mozilla re-enables TLS 1.0 and 1.1 because of Coronavirus (and Google)
#3And this highlights how Google and the Chrome ecosystem is strangling web tech. The fact they were afraid of making a move that isn't in lockstep with Chrome means Chrome has too damn much influence.
Re: Mozilla re-enables TLS 1.0 and 1.1 because of Coronavirus (and Google)
#4"We reverted the change for an undetermined amount of time to better enable access to critical government sites sharing COVID19 information."
This makes a lot of sense. Normally, browsers moving together to turn down an old and insecure protocol would push the last few sites to update, but with everything being a mess because of the coronavirus this isn't a good time.
(Disclosure: I work for Google)
Re: Mozilla re-enables TLS 1.0 and 1.1 because of Coronavirus (and Google)
#5Seems to indicate it wasn't as urgent to disable these as professed. I think browser vendors are sometimes a little too quick to break things, glad to see this pragmatism.
Re: Mozilla re-enables TLS 1.0 and 1.1 because of Coronavirus (and Google)
#6>"The preference change will be remotely applied to Firefox 74"
No thanks. How do they do this, and how do I stop people from being able to remotely "manage" my Firefox install?
Re: Mozilla re-enables TLS 1.0 and 1.1 because of Coronavirus (and Google)
#7I was in charge of ensuring the TLS 1.2 compliance of hundreds of old sites in my organization. 2 weeks ago I was well on track to have it finished in time. Now I'm tasked to just keep up essential systems that are straining under the work from home onslaught, with two suddenly homeschooled kids needing my support
I'm also so overstressed and worried that can only sleep on Xanax and have an asthma flare-up that looks like covid19 symptoms at times, adding to the anxiety.
This will be a good and needed change, but it can wait.
Re: Mozilla re-enables TLS 1.0 and 1.1 because of Coronavirus (and Google)
#8And this highlights how Google and the Chrome ecosystem is strangling web tech. The fact they were afraid of making a move that isn't in lockstep with Chrome means Chrome has too damn much influence.
Decade-old versions of TLS are flat-out bad for users. TLS 1.0 is from 1999!
The points of standards are to get the entire industry to adopt them. When the browser vendors come together and agree to all do the same thing, that's not one vendor flexing its muscles, that's standards working as intended.
Re: Mozilla re-enables TLS 1.0 and 1.1 because of Coronavirus (and Google)
#9We need back to HTTP because of Coronavirus.
Why? Is Let's Encrypt hospitalized with Coronavirus?