3 ms·
Sometimes I still browse Digg (it's different now). Since the last Firefox update from a week ago which disabled Symantec certificates the site doesn't work any
by 21 8y ago
Sometimes I still browse Digg (it's different now). Since the last Firefox update from a week ago which disabled Symantec certificates the site doesn't work anymore. I bet the day Chrome disables Symantec certificates they will immediately notice and fix it.
It's sad that in one week not even one of their people opened it in Firefox, and not many of their users either (there was just a couple of mentions on Twitter about this issue)
- chrisseaton 8y ago> Since the last Firefox update from a week ago which disabled Symantec certificates the site doesn't work anymore. Is this the fault of Firefox or Digg though?
- m3talsmith 8y agoIt's pointing out the mindshare and impact that Chrome has.
- ryuuchin 8y agoChrome distrusted Symantec certs when 70 got pushed to stable (at the end of October)[1]. Digg shows NET::ERR_CERT_SYMANTEC_LEGACY error when I navigate to it. Firefox was supposed to remove the Symantec certs in 63 (also to be released at the end of October) but I guess they pushed it back a version[2]. All major browser coordinated to distrust the certs at the same time. [1] https://security.googleblog.com/2017/09/chromes-plan-to-distrust-symantec.html https://security.googleblog.com/2017/09/chromes-plan-to-dist... [2] https://blog.mozilla.org/security/2018/07/30/update-on-the-distrust-of-symantec-tls-certificates/ https://blog.mozilla.org/security/2018/07/30/update-on-the-d...
- lern_too_spel 8y agoChrome also shows an error. The reason nobody at Digg noticed is that Digg is not https by default, so only people using certain extensions would hit that error.