[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160914150416.2d938c60@lxorguk.ukuu.org.uk>
Date: Wed, 14 Sep 2016 15:04:16 +0100
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Jiri Slaby <jslaby@...e.cz>
Cc: Kees Cook <keescook@...omium.org>,
Greg Kroah-Hartman
<gregkh@...uxfoundation.org>,
kernel-hardening@...ts.openwall.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pty: make ptmx file ops read-only after init
On Wed, 14 Sep 2016 09:59:42 +0200
Jiri Slaby <jslaby@...e.cz> wrote:
> On 09/09/2016, 12:35 AM, Kees Cook wrote:
> > The ptmx_fops structure is only changed during init, so mark it as such.
>
> Right, but I am missing what is the benefit? You would have to elaborate
> here...
The pages end up marked read only even to the kernel (and in future could
even be marked read only forever when in kvm if we get suitable virtual
machine extensions). That makes it much harder to patch those vectors
when making security attacks.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
