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 7251A1399E9 for ; Fri, 4 Sep 2015 01:23:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2D1BB14241; Fri, 4 Sep 2015 01:23:07 +0000 (UTC) Received: from mail-yk0-f173.google.com (mail-yk0-f173.google.com [209.85.160.173]) (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 0742614209 for ; Fri, 4 Sep 2015 01:23:05 +0000 (UTC) Received: by ykei199 with SMTP id i199so7331956yke.0 for ; Thu, 03 Sep 2015 18:23:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=edl/XIbOIOUhYIiiaBSMs1VgqxljkV69TKcyTkzD3/s=; b=hHa1zPlE5DkKf0tG4G3QbwS+QKthNLrskr3Z0nLcza+GlQa+dr//aoPyhYiENEI72O VTFLvaWmv+z7XNeP1cv3Q+T3hWp/A0rQS8p48//CveBsuE40+ZZZX6K1kHFIZWBhexMX 88PzPhHBswaaFrI8O2U6BfIF8epiREQDOB5LswrOZpKZp2IdyXFl3bKVz6YoTNOXkMi0 Z/Mgs7BRGxorjyzR2p+jpsdkKvzZny32pTD68I2yXHe2/AfD6tPW7cZxBDgXydnMVeVF 3n+GmK5Sx2+Y5WhVwQ6XeV2GrZ/wLykDQWDMMamA3/H0o2lPi4zssMQ/2/6AOcx2rdOk qwVg== X-Received: by 10.13.219.151 with SMTP id d145mr1116970ywe.77.1441329785095; Thu, 03 Sep 2015 18:23:05 -0700 (PDT) Received: from [192.168.2.5] (adsl-65-0-115-33.jan.bellsouth.net. [65.0.115.33]) by smtp.gmail.com with ESMTPSA id u62sm732420ywb.46.2015.09.03.18.23.04 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Sep 2015 18:23:04 -0700 (PDT) Message-ID: <55E8F277.2020707@gmail.com> Date: Thu, 03 Sep 2015 20:23:03 -0500 From: Dale User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33.1 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 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] broken seamonkey :( References: <87oahjmg8s.fsf@heimdali.yagibdah.de> <87egifm5rx.fsf@heimdali.yagibdah.de> In-Reply-To: <87egifm5rx.fsf@heimdali.yagibdah.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: a9f1f15a-9efc-4427-8012-2e4d6852fbfe X-Archives-Hash: a3c7a1462bf2d6490edb2217d3766863 lee wrote: > Fernando Rodriguez writes: > >> On Thursday, September 03, 2015 9:53:39 PM lee wrote: >>> Hi, >>> >>> since quite a while, seamonkey and its relatives are completely broken >>> when it comes to use self-signed certificates. They just refuse the >>> connection to the server, blocking you from accessing your email. >>> >>> Is there still no solution for this problem? I'm totally fed up with it >>> by now. At work, I have frozen seamonkey at version 2.31 and >>> thunderbird at some outdated version that still works with the >>> certificates. Googling for a solution doesn't reveal one, either. >>> >>> Now I need seamonkey to access the email, and I can't very well turn it >>> back to an outdated version just for that. >>> >>> BTW, if this won't be fixed, what are the replacements? >> This[1] is for firefox but should work similarly. Scroll all the way down to >> "bypassing the warning". There's also an about:config option, I *think* it's >> this one[2]. > Thank you. The problem is that it doesn't let me add an exception. Only > the older versions do that. All options to add an exception are > disabled. > > There is 'browser.ssl_override_behavior', the value of which is > 2. Guessing by what that means from [2], that should allow me to add an > exception. > > 'browser.xul.error_pages.enabled' is enabled. There's also > 'browser.xul.error_pages.expert_bad_cert', which is disabled. Let's see > what that does ... still cannot add an exception when I enable it. [3] > would indicate that it's advisable to set it to "true". > > Restarting seamonkey after changing it doesn't help. > > There's nothing wrong with the certificate, either. Older version work > just fine with it. Mutt works fine with it. Gnus works fine with it. > Evolution works fine with it. All of those are more recent than > seamonkey 2.31. > > I could resort to unencrypted connections on the LAN to be able to > upgrade the browsers and MUAs --- for security reasons, ironically --- > but some ppl with laptops need to be able to connect from anywhere over > the internet. So omit all security and use VPN for those to make things > more secure by not using self-signed certificates but insecure > connections? > > > [3]: http://kb.mozillazine.org/Browser.xul.error_pages.expert_bad_cert > >> [1] https://support.mozilla.org/en-US/kb/connection-untrusted-error-message >> [2] http://kb.mozillazine.org/Browser.ssl_override_behavior I'm using seamonkey-2.33.1-r1 and I have not run into this problem. If you would like, I can check some settings and compare them to mine to see if it would help fix yours. Just let me know what you need. Surely this can be fixed. Maybe I did something and don't recall it?? Dale :-) :-)