unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Marius Bakke <marius@gnu.org>
To: Giovanni Biscuolo <g@xelera.eu>, Tobias Geerinckx-Rice <me@tobias.gr>
Cc: help-guix@gnu.org
Subject: Re: curl server certificate verification failed for a few sites
Date: Sat, 06 Jun 2020 15:44:05 +0200	[thread overview]
Message-ID: <87o8pwtil6.fsf@gnu.org> (raw)
In-Reply-To: <87tuzok0zk.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me>

[-- Attachment #1: Type: text/plain, Size: 697 bytes --]

Giovanni Biscuolo <g@xelera.eu> writes:

> Hi Tobias,
>
> thank you for your clear explanation and patience
>
> ...and sorry again to all other Guix users for the "noise": this is not
> strictly related to Guix but just to the most recent version of
> curl/wget
>
> I still I don't understand the differences between curl (and wget)
> behaviour and the last Guix available ungoogled-chromium (see below).

The problem is with GnuTLS, which failed if one of the trust roots were
using an expired certificate:

  https://gitlab.com/gnutls/gnutls/-/issues/1008

It has been fixed in the latest GnuTLS, which is in Guix as of commit
8951b9496b5c390adb3b3292d234bb8ab9936c40.  Thanks for reporting it!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2020-06-06 13:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 13:13 curl server certificate verification failed for a few sites Giovanni Biscuolo
2020-06-04 14:40 ` Jack Hill
2020-06-04 16:14   ` Giovanni Biscuolo
2020-06-04 16:43     ` Tobias Geerinckx-Rice
2020-06-06  9:16       ` Giovanni Biscuolo
2020-06-06 13:44         ` Marius Bakke [this message]
2020-06-08 17:52           ` Giovanni Biscuolo
2020-06-06 14:29         ` Tobias Geerinckx-Rice

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=87o8pwtil6.fsf@gnu.org \
    --to=marius@gnu.org \
    --cc=g@xelera.eu \
    --cc=help-guix@gnu.org \
    --cc=me@tobias.gr \
    /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).