From: lee <lee@yagibdah.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] broken seamonkey :(
Date: Sun, 06 Sep 2015 15:18:26 +0200 [thread overview]
Message-ID: <87twr7it3x.fsf@heimdali.yagibdah.de> (raw)
In-Reply-To: <201509052324.43538.michaelkintzios@gmail.com> (Mick's message of "Sat, 5 Sep 2015 23:24:28 +0100")
Mick <michaelkintzios@gmail.com> writes:
> On Saturday 05 Sep 2015 22:40:09 Fernando Rodriguez wrote:
>>
>> Since it lets you open the exception dialog but just hangs when downloading
>> the certificate I wonder if it has something to do with your OCSP settings.
>> Check that they match mine:
>>
>> security.OCSP.GET.enabled false
>> security.OCSP.enabled 1
>> security.OCSP.require false
>>
>> everything else is true.
>
> Some reports mention a couple of workarounds which may solve this problem:
>
> 1. Remove your certificate from *any* tabs that may have been saved in. Check
> that it is no longer stored in any tab.
>
> Then try to reload it in the Authorities tab and see if it will allow you to
> set up an exception.
>
> 2. I think you mentioned that you tried a fresh profile, but just in case:
> Make a back up of your Mozilla Profile. Go to Help/Troubleshooting and select
> Refresh Firefox (or the equivalent for the SeaMonkey GUI).
I moved ~/.mozilla out of the way, imported the certificate under
authorities, gave it all trust, and I'm getting exactly the same as
before when trying to connect: The dialog to add an exception comes up,
with the buttons to add one disabled, and clicking on "Get Certificate"
does nothing.
--
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us. Finally, this fear has become reasonable.
next prev parent reply other threads:[~2015-09-06 14:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 19:53 [gentoo-user] broken seamonkey :( lee
2015-09-03 20:10 ` Fernando Rodriguez
2015-09-03 23:39 ` lee
2015-09-04 0:08 ` Fernando Rodriguez
2015-09-04 1:23 ` Dale
2015-09-04 7:54 ` Peter Weilbacher
2015-09-04 10:43 ` Mick
2015-09-04 19:50 ` lee
2015-09-04 20:25 ` Fernando Rodriguez
2015-09-04 23:05 ` lee
2015-09-05 0:43 ` Fernando Rodriguez
2015-09-05 12:06 ` lee
2015-09-05 1:08 ` Fernando Rodriguez
2015-09-05 10:14 ` Mick
2015-09-05 16:22 ` lee
2015-09-05 17:16 ` Mick
2015-09-06 14:29 ` lee
2015-09-06 18:35 ` Mick
2015-09-12 11:54 ` lee
2015-09-06 19:17 ` Fernando Rodriguez
2015-09-13 14:23 ` lee
2015-09-05 13:06 ` lee
2015-09-05 17:09 ` Mick
2015-09-05 21:40 ` Fernando Rodriguez
2015-09-05 22:24 ` Mick
2015-09-06 13:18 ` lee [this message]
2015-09-06 13:03 ` lee
2015-09-06 18:44 ` Fernando Rodriguez
2015-09-06 2:45 ` lee
2015-09-06 18:12 ` Mick
2015-09-12 11:20 ` lee
2015-09-12 11:23 ` [gentoo-user] SOLVED: " lee
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=87twr7it3x.fsf@heimdali.yagibdah.de \
--to=lee@yagibdah.de \
--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