From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id B8B98138330 for ; Tue, 9 Jan 2018 11:51:06 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 136D4E0A80; Tue, 9 Jan 2018 11:50:59 +0000 (UTC) Received: from smarthost03d.mail.zen.net.uk (smarthost03d.mail.zen.net.uk [212.23.1.23]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 9FCFDE090A for ; Tue, 9 Jan 2018 11:50:58 +0000 (UTC) Received: from [82.69.80.10] (helo=peak.localnet) by smarthost03d.mail.zen.net.uk with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1eYsQj-00013C-4y for gentoo-user@lists.gentoo.org; Tue, 09 Jan 2018 11:50:57 +0000 From: Peter Humphrey To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Firefox-57.0.4 won't accept TLS certificate exception Date: Tue, 09 Jan 2018 11:50:56 +0000 Message-ID: <2883426.IvTKrsIllc@peak> In-Reply-To: <2918660.EtAQm8RF2E@dell_xps> References: <2918660.EtAQm8RF2E@dell_xps> 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-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Originating-smarthost03d-IP: [82.69.80.10] Feedback-ID: 82.69.80.10 X-Archives-Salt: d4c08bc9-feac-4108-a77f-fad12939b88b X-Archives-Hash: adec82f05a46d5c824833751a0c7266f On Tuesday, 9 January 2018 11:34:24 GMT Mick wrote: > I just noticed I am not able to override FF's protestations about the > domain name of the loaded TLS certificate not matching the visited > domain. When I click on Advance/"Confirm Security Exception" to > permanently store this exception nothing happens. All I can do > thereafter is cancel this pop up window. Of course the page will not > load. I've noticed something similar, but it varies from one site to another. Sometimes, confirming an exception works as before, but at other times I'm not even offered the option to make an exception. In that latter case I fire up another browser and use that instead. > How can I overcome this intransigence by the browser, who thinks it knows > better what I wish to do? I wish I knew. -- Regards, Peter.