From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Giovanni Biscuolo <g@xelera.eu>
Cc: Jack Hill <jackhill@jackhill.us>, help-guix@gnu.org
Subject: Re: curl server certificate verification failed for a few sites
Date: Thu, 04 Jun 2020 18:43:10 +0200 [thread overview]
Message-ID: <874krqdboh.fsf@nckx> (raw)
In-Reply-To: <87o8pylsel.fsf@roquette.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
Giovanni Biscuolo 写道：
> Jack Hill <jackhill@jackhill.us> writes:
>> The error wget gives is a little bit better,
FWIW, I use this (extremely verbose) command to debug/check my own
servers:
$ openssl s_client -showcerts -servername
voices.transparency.org \
-connect voices.transparency.org:443
>> Therefore, I think the fix is for voices.transparency.org to
>> update the
>> certificate chain/bundle that they are sending.
They're also sending intermediate certificates that they shouldn't
be sending in the first place[0] which doesn't help matters. I
agree that this looks like an outdated server (mis)configuration.
> Yes. All modern clients and operating systems have the newer,
> modern
> COMODO and USERTrust roots which don’t expire until 2038.
Right, but ‘modern’ there means ~2015.
Kind regards,
T G-R
[0]:
https://www.ssllabs.com/ssltest/analyze.html?d=voices.transparency.org&s=52.4.38.70&hideResults=on
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2020-06-04 16:43 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 [this message]
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=874krqdboh.fsf@nckx \
--to=me@tobias.gr \
--cc=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).