Re:Chrome users oblivious to Heartbleed revocation tsunami
by tombrossman on Saturday April 19, 2014 @10:55AM
(#7613548)
For Chromium version 33.0.1750.152 Ubuntu 12.04, The settings change is persistent.
Related question: Is anyone seeing degraded browsing performance as a result of this change yet? It is my understanding that these CRLs are spiking in size to multiple megabytes, no?
Re:Chrome users oblivious to Heartbleed revocation tsunami
by this_user on Saturday April 19, 2014 @11:24AM
(#7613618)
Same goes for Chromium 34.0.1847.116 on Arch.
Re:Chrome users oblivious to Heartbleed revocation tsunami
by seacious on Saturday April 19, 2014 @12:52PM
(#7613902)
Chromes ability to save settings silently fails with disturbing regularity (in my experience). A lot of people seem to have seen the issue (e.g. [1], and google will reveal many more) but consistent steps to reproduce seem hard to come by. It's one of the main annoyances that made me switch back to firefox.
[1] https://productforums.google.com/forum/#!topic/chrome/npSTSO...
Re:Chrome users oblivious to Heartbleed revocation tsunami
by xux on Saturday April 19, 2014 @11:37AM
(#7613660)
Using 34.0.1847.120
It's checked by default, just looked.
Re:Chrome users oblivious to Heartbleed revocation tsunami
by ryanpardieck on Saturday April 19, 2014 @12:28PM
(#7613806)
It's persistent for me.
I'm on 36.0.1941.0 dev-m.
Re:Chrome users oblivious to Heartbleed revocation tsunami
by chaosmonkey on Saturday April 19, 2014 @12:28PM
(#7613808)
35.0.1916.27 beta
The check is persistent.
Re:Chrome users oblivious to Heartbleed revocation tsunami
by crucialfelix on Saturday April 19, 2014 @08:37PM
(#7615306)
Maybe we have an extension that is causing this. I'll try disabling them tomorrow and see if the UI works.
I understand that the CRL isn't fool proof, but if your connection isn't in a position to be MITM'd it still provides protection against some things, for example if the target website DNS has been hijacked.
edit: 34.0.1847.116 m