Re:Chrome users oblivious to Heartbleed revocation tsunami
by thefreeman on Saturday April 19, 2014 @10:25AM
(#7613489)
Wow, you are right. I was chuckling to myself looking at this article thinking Good thing I am smart and enabled this check. Then I read your comment, checked my settings and indeed the setting is no longer enabled.
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
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.
Re:Chrome users oblivious to Heartbleed revocation tsunami
by lowmagnet on Saturday April 19, 2014 @10:46AM
(#7613531)
Mine's still ticked after setting it last week.
Same version you've got, on mac.
Re:Chrome users oblivious to Heartbleed revocation tsunami
by crucialfelix on Saturday April 19, 2014 @08:35PM
(#7615303)
I'm on OS X too. Possibly could be an extension messing with it. That's usually what causes behavior that not everybody else sees on the same release version.
Some above in the comments have confirmed what I saw.
Re:Chrome users oblivious to Heartbleed revocation tsunami
by manish_gill on Saturday April 19, 2014 @12:05PM
(#7613733)
Yep. Check still working on same version for OS X.
Re:Chrome users oblivious to Heartbleed revocation tsunami
by ballpoint on Saturday April 19, 2014 @11:05AM
(#7613579)
Same here.
Re:Chrome users oblivious to Heartbleed revocation tsunami
by Atroxide on Saturday April 19, 2014 @10:31AM
(#7613500)
Maybe with news of Heartbleed a chrome update happened which forces chrome to check for revocations? Might just be a UI issue with showing it as an option and could be always on. Is there any way to test if it does indeed do the check?
Most likely not though. in the Dev branch its fixed and I was able to turn it on.
Does anybody else see this ?
Chrome Version 34.0.1847.116
I've reported it twice now.