Date: Fri, 18 Dec 2015 16:54:33 +0000 From: "Schaufler, Casey" <casey.schaufler@...el.com> To: "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com> Subject: RE: Introduction > -----Original Message----- > From: Daniel Micay [mailto:danielmicay@...il.com] > Sent: Thursday, December 17, 2015 4:49 PM > To: kernel-hardening@...ts.openwall.com > Subject: Re: [kernel-hardening] Introduction > > On Thu, 2015-12-17 at 16:36 -0800, Kees Cook wrote: > > On Thu, Dec 17, 2015 at 3:34 PM, Leibowitz, Michael > > <michael.leibowitz@...el.com> wrote: > > > I work in Intel's Open Source Technology center, along with my > > > colleague, Elena Reshetova. I'm reasonably new real-life kernel > > > development, having previously just mucked about. Otherwise, I'm a > > > long-time open source/security trouble maker. > > > > Hi! Welcome! :) > > > > > I'm Interested in working on struct randomization ala RANDSTRUCT. > > > Does this seem like a suitable task? > > > > I certainly wouldn't turn it down, but I would observe that it has > > some limited utility to users of the kernel that produce binary > > builds. e.g. all the given builds of Ubuntu with RANDSTRUCT would be > > the same (though the next released version would see a different > > randomization, etc). It also complicates externally built modules. I > > see it depends on HIDESYM, though, which in turn depends on > > PAX_USERCOPY, so it would be much weaker without these two finished > > first. I'm working on teasing the PAX_USERCOPY implementation out of the greater grsecurity patch. I am reminded of a time when I had to pull a group of small splinters from my hand. Both for the difficulty in finding all of them, and the pain involved. I hope to have something limping along by the end of the month, holiday cheer permitting.
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.