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]
Date:	Thu, 4 Aug 2016 16:55:19 +0000
From:	"Roberts, William C" <william.c.roberts@...el.com>
To:	"kernel-hardening@...ts.openwall.com" 
	<kernel-hardening@...ts.openwall.com>,
	"jason@...edaemon.net" <jason@...edaemon.net>,
	"linux-mm@...r.kernel.org" <linux-mm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
CC:	"keescook@...omium.org" <keescook@...omium.org>,
	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
	"nnk@...gle.com" <nnk@...gle.com>,
	"jeffv@...gle.com" <jeffv@...gle.com>,
	"salyzyn@...roid.com" <salyzyn@...roid.com>,
	"dcashman@...roid.com" <dcashman@...roid.com>
Subject: RE: [kernel-hardening] [PATCH] [RFC] Introduce mmap randomization

> -----Original Message-----
> From: Daniel Micay [mailto:danielmicay@...il.com]
> Sent: Thursday, August 4, 2016 9:53 AM
> To: kernel-hardening@...ts.openwall.com; jason@...edaemon.net; linux-
> mm@...r.kernel.org; linux-kernel@...r.kernel.org; akpm@...ux-
> foundation.org
> Cc: keescook@...omium.org; gregkh@...uxfoundation.org; nnk@...gle.com;
> jeffv@...gle.com; salyzyn@...roid.com; dcashman@...roid.com
> Subject: Re: [kernel-hardening] [PATCH] [RFC] Introduce mmap randomization
> 
> On Tue, 2016-07-26 at 11:22 -0700, william.c.roberts@...el.com wrote:
> > The recent get_random_long() change in get_random_range() and then the
> > subsequent patches Jason put out, all stemmed from my tinkering with
> > the concept of randomizing mmap.
> >
> > Any feedback would be greatly appreciated, including any feedback
> > indicating that I am idiot.
> 
> The RAND_THREADSTACK feature in grsecurity makes the gaps the way I think
> would be ideal, i.e. tracked as part of the appropriate VMA. It would be
> straightforward to make it more general purpose.

I am not familiar with that, thanks for pointing it out. I'll take a look when my time
frees up for this again.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ