From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#16791: w3m fails to do any SSL certificate checking Date: Tue, 05 Jan 2016 00:35:57 +0100 Message-ID: <87y4c4x6hu.fsf@gnu.org> References: <87ha7wol02.fsf@netris.org> <20160103022030.GA16788@jasmine> <20160104061932.GA4210@jasmine> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60347) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aGEgT-0003XP-VI for bug-guix@gnu.org; Mon, 04 Jan 2016 18:37:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aGEgP-0002tr-TK for bug-guix@gnu.org; Mon, 04 Jan 2016 18:37:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:49749) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aGEgP-0002tn-Q8 for bug-guix@gnu.org; Mon, 04 Jan 2016 18:37:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20160104061932.GA4210@jasmine> (Leo Famulari's message of "Mon, 4 Jan 2016 01:19:32 -0500") 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: Leo Famulari Cc: 16791@debbugs.gnu.org Leo Famulari skribis: > 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. >>=20 >> If you download the "debian" file [0], which includes all of their >> packaging for w3m, you can view the file at 'debian/w3mconfig'. >>=20 >> The relevant option is "ssl_verify_server", and it must be set to "1" in >> order for w3m to perform verification. >>=20 >> Example with a domain whose certificate is expired: >> $ w3m -o ssl_verify_server 1 fmrl.me >>=20 >> Do we ever bundle configuration files in this manner? >>=20 >> Can a wrapper set command-line variables? >>=20 >> I will investigate whether these options can be set at build time. >>=20 >> 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". >>=20 >> [0] >> http://http.debian.net/debian/pool/main/w/w3m/w3m_0.5.3-26.debian.tar.xz >>=20 > > This particular issue was resolved in October 2014 in this commit > (tested): > http://anonscm.debian.org/cgit/collab-maint/w3m.git/commit/?id=3D05503271= dfd26b843589dece0da35ba5d7d38654 Looks like applying this patch would fix the bug right away, right? > 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? Unless upstream is really dead, we should track it. I think it=E2=80=99s n= ot the distro=E2=80=99s job to do non-trivial development. What about using the latest upstream tarball, along with the patch above and probably the one that disables SSLv{2,3}? Thanks, Ludo=E2=80=99.