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
<[email protected]>" [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.
Thanks,
David
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
> <[email protected]>" [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 [email protected], so we can investigate the problem.
--
~Randy
On 20:59 Wed 05 Aug 2020, 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
><[email protected]>" [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.
>
>Thanks,
>David
You should be using this script to download and verify kernel from
kernel.org ...it there for a reason , please use it...which take away
all the manual labor ..
Here is pointer to get the script :
https://git.kernel.org/pub/scm/linux/kernel/git/mricon/korg-helpers.git/tree/get-verified-tarball
Thanks,
Bhaskar
On Wed, 5 Aug 2020 18:36:08 -0700
Randy Dunlap <[email protected]> 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 <[email protected]>" [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
> [email protected], 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
On Wed, Aug 05, 2020 at 11:20:38PM -0400, David Niklas wrote:
> On Wed, 5 Aug 2020 18:36:08 -0700
> Randy Dunlap <[email protected]> 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 <[email protected]>" [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
> > [email protected], 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.
That means other projects need to change as well :)
And you are not alone, this comes up every release, no problems.
greg k-h