From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 1F3A11384C3 for ; Sun, 6 Sep 2015 14:30:31 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0F7CB142BF; Sun, 6 Sep 2015 14:29:37 +0000 (UTC) Received: from acheron.yagibdah.de (acheron.yagibdah.de [185.55.75.245]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1F735141E3 for ; Sun, 6 Sep 2015 14:29:34 +0000 (UTC) Received: from br-dmz-ip.yagibdah.de ([192.168.1.1] helo=heimdali.yagibdah.de) by acheron.yagibdah.de with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.85) (envelope-from ) id 1ZYawl-0005NA-Pw for gentoo-user@lists.gentoo.org; Sun, 06 Sep 2015 16:29:32 +0200 Received: from lee by heimdali.yagibdah.de with local (Exim 4.84) (envelope-from ) id 1ZYawl-00079H-NV for gentoo-user@lists.gentoo.org; Sun, 06 Sep 2015 16:29:31 +0200 From: lee To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] broken seamonkey :( In-Reply-To: <201509052324.43538.michaelkintzios@gmail.com> (Mick's message of "Sat, 5 Sep 2015 23:24:28 +0100") Date: Sun, 06 Sep 2015 15:18:26 +0200 Organization: my virtual residence Message-ID: <87twr7it3x.fsf@heimdali.yagibdah.de> References: <87oahjmg8s.fsf@heimdali.yagibdah.de> <201509051809.45420.michaelkintzios@gmail.com> <201509052324.43538.michaelkintzios@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) Mail-Followup-To: gentoo-user@lists.gentoo.org Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain X-Archives-Salt: 27d7eade-700e-46e8-984c-6acedaeaf4ab X-Archives-Hash: e604aad1dccfedf9ac3cd16d2e76b6b7 Mick 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.