From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#16791: w3m fails to do any SSL certificate checking Date: Wed, 10 Feb 2016 16:16:41 -0500 Message-ID: <20160210211641.GA28843@jasmine> References: <87ha7wol02.fsf@netris.org> <20160103022030.GA16788@jasmine> <20160104061932.GA4210@jasmine> <87y4c4x6hu.fsf@gnu.org> <20160105163214.GA23764@jasmine> <20160108045512.GA30445@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44979) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTc8J-0007Xf-2O for bug-guix@gnu.org; Wed, 10 Feb 2016 16:17:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aTc8F-0004EO-Rh for bug-guix@gnu.org; Wed, 10 Feb 2016 16:17:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:54489) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aTc8F-0004EC-LC for bug-guix@gnu.org; Wed, 10 Feb 2016 16:17:03 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aTc8E-00042H-Ed for bug-guix@gnu.org; Wed, 10 Feb 2016 16:17:02 -0500 Sender: "Debbugs-submit" Resent-To: bug-guix@gnu.org Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20160108045512.GA30445@jasmine> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: 16791-done@debbugs.gnu.org On Thu, Jan 07, 2016 at 11:55:12PM -0500, Leo Famulari wrote: > On Tue, Jan 05, 2016 at 11:32:14AM -0500, Leo Famulari wrote: > > On Tue, Jan 05, 2016 at 12:35:57AM +0100, Ludovic Courtès wrote: [...] > > > What about using the latest upstream tarball, along with the patch > > > above and probably the one that disables SSLv{2,3}? > > > > I'll try that. > > Mark, can you check if commit 62339e2d49 fixes this bug for you? I believe this bug is fixed. Please re-open if that is not the case.