unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "Todor Kondić" <tk.code@protonmail.com>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: "help-guix\\\\@gnu.org" <help-guix@gnu.org>
Subject: Re: Certificate problem with curl, though icecat works
Date: Thu, 13 Aug 2020 08:58:04 +0000	[thread overview]
Message-ID: <XgeQuKxpfg8CQI0QrwuOYtKkBUnhkPFkPNQ5lEaCRMHWZ4g4CRg_ngAD1d0DyLElakoC2vkw1L3WZ9_B5M-K-f8Er2K2hxp9RFURTTGAkA0=@protonmail.com> (raw)
In-Reply-To: <87v9hn591j.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, 13 August 2020 08:55, Giovanni Biscuolo <g@xelera.eu> wrote:

> Giovanni Biscuolo g@xelera.eu writes:
>
> [...]
>
> > > $ 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
>
> No, this is a different issue:
>
> --8<---------------cut here---------------start------------->8---
>
> gnutls-cliactorws.epa.gov
>
> Processed 128 CA certificate(s).
> Resolving 'actorws.epa.gov:443'...
> Connecting to '134.67.99.60:443'...
>
> -   Certificate type: X.509
>
> -   Got a certificate list of 2 certificates.
>
> -   Certificate[0] info:
>
> -   subject `CN=*.epa.gov,OU=OMS/OITO/EHD,O=Environmental Protection Agency,L=Durham,ST=North Carolina,C=US', issuer`CN=DigiCert SHA2 Secure Server CA,O=DigiCert Inc,C=US', serial 0x0caca7602da89b50c3820b33518c827a, RSA key 2048 bits, signed using RSA-SHA256, activated `2019-04-25 00:00:00 UTC', expires`2021-04-19 12:00:00 UTC', pin-sha256="o5d2tkYzGNEoALzaPpAd5q+Sima2MnbbItE64CpyDCk="
>     Public Key ID:
>     sha1:884a27ada33cc533411036cde08f7c83bee2580e
>     sha256:a39776b6463318d12800bcda3e901de6af928a66b63276db22d13ae02a720c29
>     Public Key PIN:
>     pin-sha256:o5d2tkYzGNEoALzaPpAd5q+Sima2MnbbItE64CpyDCk=
>
> -   Certificate[1] info:
>
> -   subject `CN=DigiCert SHA2 Secure Server CA,O=DigiCert Inc,C=US', issuer`CN=DigiCert Global Root CA,OU=www.digicert.com,O=DigiCert Inc,C=US', serial 0x01fda3eb6eca75c888438b724bcfbc91, RSA key 2048 bits, signed using RSA-SHA256, activated `2013-03-08 12:00:00 UTC', expires`2023-03-08 12:00:00 UTC', pin-sha256="5kJvNEMw0KjrCAu7eXY5HZdvyCS13BbA0VJG1RSP91w="
>     |<1>| Got OCSP response with an unrelated certificate.
>
> -   Status: The certificate is NOT trusted. The received OCSP status response is invalid.
>     *** PKI verification of server certificate failed...
>     *** Fatal error: Error in the certificate.
>     [~]-
>
>     --8<---------------cut here---------------end--------------->8---
>
>
> I'm going to open a bug report upstream (gnutls), thanks for your
> report.
>
> Best regards, Gio'
>
> ------------------------------------------------------------------------------------------------
>
> Giovanni Biscuolo
>
> Xelera IT Infrastructures


Thanks for confirming this! I pulled the newest Guix and updated gnutls and that did not solve the issue. Please let me know when you post the issue, so I can track it.


  reply	other threads:[~2020-08-13  8:58 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
2020-08-13  6:55   ` Giovanni Biscuolo
2020-08-13  8:58     ` Todor Kondić [this message]
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='XgeQuKxpfg8CQI0QrwuOYtKkBUnhkPFkPNQ5lEaCRMHWZ4g4CRg_ngAD1d0DyLElakoC2vkw1L3WZ9_B5M-K-f8Er2K2hxp9RFURTTGAkA0=@protonmail.com' \
    --to=tk.code@protonmail.com \
    --cc=g@xelera.eu \
    --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).