On Thursday, March 19, 2015 3:57:05 AM walt wrote: > On 03/18/2015 06:06 PM, Fernando Rodriguez wrote: > > On Wednesday, March 18, 2015 4:41:25 PM walt wrote: > >> On 03/17/2015 04:49 PM, walt wrote: > >>> I get a certificate verification error when visiting https://www.att.com > >>> using firefox-36.0, but not when using chrome-41.0.2272.76. > >> > >> Thanks to all who replied. I'm surprised by the variety of different results > >> you reported. > >> > >> (BTW, I'm running firefox-bin-36.0, so the behavior may be a bit different > > from > >> the gentoo build.) > >> > >> FF will not even show me the secure att.com webpage. I get an entire html > > page > >> with this (very big) error message: > >> > >> Secure Connection Failed > >> > >> An error occurred during a connection to www.att.com. The OCSP server > > experienced > >> an internal error. (Error code: sec_error_ocsp_server_error) > >> > >> The page you are trying to view cannot be shown because the authenticity of > > the > >> received data could not be verified. > >> > >> Please contact the website owners to inform them of this problem. > >> > >> > > > > That sounds more like a networking issue. Are you behind a firewall? Is it > > possible that you somehow blocked their OCSP server? Can you bypass the > > firewall for testing? > > Wow, creepy. I forced a warm reboot of my home wireless router and the problem > went away. I now see the gray triangle with the ! and I have no idea how long > ago that started. I probably just didn't notice it until this router screw- up > happened. And I don't even want to think about why my home router suddenly > changed behavior :(
It probably started Jan 20 when they renewed the certificate. See http://www.certificate-transparency.org/ev-ct-plan (from Mick's link). It refers to chrome but probably applies to firefox as well. -- Fernando Rodriguez
signature.asc
Description: This is a digitally signed message part.
