linux-kernel - Re: [GIT PULL] efi/urgent for v5.9-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 for Android: free password hash cracker in your pocket

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

Date:   Sun, 20 Sep 2020 15:25:12 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Borislav Petkov <bp@...e.de>
Cc:     Ard Biesheuvel <ardb@...nel.org>, x86-ml <x86@...nel.org>,
        lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] efi/urgent for v5.9-rc6

On Sun, Sep 20, 2020 at 12:33 PM Borislav Petkov <bp@...e.de> wrote:
>
> I'm simply forwarding Ard's tag, I hope that's ok.

That's ok, although it shows perhaps a weakness in our model.

Git actually would have allowed you to create a signed tag pointing to
Ard's tag, and we'd have had the signature chain that way. Although
I'm not even sure the commit signature code has then ever been tested
with that kind of odd situation.

But that might have technically been the best way of doing things
(kind of like sign-offs on commits when forwarding them in email), but
I don't think it really matters.

I just mentioned this odd tag forwarding in the merge commit instead.
It all looks fine, it's just a bit unusual.

           Linus