Hacker News Reader

Comment by thefreeman | Hacker News Reader

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

View on HN

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?

Same goes for Chromium 34.0.1847.116 on Arch.

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...

Using 34.0.1847.120

It's checked by default, just looked.

It's persistent for me.

I'm on 36.0.1941.0 dev-m.

35.0.1916.27 beta

The check is persistent.

Maybe we have an extension that is causing this. I'll try disabling them tomorrow and see if the UI works.

Reply on news.ycombinator.com