all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnurl: add CA path to configure-flags
Date: Tue, 14 Jun 2016 12:12:56 +0200	[thread overview]
Message-ID: <87y468gjtj.fsf@gnu.org> (raw)
In-Reply-To: <20160613153834.GA4065@khazad-dum> (ng0@we.make.ritual.n0.is's message of "Mon, 13 Jun 2016 15:38:34 +0000")

ng0 <ng0@we.make.ritual.n0.is> skribis:

> On 2016-06-13(04:43:32+0200), Ludovic Courtès wrote:
>> Hi,
>>
>> Andreas Enge <andreas@enge.fr> skribis:
>>
>> > On Sat, Jun 11, 2016 at 08:51:28PM +0000, ng0 wrote:
>> >> * gnurl(configure-flags): --with-ca-path=/etc/ssl/certs/
>> >
>> > my impression is that this absolute path does not do what we would like
>> > it to. Optimally, the user would decide, by installing a certificate bundle
>> > into the profile, which certificates to use. And on a foreign distro, the
>> > random certificate bundle in /etc/ssl/certs, which does not come from Guix,
>> > would be used by the Guix gnurl, which would be surprising.
>>
>> Besides, our cURL and Gnurl packages are linked against GnuTLS, which is
>> itself configured with ‘--with-default-trust-store-dir=/etc/ssl/certs’.
>>
>> Does ‘--with-ca-path’ change anything to that?
>>
>> Thanks,
>> Ludo’.
>>
>
> I strongly assume that with those set, --with-ca-path is unnecessary.

Fine.  :-)

> I know patches are now tracked in patchworks, can they be closed via
> Email, or do I have to sign up? Else someone who already is signed up
> can close this, as from my perspective this is done.

I think one has to login, which is quite inconvenient.

Ludo’.

      reply	other threads:[~2016-06-14 10:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-11 20:51 [PATCH] gnurl: add CA path to configure-flags ng0
2016-06-12 14:22 ` Andreas Enge
2016-06-12 15:56   ` ng0
2016-06-13 14:43   ` Ludovic Courtès
2016-06-13 15:38     ` ng0
2016-06-14 10:12       ` Ludovic Courtès [this message]

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=87y468gjtj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@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 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.