From: Matt Brown <matt@nmatt.com>
To: James Morris <jmorris@namei.org>,
Boris Lukashev <blukashev@sempervictus.com>
Cc: Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Greg KH <gregkh@linuxfoundation.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Kees Cook <keescook@chromium.org>,
kernel-hardening@lists.openwall.com,
linux-security-module <linux-security-module@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [kernel-hardening] Re: [PATCH v7 2/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN
Date: Wed, 31 May 2017 00:10:17 -0400 [thread overview]
Message-ID: <cb0daac8-bd8d-0780-cf04-46033f8fea10@nmatt.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1705311239420.6920@namei.org>
On 05/30/2017 10:48 PM, James Morris wrote:
> On Mon, 29 May 2017, Boris Lukashev wrote:
>
>> With all due respect sir, i believe your review falls short of the
>> purpose of this effort - to harden the kernel against flaws in
>> userspace.
>
> Which effort? Kernel self protection is about protecting against flaws in
> the kernel.
>
> See:
> https://kernsec.org/wiki/index.php/Kernel_Self_Protection_Project
>
> "This project starts with the premise that kernel bugs have a very long
> lifetime, and that the kernel must be designed in ways to protect against
> these flaws."
>
> We need to avoid conflating:
>
> - hardening the kernel against attack; and
> - modifying the kernel to try and harden userspace.
>
> These patches are the latter, and the case for them is not as
> straightforward.
>
>
> - James
>
I agree that these patches aren't kernel self protection and I don't
believe I have claimed they are such a thing. These patches I'm
presenting are more akin to ptrace protections that are found in Yama.
next prev parent reply other threads:[~2017-05-31 4:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 21:37 [PATCH v7 0/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN Matt Brown
2017-05-29 21:37 ` [PATCH v7 1/2] security: tty: Add owner user namespace to tty_struct Matt Brown
2017-05-29 21:38 ` [PATCH v7 2/2] security: tty: make TIOCSTI ioctl require CAP_SYS_ADMIN Matt Brown
2017-05-29 22:26 ` Alan Cox
2017-05-29 23:51 ` [kernel-hardening] " Boris Lukashev
2017-05-30 0:27 ` Casey Schaufler
2017-05-30 2:00 ` Matt Brown
2017-05-30 2:46 ` Casey Schaufler
2017-05-30 3:18 ` Matt Brown
2017-05-30 12:24 ` Alan Cox
2017-05-30 16:28 ` Matt Brown
2017-05-30 16:44 ` Daniel Micay
2017-05-30 18:32 ` Stephen Smalley
2017-05-30 18:44 ` Nick Kralevich
2017-05-30 18:57 ` Matt Brown
2017-05-30 20:22 ` Daniel Micay
2017-05-30 23:00 ` Matt Brown
2017-05-30 23:40 ` Daniel Micay
2017-05-30 23:59 ` Matt Brown
2017-05-30 22:51 ` Alan Cox
2017-05-30 23:19 ` Matt Brown
2017-05-30 23:56 ` Alan Cox
2017-06-01 2:35 ` Kees Cook
2017-06-01 13:08 ` Alan Cox
2017-06-01 17:18 ` Serge E. Hallyn
2017-06-01 21:26 ` Alan Cox
2017-06-01 18:58 ` Kees Cook
2017-06-01 21:24 ` Alan Cox
2017-06-02 14:46 ` Matt Brown
2017-06-02 15:36 ` Serge E. Hallyn
2017-06-02 16:02 ` Matt Brown
2017-06-02 16:57 ` Serge E. Hallyn
2017-06-02 17:32 ` Matt Brown
2017-06-02 18:18 ` Serge E. Hallyn
2017-06-02 19:22 ` Matt Brown
2017-06-02 19:25 ` Kees Cook
2017-06-02 19:26 ` Matt Brown
2017-06-02 20:05 ` Alan Cox
2017-06-02 20:11 ` Nick Kralevich
2017-06-02 20:46 ` Matt Brown
2017-06-03 22:00 ` Alan Cox
2017-06-03 22:22 ` Matt Brown
2017-06-04 3:37 ` Peter Dolding
2017-05-30 15:20 ` Casey Schaufler
2017-05-30 16:09 ` Matt Brown
2017-06-04 6:29 ` Boris Lukashev
2017-05-31 2:48 ` James Morris
2017-05-31 4:10 ` Matt Brown [this message]
2017-05-30 0:15 ` Matt Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cb0daac8-bd8d-0780-cf04-46033f8fea10@nmatt.com \
--to=matt@nmatt.com \
--cc=blukashev@sempervictus.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).