unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ng0 <ngillmann@runbox.com>
To: Ricardo Wurmus <rekado@elephly.net>, myglc2 <myglc2@gmail.com>
Cc: help-guix@gnu.org
Subject: curl_ca_bundle, and gnurl?
Date: Fri, 30 Sep 2016 14:12:59 +0000	[thread overview]
Message-ID: <87d1jllbmc.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87shshsw3w.fsf@elephly.net>

Ricardo Wurmus <rekado@elephly.net> writes:

> myglc2 <myglc2@gmail.com> writes:
>
>> With GuixSD user config ...
……
>>  )
>
> You forgot to actually add “nss-certs” to the manifest.  After adding
> “nss-certs” you need to set the environment variable CURL_CA_BUNDLE:
>
>   export CURL_CA_BUNDLE=/home/rekado/.myglc2-profile/etc/ssl/certs/ca-certificates.crt
>
> (I only recently patched r-curl to respect this environment variable.
> We should patch libcurl so that all packages using libcurl understand
> it.)
>

I wonder if we need this for gnurl or if the code base of gnurl is still
curl-like enough that it respects the variable.. last time I tried gnurl
as a user on its own (which is *not* the intended use) was on Gentoo.
Gnurl is afaik not (yet) a gnu project and requires no sync with the gnu
descriptions.. I should add this to the description.

But can you share some insights why curl requires this? For gnurl I rely
on its test suite, but I think curl does not complain about the missing
CURL_CA_BUNDLE in its test suite either, or does it?

And if gnurl should require this, how could I fix gnurl (not the package
description in guix) to drop this strange behavior if it is possible at
all?

>
> ~~ Ricardo
>
>
>

  reply	other threads:[~2016-09-30 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 23:09 R install.packages() fails: 'Peer certificate cannot be authenticated with given CA certificates' myglc2
2016-09-30  7:08 ` Ricardo Wurmus
2016-09-30 14:12   ` ng0 [this message]
2016-09-30 19:20     ` curl_ca_bundle, and gnurl? Ricardo Wurmus
2016-10-01 11:41       ` ng0

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=87d1jllbmc.fsf@we.make.ritual.n0.is \
    --to=ngillmann@runbox.com \
    --cc=help-guix@gnu.org \
    --cc=myglc2@gmail.com \
    --cc=rekado@elephly.net \
    /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.
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).