From: Ricardo Wurmus <rekado@elephly.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 28948@debbugs.gnu.org
Subject: bug#28948: feh does encounter certificate errors with valid certificates
Date: Sun, 29 Oct 2017 22:35:39 +0100 [thread overview]
Message-ID: <87k1zdljro.fsf@elephly.net> (raw)
In-Reply-To: <871slm5eby.fsf@fastmail.com>
Marius Bakke <mbakke@fastmail.com> writes:
> ng0 <ng0@infotropique.org> 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.
Does anything speak against patching in support for the CURL_CA_BUNDLE
environment variable?
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-10-29 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 20:33 bug#28948: feh does encounter certificate errors with valid certificates ng0
2017-10-29 12:27 ` Marius Bakke
2017-10-29 21:35 ` Ricardo Wurmus [this message]
2017-10-29 22:00 ` Marius Bakke
2017-10-29 23:47 ` Marius Bakke
2017-10-30 8:02 ` Ricardo Wurmus
2017-10-30 14:06 ` ng0
2017-11-01 20:55 ` Marius Bakke
2017-11-05 15:21 ` Marius Bakke
2017-11-05 16:14 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1zdljro.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=28948@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.