From: Lars Ingebrigtsen <larsi@gnus.org>
To: John Cummings <john@rootabega.net>
Cc: Michael Hoffman <emacs-hoffman@snkmail.com>, 51038@debbugs.gnu.org
Subject: bug#51038: 27.2; ELPA certificate not trusted on Windows
Date: Wed, 06 Oct 2021 11:25:12 +0200 [thread overview]
Message-ID: <87ee8yec93.fsf@gnus.org> (raw)
In-Reply-To: <laKT_8vsy9AfDG0d3XZAeR5JDbTflOIYiOy_-b8DASqEkbq3O5PguTT-iCT2D_GMn_U5bp5GoVTuiUifLvEDd6g0vJ6EKdZLfxa3B0JbKiY=@rootabega.net> (John Cummings's message of "Tue, 05 Oct 2021 17:35:35 +0000")
John Cummings <john@rootabega.net> writes:
> I believe that this is what you should expect if you are using gnutls
> 3.6.12 and you have the expired X3 root cert in your trust store.
Yup. So this isn't a problem on Savannah. Quoting:
----
From: Bob Proulx <INVALID.NOREPLY@gnu.org>
Subject: Certificate Expiration Event September 2021
On September 30, 2021, as planned the DST Root CA X3 cross-sign has expired
for the Let's Encrypt trust chain. That was a normal and planned event.
However coupled with a verification error in the code of libraries
authenticating certificates it caused some clients that have not been updated
to fixed versions to have problems validating certificates.
If you are experiencing invalid certificate chain problems with Let's Encrypt
certificates (not a Savannah problem) then please upgrade your client to the
latest security patches for your system. Please reference these resources as
to upstream information and discussion about the issue.
* https://letsencrypt.org/docs/dst-root-ca-x3-expiration-september-2021/
* https://community.letsencrypt.org/t/production-chain-changes/150739/4
* https://letsencrypt.org/docs/certificate-compatibility/
* https://letsencrypt.org/certificates/
* https://www.openssl.org/blog/blog/2021/09/13/LetsEncryptRootCertExpire/
----
So I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-06 9:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 15:14 bug#51038: 27.2; ELPA certificate not trusted on Windows Michael Hoffman
2021-10-05 17:35 ` John Cummings
2021-10-06 9:25 ` Lars Ingebrigtsen [this message]
2021-10-06 10:54 ` John Cummings
2021-10-06 12:57 ` Eli Zaretskii
2021-10-06 13:12 ` John Cummings
2021-10-06 13:35 ` Eli Zaretskii
2021-10-06 13:39 ` John Cummings
2021-10-06 13:57 ` Michael Hoffman
2021-10-06 15:36 ` Eli Zaretskii
2021-10-06 16:13 ` John Cummings
2021-10-24 16:49 ` Ioannis Kappas
2021-10-24 17:11 ` Eli Zaretskii
2021-10-24 18:21 ` Ioannis Kappas
2021-10-24 18:44 ` Lars Ingebrigtsen
2021-10-24 18:50 ` Eli Zaretskii
2021-10-24 20:30 ` Ioannis Kappas
2021-10-25 11:48 ` Eli Zaretskii
2021-10-25 17:18 ` Ioannis Kappas
2021-10-28 19:34 ` Ioannis Kappas
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=87ee8yec93.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=51038@debbugs.gnu.org \
--cc=emacs-hoffman@snkmail.com \
--cc=john@rootabega.net \
/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).