linux-kernel - Re: [GIT PULL] NFSD fixes for v6.14

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHk-=wimOy=E0bKyH99cL6H0+C-k4q_iZB45t56eSdQ+UM2umA@mail.gmail.com>
Date: Mon, 10 Feb 2025 13:21:09 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: cel@...nel.org
Cc: Jeff Layton <jlayton@...nel.org>, linux-nfs@...r.kernel.org, 
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] NFSD fixes for v6.14

On Mon, 10 Feb 2025 at 10:59, <cel@...nel.org> wrote:
>
> Note that my GPG key expired a few days ago. I renewed it with no
> expiry and pushed it to pgp.mit.edu earlier today.

Thanks for the note. Can you send the update to kernel.org too, so
that the key repo there gets updated too? That tends to be my primary
way to get key updates, because the pgp keyservers are inevitably
flaky and unreliable as all heck, ie

  gpg: refreshing 1 key from hkp://pgp.mit.edu
  gpg: keyserver refresh failed: No keyserver available

and the pgp.mit.edu web interface seems to be broken too.

Anyway, I've done the pull, but this is just one reason I hate people
putting expiration dates on their keys: the key server infrastructure
has been so broken for years that it's just a pain.

              Linus