linux-kernel - Re: [PATCH v4 00/15] exec: Use sane stack rlimit under secureexec

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] [day] [month] [year] [list]

Date:   Tue, 1 Aug 2017 14:04:42 -0700
From:   Kees Cook <keescook@...omium.org>
To:     Linus Torvalds <torvalds@...ux-foundation.org>
Cc:     James Morris <jmorris@...ei.org>,
        Andrew Morton <akpm@...ux-foundation.org>,
        David Howells <dhowells@...hat.com>,
        "Eric W. Biederman" <ebiederm@...ssion.com>,
        John Johansen <john.johansen@...onical.com>,
        "Serge E. Hallyn" <serge@...lyn.com>,
        Paul Moore <paul@...l-moore.com>,
        Stephen Smalley <sds@...ho.nsa.gov>,
        Casey Schaufler <casey@...aufler-ca.com>,
        Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
        James Morris <james.l.morris@...cle.com>,
        Andy Lutomirski <luto@...nel.org>,
        "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
        linux-security-module <linux-security-module@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 00/15] exec: Use sane stack rlimit under secureexec

On Tue, Aug 1, 2017 at 1:19 PM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Tue, Aug 1, 2017 at 8:04 AM, Kees Cook <keescook@...omium.org> wrote:
>>
>> Do you want me to carry this for -next and send it as a distinct pull
>> request for v4.14?
>
> Yes, I think that would be preferred. I consider this a "execve()"
> cleanup/change with implications for the security models rather than
> the other way around, so I'd rather keep it separate, and you already
> have a few other git trees so I think it makes sense to just treat it
> as another of your git pulls next merge window.

Okay, sounds good. Thanks!

-Kees

-- 
Kees Cook
Pixel Security