From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 55858@debbugs.gnu.org, Ken Brown <kbrown@cornell.edu>
Subject: bug#55858: 28.1; process-async-https-with-delay failure
Date: Thu, 09 Jun 2022 10:30:52 +0200 [thread overview]
Message-ID: <877d5q2q83.fsf@gmail.com> (raw)
In-Reply-To: <83mtem4db9.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 09 Jun 2022 08:26:50 +0300")
>>>>> On Thu, 09 Jun 2022 08:26:50 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> There are two issues here. First, there's obviously something I should
>> do on my system so that the TLS certificate for elpa.gnu.org is
>> trusted. I know nothing about TLS certificates and would appreciate
>> help here.
Eli> Not sure about Cygwin, but in general on MS-Windows GnuTLS uses the
Eli> system certificate store to verify certificates. The particular
Eli> problem above should be solved by upgrading GnuTLS and perhaps also
Eli> updating the system certificate store (which should be in general
Eli> always up to date, but I don't know how that system is maintained).
This might be the Let's Encrypt cross-signing certificate expiry
issue, which is fixed in GnuTLS >= 3.6.14 See eg
<https://blog.germancoding.com/2021/04/16/lets-encrypt-and-expired-root-certificates/>
Eli> OTOH, if Cygwin GnuTLS uses the Posix mechanism of certificate stores
Eli> on disk files, then upgrading the certificate files.
If Iʼm right, itʼs a problem in GnuTLS, not an issue with the
certificate store.
Alternatively, we could just let-bind `network-security-level' to 'low
in that test, which effectively disables the checking.
Robert
--
next prev parent reply other threads:[~2022-06-09 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 22:04 bug#55858: 28.1; process-async-https-with-delay failure Ken Brown
2022-06-09 5:26 ` Eli Zaretskii
2022-06-09 8:30 ` Robert Pluim [this message]
2022-06-09 6:44 ` Achim Gratz
2022-06-09 11:17 ` Ken Brown
2022-06-09 13:07 ` Lars Ingebrigtsen
2022-07-11 11:20 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877d5q2q83.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=55858@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kbrown@cornell.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).