From: Jim Garrison <jhg@jhmg.net>
To: cygwin@cygwin.com
Subject: setup-x86_64.exe gpg signing key expired?
Date: Fri, 2 Sep 2022 14:47:51 -0700 [thread overview]
Message-ID: <4fc205ea-6501-c983-297b-97610d39e9c7@jhmg.net> (raw)
It appears the key expired 2022-02-26, so I presume this is known. I
bring it up on the slim chance it hasn't been noticed or reported yet.
$ gpg --verify setup-x86_64.exe.sig
gpg: assuming signed data in 'setup-x86_64.exe'
gpg: Signature made Fri, Jun 24, 2022 05:48:55 PDT
gpg: using DSA key 1169DF9F22734F743AA59232A9A262FF676041BA
gpg: checking the trustdb
gpg: public key CCB2EB46E76CF6D0 is 35475 seconds newer than the signature
gpg: marginals needed: 3 completes needed: 1 trust model: classic
gpg: depth: 0 valid: 3 signed: 3 trust: 0-, 0q, 0n, 0m, 0f, 3u
gpg: depth: 1 valid: 3 signed: 0 trust: 2-, 0q, 0n, 0m, 1f, 0u
gpg: next trustdb check due at 2023-04-30
gpg: Good signature from "Cygwin <cygwin@cygwin.com>" [full]
gpg: Signature made Fri, Jun 24, 2022 05:48:55 PDT
gpg: using RSA key 56405CF6FCC81574682A5D561A698DE9E2E56300
gpg: Good signature from "Cygwin <cygwin@cygwin.com>" [expired]
gpg: Note: This key has expired!
Primary key fingerprint: 5640 5CF6 FCC8 1574 682A 5D56 1A69 8DE9 E2E5 6300
...and...
$ gpg -k 56405CF6FCC81574682A5D561A698DE9E2E56300
pub rsa4096 2020-02-27 [SC] [expired: 2022-02-26]
56405CF6FCC81574682A5D561A698DE9E2E56300
uid [ expired] Cygwin <cygwin@cygwin.com>
Cheers!
--
Jim Garrison
jhg@acm.org
next reply other threads:[~2022-09-02 21:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 21:47 Jim Garrison [this message]
2022-09-02 22:25 ` Jon Turney
2022-09-02 22:45 ` Jim Garrison
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=4fc205ea-6501-c983-297b-97610d39e9c7@jhmg.net \
--to=jhg@jhmg.net \
--cc=cygwin@cygwin.com \
--cc=jhg@acm.org \
/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).