Re: kaslr should avoid setup_data region

2014-05-08 Thread Dave Young
On 05/08/14 at 12:31pm, Kees Cook wrote: > On Thu, May 8, 2014 at 2:46 AM, Dave Young wrote: > > On 04/24/14 at 03:50pm, Kees Cook wrote: > >> On Wed, Apr 23, 2014 at 7:50 PM, Dave Young wrote: > >> > On 04/23/14 at 07:43pm, Kees Cook wrote: > >> >> On Wed, Apr 23, 2014 at 7:35 PM, Dave Young wr

Re: kaslr should avoid setup_data region

2014-05-08 Thread Kees Cook
On Thu, May 8, 2014 at 2:46 AM, Dave Young wrote: > On 04/24/14 at 03:50pm, Kees Cook wrote: >> On Wed, Apr 23, 2014 at 7:50 PM, Dave Young wrote: >> > On 04/23/14 at 07:43pm, Kees Cook wrote: >> >> On Wed, Apr 23, 2014 at 7:35 PM, Dave Young wrote: >> >> > Hello Kees >> >> > >> >> > I'm worryin

Re: kaslr should avoid setup_data region

2014-05-08 Thread Dave Young
On 04/24/14 at 03:50pm, Kees Cook wrote: > Ah, it sounds like boot_params.hdr.setup_data contains a series of > e820-like entries chained together as a linked list? Which loaders > currently populate that? Looks like EFI? Seems like > arch/x86/boot/compressed/eboot.c works on setup_data at least. >

Re: kaslr should avoid setup_data region

2014-05-05 Thread Dave Young
> I won't be in a position to test EFI booting for a while. If someone > else took this, that would make it get fixed much faster. I will hopefully look into it next week. But as I said I can only test with a hacked kernel which set the randomized addr to the setup_data region. Thanks Dave -- To

Re: kaslr should avoid setup_data region

2014-04-25 Thread Dave Young
On 04/24/14 at 03:50pm, Kees Cook wrote: > Ah, it sounds like boot_params.hdr.setup_data contains a series of > e820-like entries chained together as a linked list? Which loaders > currently populate that? Looks like EFI? Seems like > arch/x86/boot/compressed/eboot.c works on setup_data at least.

Re: kaslr should avoid setup_data region

2014-04-24 Thread H. Peter Anvin
On 04/24/2014 03:50 PM, Kees Cook wrote: > Ah, it sounds like boot_params.hdr.setup_data contains a series of > e820-like entries chained together as a linked list? Which loaders > currently populate that? Looks like EFI? Seems like > arch/x86/boot/compressed/eboot.c works on setup_data at least. >

Re: kaslr should avoid setup_data region

2014-04-24 Thread Kees Cook
Ah, it sounds like boot_params.hdr.setup_data contains a series of e820-like entries chained together as a linked list? Which loaders currently populate that? Looks like EFI? Seems like arch/x86/boot/compressed/eboot.c works on setup_data at least. I won't be in a position to test EFI booting for

Re: kaslr should avoid setup_data region

2014-04-23 Thread Dave Young
On 04/23/14 at 07:43pm, Kees Cook wrote: > On Wed, Apr 23, 2014 at 7:35 PM, Dave Young wrote: > > Hello Kees > > > > I'm worrying that setup_data regions could be overwitten by randomize > > kernel base. Would you like to fix it in kaslr code? > > > > One problem is there could be a lot of setup_d

Re: kaslr should avoid setup_data region

2014-04-23 Thread Kees Cook
On Wed, Apr 23, 2014 at 7:35 PM, Dave Young wrote: > Hello Kees > > I'm worrying that setup_data regions could be overwitten by randomize > kernel base. Would you like to fix it in kaslr code? > > One problem is there could be a lot of setup_data regions but current > mem_avoid is an fixed array.