linux-kernel - Re: [GIT PULL] efi/urgent for v5.10-rc6

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-=wiaj3E-UWvwQVuBYzy+=T8MmTyqzFJ34u5sY+Yt9Vnj2g@mail.gmail.com>
Date:   Sun, 29 Nov 2020 10:32:31 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Borislav Petkov <bp@...e.de>, Ard Biesheuvel <ardb@...nel.org>
Cc:     x86-ml <x86@...nel.org>, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] efi/urgent for v5.10-rc6

On Sun, Nov 29, 2020 at 2:42 AM Borislav Petkov <bp@...e.de> wrote:
>
> please pull more forwarded EFI urgent fixes.

Ard seems to be using almost random signing of his tags. Last time it
was signed with subkey 9CD2A0DA, this time it's subkey FBD9627C.

I see that it's all the same primary key, and I'm pretty sure it's
simply because the 9CD2A0DA subkey is about to expire, but these
things take me by surprise when I suddenly see a new key like that.

It would be good to get a heads-up, because otherwise I end up
spending time looking at why I suddenly see a new key...

This is not a problem, it's just a note for people to try to avoid
surprising me..

          Linus