On Tue, Oct 1, 2013 at 10:30 PM, H. Peter Anvin wrote:
> On 10/01/2013 10:25 PM, Ingo Molnar wrote:
>>
>> I mean, for example in an oops message we print data in words: the RIP,
>> other registers and stack contents. If any of these values lies within the
>> randomization range then we could
On 10/01/2013 10:25 PM, Ingo Molnar wrote:
>
> I mean, for example in an oops message we print data in words: the RIP,
> other registers and stack contents. If any of these values lies within the
> randomization range then we could de-randomize it.
>
> So instead of exposing randomized values,
* H. Peter Anvin wrote:
> I think that the randomization offset would be necessary in order to
> identify pointers.
I mean, for example in an oops message we print data in words: the RIP,
other registers and stack contents. If any of these values lies within the
randomization range then we
I think that the randomization offset would be necessary in order to identify
pointers.
Ingo Molnar wrote:
>
>* Kees Cook wrote:
>
>> Here is the latest version of the kASLR series. It has much improved
>> e820 walking code, and expands the window available on 64-bit.
>>
>> This is rolled
* Kees Cook wrote:
> Here is the latest version of the kASLR series. It has much improved
> e820 walking code, and expands the window available on 64-bit.
>
> This is rolled out on Chrome OS devices, and working well.
There's one kernel debuggability detail that should be discussed I think:
Here is the latest version of the kASLR series. It has much improved
e820 walking code, and expands the window available on 64-bit.
This is rolled out on Chrome OS devices, and working well.
-Kees
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
Here is the latest version of the kASLR series. It has much improved
e820 walking code, and expands the window available on 64-bit.
This is rolled out on Chrome OS devices, and working well.
-Kees
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
* Kees Cook keesc...@chromium.org wrote:
Here is the latest version of the kASLR series. It has much improved
e820 walking code, and expands the window available on 64-bit.
This is rolled out on Chrome OS devices, and working well.
There's one kernel debuggability detail that should be
I think that the randomization offset would be necessary in order to identify
pointers.
Ingo Molnar mi...@kernel.org wrote:
* Kees Cook keesc...@chromium.org wrote:
Here is the latest version of the kASLR series. It has much improved
e820 walking code, and expands the window available on
* H. Peter Anvin h...@zytor.com wrote:
I think that the randomization offset would be necessary in order to
identify pointers.
I mean, for example in an oops message we print data in words: the RIP,
other registers and stack contents. If any of these values lies within the
randomization
On 10/01/2013 10:25 PM, Ingo Molnar wrote:
I mean, for example in an oops message we print data in words: the RIP,
other registers and stack contents. If any of these values lies within the
randomization range then we could de-randomize it.
So instead of exposing randomized values, we
On Tue, Oct 1, 2013 at 10:30 PM, H. Peter Anvin h...@zytor.com wrote:
On 10/01/2013 10:25 PM, Ingo Molnar wrote:
I mean, for example in an oops message we print data in words: the RIP,
other registers and stack contents. If any of these values lies within the
randomization range then we could
12 matches
Mail list logo