linux-kernel - Re: [PATCH 0/3] stream

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]

Date:   Tue, 7 May 2019 11:54:21 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Kirill Smelkov <kirr@...edi.com>
Cc:     Al Viro <viro@...iv.linux.org.uk>, Arnd Bergmann <arnd@...db.de>,
        Christoph Hellwig <hch@....de>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Pavel Machek <pavel@...x.de>,
        Rasmus Villemoes <linux@...musvillemoes.dk>,
        Miklos Szeredi <miklos@...redi.hu>,
        linux-fsdevel <linux-fsdevel@...r.kernel.org>,
        Linux List Kernel Mailing <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] stream_open bits for Linux 5.2

On Mon, May 6, 2019 at 10:20 AM Kirill Smelkov <kirr@...edi.com> wrote:
>
> Maybe it will help: the patches can be also pulled from here:
>
>         git pull https://lab.nexedi.com/kirr/linux.git y/stream_open-5.2

I'll take this, but I generally *really* want a signed tag for
non-kernel.org git tree sources. The gpg key used for signing doesn't
necessarily even have to be signed by others yet, but just the fact
that there's a pgp key means that then future pulls at least verify
that it's the sam,e controlling entity, and we can get the signatures
later.

For something one-time where I will then look through the details of
each commit it's not like I absolutely require it, which is why I'm
pulling it, but just in general I wanted to point this out.

                        Linus