From: Jib Style <jibstyle209@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Emacs, GnuTLS, and DST Root CA X3
Date: Wed, 06 Oct 2021 05:25:40 -0700 [thread overview]
Message-ID: <vriu1r4yibln.fsf@gmail.com> (raw)
In-Reply-To: <5e7db95b-7904-a991-5257-8c929efadc57@SystematicSw.ab.ca>
I followed the recent announcements, but unfortunately the problem
persists.
I tested on two computers, with the following ca-certificates versions:
- ca-certificates-2.40-1
- ca-certificates-2.50-1
- ca-certificates-2.50-2
- ca-certificates-2.50-3
- ca-certificates-2.50-3 AND ca-certificates-letsencrypt-2.50-3
In all cases, the result was the same.
From the ca-certificates-letsencrypt-2.50-3 announcement:
> It may be necessary to also remove trust for the already expired DST
> X3 root CA
I'm still trying to figure out _how_ to do this, although I'm not sure
whether it should help my situation. I'll report back with the result.
Some (non-Cygwin) Emacs users reported that GnuTLS >= 3.6.14 works.
next prev parent reply other threads:[~2021-10-06 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 8:22 Jib Style
2021-10-06 7:08 ` Brian Inglis
2021-10-06 12:25 ` Jib Style [this message]
2021-10-06 23:33 ` Jib Style
2021-10-07 6:19 ` ASSI
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vriu1r4yibln.fsf@gmail.com \
--to=jibstyle209@gmail.com \
--cc=cygwin@cygwin.com \
/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).