From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marius Bakke Subject: bug#28948: feh does encounter certificate errors with valid certificates Date: Sun, 29 Oct 2017 23:00:08 +0100 Message-ID: <87tvyh4ntj.fsf@fastmail.com> References: <20171022203339.qomgp4xm2rqh4zwe@abyayala> <871slm5eby.fsf@fastmail.com> <87k1zdljro.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43100) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1e8vdj-0001QA-Ma for bug-guix@gnu.org; Sun, 29 Oct 2017 18:01:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1e8vdf-0001jh-9V for bug-guix@gnu.org; Sun, 29 Oct 2017 18:01:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:60602) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1e8vde-0001jZ-UZ for bug-guix@gnu.org; Sun, 29 Oct 2017 18:01:03 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1e8vde-0001Pz-Ih for bug-guix@gnu.org; Sun, 29 Oct 2017 18:01:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87k1zdljro.fsf@elephly.net> 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" To: Ricardo Wurmus Cc: 28948@debbugs.gnu.org --=-=-= Content-Type: text/plain Ricardo Wurmus writes: > Marius Bakke writes: > >> ng0 writes: >> >>> feh https://i.imgur.com/263enxT.jpg >>> feh opens image >>> >>> Problem: >>> user@abyayala ~/src/guix/guix$ feh https://i.imgur.com/263enxT.jpg >>> feh WARNING: open url: server certificate verification failed. CAfile: none CRLfile: none >>> feh WARNING: https://i.imgur.com/263enxT.jpg - File does not exist >>> feh: No loadable images specified. >>> See 'man feh' for detailed usage information >> >> This is the same issue with libcurl as has been discussed many times in >> the past. Since it won't be fixed upstream any time soon (support for >> CURL_CA_BUNDLE has been removed also for Windows), I suggest we "bite >> the bullet" this time and add a hard-coded default. > > This would mean that individual users no longer have control over what > certificate authorities they want to trust. Check and mate. I never considered this, but that makes this patch a non-starter. > Does anything speak against patching in support for the CURL_CA_BUNDLE > environment variable? No, it looks like the only option. Should set a good precedent. :-) --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAln2T2gACgkQoqBt8qM6 VPokzQgAz3gY7N+vKJCtlTCP4KI+SYmnyq+V/78pbFpXvarSrpeXGWDqCwavk2+6 rcUgAk1jTtoSgOg+p/ikkb9M0mVtLbZJ258ILSiXdcwTJWZq2bwW0Ditwzv6fM8I DS1JKYQ6QXuOB/ct1gJfYWZA4w9lq6BnLwNjutsTzA8jwz3vPbF/qMQaGBGj6edD DuPen9cetAbud9sVL24mWC8i5Xhef+MMxDb1zjsVCoab9nZT75DavfkLZDb9W9KU Imihk04ZF69hhg8e0ke48+xvrxkqBgV1p/vqmPTz7LZZCEfLZIc6VEFJQfjfE19h HlvUm/1gyyclYPv0/dNz7VI91DcOVA== =yqOY -----END PGP SIGNATURE----- --=-=-=--