From: Greg KH <gregkh@linuxfoundation.org>
To: Sasha Levin <sashal@kernel.org>
Cc: "Jörg-Volker Peetz" <jvpeetz@web.de>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 5.2.10
Date: Mon, 26 Aug 2019 06:33:28 +0200 [thread overview]
Message-ID: <20190826043328.GB26547@kroah.com> (raw)
In-Reply-To: <20190825223537.GB5281@sasha-vm>
On Sun, Aug 25, 2019 at 06:35:38PM -0400, Sasha Levin wrote:
> Thanks for looking into this!
>
> On Sun, Aug 25, 2019 at 05:26:37PM +0200, Jörg-Volker Peetz wrote:
> > Where can I find your public gpg key and it's fingerprint?
> > It's not yet documented on https://www.kernel.org/category/signatures.html .
>
> You're right, I'll send a patch to add my fingerprint as well.
>
> > I'm asking because the "gpg --locate-keys" method does not work for me.
>
> I can confirm this, and this is weird... I see a kernel.org UID on the
> key, and gpg seems to confirm that as well:
>
> $ gpg --quick-add-uid DEA66FF797772CDC 'Sasha Levin <sashal@kernel.org>'
> gpg: Such a user ID already exists on this key!
>
> Let me contact kernel.org support to see what I'm doing wrong...
Looks like everything is correct from my end:
$ git tag -v v5.2.10
object f7d5b3dc4792a5fe0a4d6b8106a8f3eb20c3c24c
type commit
tag v5.2.10
tagger Sasha Levin <sashal@kernel.org> 1566742490 -0400
This is the 5.2.10 stable release
gpg: Signature made Sun 25 Aug 2019 04:14:50 PM CEST
gpg: using RSA key E27E5D8A3403A2EF66873BBCDEA66FF797772CDC
gpg: Good signature from "Sasha Levin <sashal@kernel.org>" [unknown]
gpg: aka "Sasha Levin <sasha.levin@oracle.com>" [undefined]
gpg: aka "Sasha Levin <alexander.levin@verizon.com>" [unknown]
gpg: aka "Sasha Levin <alexander.levin@microsoft.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: E27E 5D8A 3403 A2EF 6687 3BBC DEA6 6FF7 9777 2CDC
I'll go add yours and Ben's fingerprints to the kernel.org website so
that others can verify it there.
thanks,
greg k-h
next prev parent reply other threads:[~2019-08-26 4:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 14:47 Linux 5.2.10 Sasha Levin
2019-08-25 14:47 ` Sasha Levin
2019-08-25 15:53 ` Bhaskar Chowdhury
2019-08-25 17:33 ` Paul Bolle
2019-08-26 4:34 ` Greg KH
2019-08-26 5:41 ` Bhaskar Chowdhury
2019-08-26 6:10 ` Greg KH
2019-08-26 7:55 ` Paul Bolle
[not found] ` <qju9bd$47qi$1@blaine.gmane.org>
2019-08-25 22:35 ` Sasha Levin
2019-08-26 4:33 ` Greg KH [this message]
2019-08-26 14:02 ` Jörg-Volker Peetz
2019-08-26 14:02 ` Jörg-Volker Peetz
2019-08-26 6:38 ` Bhaskar Chowdhury
2019-08-26 8:01 ` Greg KH
2019-08-26 8:21 ` Greg KH
2019-08-26 8:30 ` Bhaskar Chowdhury
2019-08-26 8:28 ` Bhaskar Chowdhury
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=20190826043328.GB26547@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jvpeetz@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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 NNTP newsgroup(s).