public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fernando Rodriguez <frodriguez.developer@outlook.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Is this a bug in firefox-36.0?
Date: Thu, 19 Mar 2015 11:29:57 -0400	[thread overview]
Message-ID: <50972182.mg828J0U53@navi> (raw)
In-Reply-To: <meea22$hvg$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1946 bytes --]

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

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-03-19 15:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 23:49 [gentoo-user] Is this a bug in firefox-36.0? walt
2015-03-18  0:47 ` Daniel Frey
2015-03-18  1:15   ` [gentoo-user] " walt
2015-03-18  2:34     ` Daniel Frey
2015-03-18 19:42   ` »Q«
2015-03-18  1:07 ` [gentoo-user] " Zhu Sha Zang
2015-03-18  3:53 ` Fernando Rodriguez
2015-03-18  6:56   ` Mick
2015-03-18  4:48 ` Fernando Rodriguez
2015-03-18 23:41 ` [gentoo-user] " walt
2015-03-18 23:46   ` Daniel Frey
2015-03-19  1:06   ` Fernando Rodriguez
2015-03-19 10:57     ` walt
2015-03-19 15:29       ` Fernando Rodriguez [this message]
2015-03-19  7:26   ` Marc Joliet
2015-03-20  0:15   ` »Q«
2015-03-21  0:18     ` walt
2015-03-21  3:37       ` »Q«
2015-03-24  6:52         ` Mick
2015-03-24  9:36           ` Peter Humphrey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50972182.mg828J0U53@navi \
    --to=frodriguez.developer@outlook.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox