unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: David Loyall <david@the-good-guys.net>
Cc: help-guix@gnu.org
Subject: Re: rust:cargo (libcurl) vs. CURL_CA_BUNDLE
Date: Sun, 01 Sep 2019 12:58:38 +0200	[thread overview]
Message-ID: <87lfv8b7vl.fsf@gnu.org> (raw)
In-Reply-To: <CA+4fW6mbsLbzrUwVTunce3bHObbs8sVk3Zzrw3u_kKD9KHoQEQ@mail.gmail.com> (David Loyall's message of "Thu, 15 Aug 2019 18:14:41 -0500")

Hello David,

David Loyall <david@the-good-guys.net> skribis:

> I think the way `cargo` uses `libcurl` is preventing it from looking
> in the `CURL_CA_BUNDLE` environment variable to find where the
> certificate authority file is.
>
> Here we see what `cargo` I am using:
>
>     sebboh@geeks ~/projects$ cargo -V
>     cargo 1.36.0
>
> Here we see the contents of one of my environment variables:
>
>     sebboh@geeks ~/projects$ echo $CURL_CA_BUNDLE
>     /home/sebboh/.guix-profile/etc/ssl/certs/ca-certificates.crt
>
> Here we try to use `cargo` for a common task:
>
>     sebboh@geeks ~/projects$ cargo install rustfmt-nightly
>         Updating crates.io index
>     error: failed to download from
> `https://crates.io/api/v1/crates/rustfmt-nightly/1.4.5/download`
>
>     Caused by:
>       [60] SSL peer certificate or SSH remote key was not OK (server
> certificate verification failed. CAfile: none CRLfile: none)

This was discussed recently on IRC:

  http://logs.guix.gnu.org/guix/2019-08-29.log#102010

Unfortunately we didn’t reach a conclusion.

My guess was that perhaps cargo honors a different environment
variable—i.e., not ‘SSL_CERT_FILE’, ‘SSL_CERT_DIR’, nor
‘CURL_CA_BUNDLE’.  The ‘ltrace -e getenv’ trick I gave might give us
clues about relevant environment variables.

Could you give it a try?

Thanks,
Ludo’.

  reply	other threads:[~2019-09-01 10:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-15 23:14 rust:cargo (libcurl) vs. CURL_CA_BUNDLE David Loyall
2019-09-01 10:58 ` Ludovic Courtès [this message]
2019-09-04  0:16   ` David Loyall
2019-09-24 22:22     ` Robin Heinemann

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=87lfv8b7vl.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=david@the-good-guys.net \
    --cc=help-guix@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.
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).