linux-kernel - Re: [GIT PULL] Crypto Update for 5.18

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-=wix0F2nwk8v2Hmo-x6Yr0PEji9=oMTewk6YhL+ATM2fVg@mail.gmail.com>
Date:   Mon, 21 Mar 2022 16:14:50 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Herbert Xu <herbert@...dor.apana.org.au>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Crypto Mailing List <linux-crypto@...r.kernel.org>
Subject: Re: [GIT PULL] Crypto Update for 5.18

On Sun, Mar 20, 2022 at 4:42 PM Herbert Xu <herbert@...dor.apana.org.au> wrote:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus

So perhaps somewhat ironically, the crypto tree is now the first tree
I'm merging in this merge window that doesn't have a signed tag.

I don't require signed tags for kernel.org pulls, but I really do
heavily prefer them, and they aren't that hard to do.

I'm sure there are several other non-signed pull requests waiting in
the queue, but still, your pull request stands out as being the first
one - out of 27 so far - that didn't have it.

Can I prod you in the direction of making signed tags a part of your
workflow? The tag can contain the details of the pull - in which case
git request-pull will populate the pull request with it - or it can be
just some dummy message and you write the details separately in the
pull request email like you do now.

I know you have a pgp key, because I have one in my keyring from you
going all the way back to 2011. And if you have lost sight of that one
and need to create a new one, that still better going forward than not
signing your pull requests at all..

            Linus