From: Giovanni Biscuolo <g@xelera.eu>
To: Jack Hill <jackhill@jackhill.us>
Cc: help-guix@gnu.org
Subject: Re: curl server certificate verification failed for a few sites
Date: Thu, 04 Jun 2020 18:14:42 +0200 [thread overview]
Message-ID: <87o8pylsel.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <alpine.DEB.2.20.2006041034580.5735@marsh.hcoop.net>
[-- Attachment #1: Type: text/plain, Size: 2439 bytes --]
Hi Jack,
thanks for your help!
...and sorry if this is not Guix specific
Jack Hill <jackhill@jackhill.us> writes:
[...]
> I think that this is due to the recent AdTrust Root CA cert expiration
> [0]. The error wget gives is a little bit better, but you know about the
> situation to interpret it correctly:
>
> """
> $ wget "https://voices.transparency.org" -O /dev/null
> --2020-06-04 10:37:29-- https://voices.transparency.org/
> Resolving voices.transparency.org (voices.transparency.org)...
> 52.4.225.124, 52.4.240.221, 52.1.119.170, ...
> Connecting to voices.transparency.org
> (voices.transparency.org)|52.4.225.124|:443... connected.
> ERROR: The certificate of ‘voices.transparency.org’ is not trusted.
> ERROR: The certificate of ‘voices.transparency.org’ has expired.
> """
oh I see, I get this error also... but I do not understand the different
behaviour with what I see in Firefox (from Debian) or ungoogled-chromium
(from Guix): using one of those browsers the certificate is valid, the
certificate viewer shows that the root in cert hierarchy is "USERTrust
RSA Certification Authority"
The section in [0] titled "Certificate Chain Diagram" states:
--8<---------------cut here---------------start------------->8---
A legacy browser or older device that does not have the modern
“USERTRust” root would not trust it and so would look further up the
chain to a root it does trust, the AddTrust External CA Root. A more
modern browser would have the USERTrust root already installed and trust
itwithout needing to rely on the older AddTrust root.
--8<---------------cut here---------------end--------------->8---
I do not fully understand why curl and wget return error while Firefox
and ungoogled-chromium not
[...]
> Therefore, I think the fix is for voices.transparency.org to update the
> certificate chain/bundle that they are sending.
>
> [0]
> https://support.sectigo.com/Com_KnowledgeDetailPage?Id=kA03l00000117LT
this page states:
--8<---------------cut here---------------start------------->8---
Will my certificate still be trusted after May 30, 2020?
Yes. All modern clients and operating systems have the newer, modern
COMODO and USERTrust roots which don’t expire until 2038.
--8<---------------cut here---------------end--------------->8---
Thanks! Gio'
--
Giovanni Biscuolo
Xelera IT Infrastructures
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-06-04 16:15 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 [this message]
2020-06-04 16:43 ` Tobias Geerinckx-Rice
2020-06-06 9:16 ` Giovanni Biscuolo
2020-06-06 13:44 ` Marius Bakke
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=87o8pylsel.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me \
--to=g@xelera.eu \
--cc=help-guix@gnu.org \
--cc=jackhill@jackhill.us \
/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).