From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Is this a bug in firefox-36.0?
Date: Fri, 20 Mar 2015 22:37:59 -0500 [thread overview]
Message-ID: <20150320223759.163e02de@sepulchrave.remarqs> (raw)
In-Reply-To: meidcg$cp5$1@ger.gmane.org
On Fri, 20 Mar 2015 17:18:23 -0700
walt <w41ter@gmail.com> wrote:
> On 03/19/2015 05:15 PM, »Q« wrote:
> >> 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.
>
> > Why didn't you say so? ;)
> >
> > Enter "about:config" in the address bar, search for
> > "security.OCSP.require" and toggle it to false, which is the default
> > (Mozilla's shipped default, at least).
>
> Very interesting, thanks.
>
> Now that I have an expert's brain to pick :) maybe you can answer two
> more questions for me:
>
> I know I didn't change that flag myself, but something did. Do you
> know if firefox extensions/addons can change the items in
> about:config?
I won't cop to being an expert! But yes, extensions can change
settings, and AFAIK if/when that happens there is no way to tell what
extension has done what to them. If an extension changed that
particular setting, I'd guess it would be an extension meant to tighten
security.
> Second, I "fixed" the problem once by rebooting my wireless router,
> but got the same error again early this morning -- which I "fixed"
> once again by rebooting my wireless router. This makes me worry that
> somebody out there in the evil internet might be changing the
> security settings of my router (which is owned by my ISP and has
> remotely updateable firmware).
Sorry, I have no idea how to investigate that.
next prev parent reply other threads:[~2015-03-21 3:38 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
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« [this message]
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=20150320223759.163e02de@sepulchrave.remarqs \
--to=boxcars@gmx.net \
--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