Re: [PATCH v5 4/7] introduce post-init read-only memory

2016-03-07 Thread Andy Lutomirski
On Mon, Mar 7, 2016 at 4:16 PM, Kees Cook wrote: > On Mon, Mar 7, 2016 at 5:00 AM, Christian Borntraeger > wrote: >> On 02/17/2016 11:41 PM, Kees Cook wrote: >>> One of the easiest ways to protect the kernel from attack is to reduce >>> the internal attack surface exposed when a "write" flaw is a

Re: [PATCH v5 4/7] introduce post-init read-only memory

2016-03-07 Thread Kees Cook
On Mon, Mar 7, 2016 at 5:00 AM, Christian Borntraeger wrote: > On 02/17/2016 11:41 PM, Kees Cook wrote: >> One of the easiest ways to protect the kernel from attack is to reduce >> the internal attack surface exposed when a "write" flaw is available. By >> making as much of the kernel read-only as

Re: [PATCH v5 4/7] introduce post-init read-only memory

2016-03-07 Thread Christian Borntraeger
On 02/17/2016 11:41 PM, Kees Cook wrote: > One of the easiest ways to protect the kernel from attack is to reduce > the internal attack surface exposed when a "write" flaw is available. By > making as much of the kernel read-only as possible, we reduce the > attack surface. > > Many things are wri