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: Mon, 4 Jan 2016 14:12:04 -0500 Message-ID: <20160104191204.GB26142@jasmine> References: <87ha7wol02.fsf@netris.org> <20160103022030.GA16788@jasmine> <20160104061932.GA4210@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58894) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aGAZ0-0005jZ-JL for bug-guix@gnu.org; Mon, 04 Jan 2016 14:13:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aGAYw-0003IF-JJ for bug-guix@gnu.org; Mon, 04 Jan 2016 14:13:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:49636) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aGAYw-0003IA-8y for bug-guix@gnu.org; Mon, 04 Jan 2016 14:13:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <20160104061932.GA4210@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@debbugs.gnu.org On Mon, Jan 04, 2016 at 01:19:32AM -0500, Leo Famulari wrote: > On Sat, Jan 02, 2016 at 09:20:30PM -0500, Leo Famulari wrote: > > I looked into how Debian does it. They bundle a configuration file that > > sets the correct options. > > > > If you download the "debian" file [0], which includes all of their > > packaging for w3m, you can view the file at 'debian/w3mconfig'. > > > > The relevant option is "ssl_verify_server", and it must be set to "1" in > > order for w3m to perform verification. > > > > Example with a domain whose certificate is expired: > > $ w3m -o ssl_verify_server 1 fmrl.me > > > > Do we ever bundle configuration files in this manner? > > > > Can a wrapper set command-line variables? > > > > I will investigate whether these options can be set at build time. > > > > I don't think we should ship a browser in this state, even if users are > > able to configure it properly after installation. w3m is used by other > > programs like mutt to render html "under the hood". > > > > [0] > > http://http.debian.net/debian/pool/main/w/w3m/w3m_0.5.3-26.debian.tar.xz > > > > This particular issue was resolved in October 2014 in this commit > (tested): > http://anonscm.debian.org/cgit/collab-maint/w3m.git/commit/?id=05503271dfd26b843589dece0da35ba5d7d38654 > > It looks like there is a lot of development activity happening within > Debian, beyond simple packaging [0]. Even what seems to be the official > SourceForge page seems to be tracking the Debian work [1]. > > The Debian developers are regularly issuing release tags but not release > tarballs. I built from the latest one and it seems to work. > > I think we should use the Debian repo as the source for our w3m package. > What does everyone else think? I wanted to "tighten" w3m's SSL configuration in general, and found that the Debian developers have already disabled SSLv2 and SSLv3 [0] and some insecure ciphers [1]. [0] http://anonscm.debian.org/cgit/collab-maint/w3m.git/commit/?id=05503271dfd26b843589dece0da35ba5d7d38654 http://anonscm.debian.org/cgit/collab-maint/w3m.git/commit/?id=1aace42d026c7df31c4762ef1095ce83450916fc [1] http://anonscm.debian.org/cgit/collab-maint/w3m.git/commit/?id=3335b5e824eecf70055af985b12c60651787fbfc > > [0] > http://anonscm.debian.org/cgit/collab-maint/w3m.git/ > > [1] > http://sourceforge.net/p/w3m/patches/71/ > > >