linux-kernel - Re: [GIT PULL] Security subsystem updates for v4.16

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: <CA+55aFw1vWWmv5Ebq9yWVDFm4SQUG_fNd3f5yoYkWRTfUNaL_Q@mail.gmail.com>
Date:   Wed, 31 Jan 2018 13:21:44 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     James Morris <jmorris@...ei.org>, Kees Cook <keescook@...omium.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        LSM List <linux-security-module@...r.kernel.org>
Subject: Re: [GIT PULL] Security subsystem updates for v4.16

On Sun, Jan 28, 2018 at 3:41 PM, James Morris <jmorris@...ei.org> wrote:
>
> Note that individual trees may also be pulled via:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git
>         next-integrity
>         next-smack
>         next-tpm

So I did that, because it makes it easier and more controlled for me.
But then when double-checking that the end result is identical to your
full pull request, I end up missing the seccomp tree.

I can pull that separately too, but it was missing explanations and a
real pull request, so I left it alone.

           Linus