From: Nils Freydank <nils.freydank@posteo.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT: latest longterm kernel.org patches are unsigned
Date: Sun, 19 Aug 2018 22:01:01 +0200 [thread overview]
Message-ID: <3115138.41nusDH7Vv@pygoscelis> (raw)
In-Reply-To: <20180817160712.mlopxb7xpx6ny6qu@matica.foolinux.mooo.com>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
Hi,
kernel.org won’t provide the signatures anymore. I was politely pointed
to the following site via IRC but got no reason for it.
https://www.kernel.org/category/site-news.html
--- Quote ---
No future PGP signatures on patches and changelogs
For legacy purposes, we will continue to provide pre-generated changelogs and
patches (both to the previous mainline and incremental patches to previous
stable). However, from now on they will be generated by automated processes
and will no longer carry detached PGP signatures. If you require
cryptographically verified patches, please generate them directly from the
stable git repository after verifying the PGP signatures on the tags using git
verify-tag.
--- EOQ ---
Am Freitag, 17. August 2018, 18:07:13 CEST schrieb Ian Zimmerman:
> If you browse this URL:
>
> https://cdn.kernel.org/pub/linux/kernel/v4.x/
>
> you'll see that for each 4.14 patch up to 4.14.58 there is a
> cooresponding GPG signature file:
>
> patch-4.14.58.sign 25-Jul-2018 09:28 833
> patch-4.14.58.xz 25-Jul-2018 09:28 1M
>
> etc.
>
> But starting with 4.14.59, there are no .sign files. Why? Is this a
> bug, and if so, where do I report it?
>
> This breaks my lovingly duct-taped kernel update infrastructure ...
--
GPG fingerprint: '00EF D31F 1B60 D5DB ADB8 31C1 C0EC E696 0E54 475B'
Nils Freydank
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-19 20:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 16:07 [gentoo-user] OT: latest longterm kernel.org patches are unsigned Ian Zimmerman
2018-08-19 20:01 ` Nils Freydank [this message]
2018-08-20 21:33 ` james
2018-08-21 3:22 ` J. Roeleveld
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=3115138.41nusDH7Vv@pygoscelis \
--to=nils.freydank@posteo.de \
--cc=gentoo-user@lists.gentoo.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