From: David Niklas <Hgntkwis@vfemail.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Is anyone else getting a bad signature from kernel.org's 5.8 sources+Greg's sign?
Date: Wed, 5 Aug 2020 23:20:38 -0400 [thread overview]
Message-ID: <20200805232038.7a1767cc@Phenom-II-x6.niklas.com> (raw)
In-Reply-To: <5a943a1f-c5ef-937f-f67e-1c59c04d63fb@infradead.org>
On Wed, 5 Aug 2020 18:36:08 -0700
Randy Dunlap <rdunlap@infradead.org> wrote:
> On 8/5/20 5:59 PM, David Niklas wrote:
> > Hello,
> > I downloaded the kernel sources from kernel.org using curl, then
> > opera, and finally lynx (to rule out an html parsing bug). I did the
> > same with the sign and I keep getting:
> >
> > % gpg2 --verify linux-5.8.tar.sign linux-5.8.tar.xz
> > gpg: Signature made Mon Aug 3 00:19:13 2020 EDT
> > gpg: using RSA key
> > 647F28654894E3BD457199BE38DBBDC86092693E gpg: BAD signature from
> > "Greg Kroah-Hartman <gregkh@linuxfoundation.org>" [unknown]
> >
> > I did refresh all the keys just in case.
> > I believe this is important so I'm addressing this to the signer and
> > only CC'ing the list.
> >
> > If I'm made some simple mistake, feel free to send SIG666 to my
> > terminal. I did re-read the man page just in case.
>
> It works successfully for me.
>
>
> from https://www.kernel.org/category/signatures.html::
>
>
> If you get "BAD signature"
>
> If at any time you see "BAD signature" output from "gpg2 --verify",
> please first check the following first:
>
> Make sure that you are verifying the signature against the .tar
> version of the archive, not the compressed (.tar.xz) version. Make sure
> the the downloaded file is correct and not truncated or otherwise
> corrupted.
>
> If you repeatedly get the same "BAD signature" output, please email
> helpdesk@kernel.org, so we can investigate the problem.
>
>
>
Many thanks. I've never seen a signature done that way before, but I
understand why you would do it that way.
David
next prev parent reply other threads:[~2020-08-06 3:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 0:59 David Niklas
2020-08-06 1:36 ` Randy Dunlap
2020-08-06 3:20 ` David Niklas [this message]
2020-08-06 5:40 ` Greg Kroah-Hartman
2020-08-06 1:54 ` Re:Use the script already there.. " 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=20200805232038.7a1767cc@Phenom-II-x6.niklas.com \
--to=hgntkwis@vfemail.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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
all inboxes | Powered by JetHome®