From: Giovanni Biscuolo <g@xelera.eu>
To: TK <tkprom@protonmail.com>, "help-guix\\@gnu.org" <help-guix@gnu.org>
Subject: Re: Certificate problem with curl, though icecat works
Date: Wed, 12 Aug 2020 19:47:13 +0200 [thread overview]
Message-ID: <87y2mj69jy.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <9kSaR15iLCuEyScHdlJ73XpOm85IcNNLxHb6T9PoWPiW6PTiT9eFfsAIStaIyuxzgpZOpCUfYkLP4Y8PaE3jxcKxOryeTFg5BzplBz1esxQ=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
Hi TK
TK <tkprom@protonmail.com> writes:
[...]
> However, doing the same thing with curl errors out:
>
> $ curl https://actorws.epa.gov/actorws/chemIdentifier/v01/resolve.json?identifier=MKXZASYAUGDDCJ-NJAFHUGGSA-N
>
> curl: (60) server certificate verification failed. CAfile: /home/user/.guix-profiles/profile/etc/ssl/certs/ca-certificates.crt CRLfile: none
> More details here: https://curl.haxx.se/docs/sslcerts.html
>
> ca-certificates.crt exists at the CAfile location and CURL_CA_BUNDLE is set properly.
This is similar to
https://lists.gnu.org/archive/html/help-guix/2020-06/msg00025.html
and it should be fixed in the latest GnuTLS, which is in Guix since
commiy 8951b9496b5c390adb3b3292d234bb8ab9936c40
Anyway I can confirm that I get the same results as you.
I'm going to investigare if I can add something useful and open a bug
(probably upstream?)
happy hacking! Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-08-12 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-11 11:31 Certificate problem with curl, though icecat works TK
2020-08-12 17:47 ` Giovanni Biscuolo [this message]
2020-08-13 6:55 ` Giovanni Biscuolo
2020-08-13 8:58 ` Todor Kondić
2020-08-13 10:26 ` Giovanni Biscuolo
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=87y2mj69jy.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me \
--to=g@xelera.eu \
--cc=help-guix@gnu.org \
--cc=tkprom@protonmail.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.
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).