From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: brooke@alchemists.io, git@vger.kernel.org
Subject: Re: How to Verify Git GPG Signed Downloads?
Date: Sun, 24 Jan 2021 17:03:56 -0800 [thread overview]
Message-ID: <xmqqh7n5zv2b.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <YA3nwFcYz4tbhrlO@camp.crustytoothpaste.net> (brian m. carlson's message of "Sun, 24 Jan 2021 21:33:52 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
>> $ gpg --list-keys -v 96AFE6CB
>> gpg: using PGP trust model
>> gpg: NOTE: signature key 96AFE6CB expired Sun Jul 26 13:41:24 2020 EDT
>> gpg: NOTE: signature key B3F7CAC9 expired Sun Jul 26 13:41:42 2020 EDT
>> pub 4096R/713660A7 2011-10-01
>> uid Junio C Hamano <gitster@pobox.com>
>> uid Junio C Hamano <junio@pobox.com>
>> uid Junio C Hamano <jch@google.com>
>> sub 4096R/96AFE6CB 2011-10-03 [expired: 2020-07-26]
>> sub 4096R/833262C4 2011-10-01
>> sub 4096R/B3F7CAC9 2014-09-20 [expired: 2020-07-26]
>>
>> It is possible that Junio forgot to push his refreshed public key.
>
> Yes, I think that's the case.
Hmph, I was fairly sure I pushed it out when I refreshed the expiry
date sometime early last year, but apparently it did not go through.
I just tried recv-keys from keys.gnupg.net into a throw-away
GNUPGHOME and got the output at the end, so it should be OK now.
Sorry about that.
$ gpg --list-keys -v 96AFE6CB
gpg: using pgp trust model
pub rsa4096 2011-10-01 [SC]
96E07AF25771955980DAD10020D04E5A713660A7
uid [ unknown] Junio C Hamano <gitster@pobox.com>
uid [ unknown] Junio C Hamano <jch@google.com>
uid [ unknown] Junio C Hamano <junio@pobox.com>
sub rsa4096 2011-10-01 [E]
sub rsa4096 2011-10-03 [S] [expires: 2028-01-11]
sub rsa4096 2014-09-20 [S] [expires: 2028-01-11]
prev parent reply other threads:[~2021-01-25 1:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 16:49 How to Verify Git GPG Signed Downloads? Brooke Kuhlmann
2021-01-24 17:57 ` Jason Pyeron
2021-01-24 21:33 ` brian m. carlson
2021-01-24 22:24 ` Jason Pyeron
2021-01-25 1:03 ` Junio C Hamano [this message]
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=xmqqh7n5zv2b.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=brooke@alchemists.io \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.