From: Daniel Frey <djqfrey@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Is this a bug in firefox-36.0?
Date: Tue, 17 Mar 2015 17:47:04 -0700 [thread overview]
Message-ID: <5508CB08.4010005@gmail.com> (raw)
In-Reply-To: <meaej3$h3p$1@ger.gmane.org>
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.
>
> Anyone else see the same with firefox-36?
I haven't tried, honestly. But I have had problems with Firefox not
including some intermediary certificates before. That breaks the whole
chain of trust.
> BTW, I tried the latest firefox in a Win7 virtual machine and I was
> shocked to see that firefox was updating itself when I was logged in
> as an unprivileged user (i.e. *not* an Administrator). Are the idiots
> at M$ *really* that stupid? They've learned nothing, apparently, since
> Win 95 :(
Remove the 'Mozilla Maintenance Service' from Programs & Features (or
whatever it's called) and it won't auto update. Mozilla installs a
privileged service that auto updates its software.
Dan
next prev parent reply other threads:[~2015-03-18 0:47 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 [this message]
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«
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=5508CB08.4010005@gmail.com \
--to=djqfrey@gmail.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