From: Mark H Weaver <mhw@netris.org>
To: "Tomáš Čech" <sleep_walker@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: curl: Update to 7.41.0. Fix #20121.
Date: Sun, 22 Mar 2015 12:56:43 -0400 [thread overview]
Message-ID: <87vbht7yyc.fsf@netris.org> (raw)
In-Reply-To: <1427019636-24875-1-git-send-email-sleep_walker@gnu.org> ("Tomáš Čech"'s message of "Sun, 22 Mar 2015 11:20:36 +0100")
Tomáš Čech <sleep_walker@gnu.org> writes:
> @@ -60,7 +64,18 @@
> ("pkg-config" ,pkg-config)
> ("python" ,python-2)))
> (arguments
> - `(#:configure-flags '("--with-gnutls" "--with-gssapi")
> + `(#:configure-flags
> + '("--with-gnutls" "--with-gssapi" "--enable-http"
> + ;; This option requires parameter so let's use this one
> + ;; - when it exists, it makes sense
> + ;; - when it doesn't exist, we can still use SSL_CERT_DIR environment
> + ;; variable to set it per user or for whole system
> + ;; Fixes #20121.
> + "--with-ca-path=/etc/ssl/certs"
It would be better to avoid passing the --with-ca-path= option. We are
attempting to move away from having any compiled-in system-wide location
for the CA trust store. Each user should be able to specify their
desired trust store using environment variables or other settings.
We currently pass a similar configure-time option to GnuTLS for now, but
only because GnuTLS provides no other way to specify the location of an
old-style system trust store. We should be able to remove this when we
have the more modern p11-kit system working.
Can you find a way to make 'curl' work without compiling-in a hard-coded
system trust store location?
Mark
next prev parent reply other threads:[~2015-03-22 16:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 10:20 [PATCH] gnu: curl: Update to 7.41.0. Fix #20121 Tomáš Čech
2015-03-22 12:40 ` Tomáš Čech
2015-03-22 16:56 ` Mark H Weaver [this message]
2015-03-22 17:41 ` Tomáš Čech
2015-03-22 18:16 ` Mark H Weaver
2015-03-22 19:09 ` Tomáš Čech
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbht7yyc.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=sleep_walker@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).