Re:Symantec Distrust in Firefox Nightly 63
by pietroglyph on Friday August 17, 2018 @05:42PM
(#17785704)
It's interesting that Firefox preserves the "Continue" button for affected sites, while Chrome does not. I get that we want to keep broken sites relatively accessible for a while, but I worry that we could also be teaching people to ignore warnings like these. I wonder if the continue button dissapears with HSTS…
Re:Symantec Distrust in Firefox Nightly 63
by abdullahkhalids on Friday August 17, 2018 @07:03PM
(#17785990)
Probably because Mozilla subscribes to the ethos that a user should get the final say in what computation gets done on their computer, and not some third party. I would be sad if they ever took the "continue" option away.
This is consistent with their position on drm in browsers.
Re:Symantec Distrust in Firefox Nightly 63
by aaronmdjones on Friday August 17, 2018 @07:07PM
(#17786003)
Firefox Nightly has the continue button regardless, but if the site has HSTS, it will tell you so, and will not allow you to add an exception; continue only shows the cause of the problem, in this case, that the certificate came from an untrusted source. This is in line with the "no user recourse" section of the HSTS RFC.
Re:Symantec Distrust in Firefox Nightly 63
by some_account on Saturday August 18, 2018 @05:11PM
(#17790729)
Users should get the final say always. This was normal behavior before windows 8. Now windows users are guests in their operating system, and the attitude can be seen in other software as well, not only from Microsoft.
Firefox is an awesome browser and is the most pro choice browser on the market, with options for privacy plugins, search engines, cookie choices, tracking protection, etc.
Re:Symantec Distrust in Firefox Nightly 63
by cat199 on Friday August 17, 2018 @06:57PM
(#17785972)
sounds like you've never needed to diagnose a broken cert before..
all of this nannying for the common good and breaking functionality is not always a good thing. provide sensible defaults and give the user control to override it as they see fit (like the continue button)
Re:Symantec Distrust in Firefox Nightly 63
by morganvachon on Friday August 17, 2018 @06:12PM
(#17785817)
Well, to get to the continue button you have to click once, then after you click continue you have a new dialog asking if you're sure you want to trust the certificate and whether you want to trust just for the session or permanently. It's not idiot-proof, but then nothing in software ever is.
Re:Symantec Distrust in Firefox Nightly 63
by phobosdeimos on Friday August 17, 2018 @08:00PM
(#17786171)
Personal responsibility? I have on occasion ordered things from websites who did not have their security in order. My conscious and informed decision. Although I did not order with a creditcard ofcourse.
Re:Symantec Distrust in Firefox Nightly 63
by sofaofthedamned on Friday August 17, 2018 @05:11PM
(#17785599)
Considering the PCWorld group in the UK have had to disclose a serious breach recently, plus they have not bothered to update their EV certs, i'd suggest their security isn't up to scratch and black hats will notice this.
Re:Symantec Distrust in Firefox Nightly 63
by sp332 on Friday August 17, 2018 @04:23PM
(#17785398)
Also accounts.intuit.com which affects various products e.g. Mint.
And an interesting comment from the thread:
Enforcement of this error can be disabled by setting security.pki.distrust_ca_policy to '1' in about:config. Changing the value back to '2' will re-enable this change.
This is consistent with their position on drm in browsers.
Firefox is an awesome browser and is the most pro choice browser on the market, with options for privacy plugins, search engines, cookie choices, tracking protection, etc.
all of this nannying for the common good and breaking functionality is not always a good thing. provide sensible defaults and give the user control to override it as they see fit (like the continue button)
And an interesting comment from the thread:
Enforcement of this error can be disabled by setting security.pki.distrust_ca_policy to '1' in about:config. Changing the value back to '2' will re-enable this change.
Similar schedule and post: https://security.googleblog.com/2018/03/distrust-of-symantec...
Sites like PayPal and Intuit, which should be on top of things related to security, have been non-responsive to my pings to fix it.