[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 8 Apr 2013 08:35:21 +0300
From: Hasinoliva MIARIMANJATO <hasinoliva@...il.com>
To: kernel-hardening@...ts.openwall.com
Subject: Re: Re: [PATCH 1/3] x86: routines to choose random
kernel base offset
Hi i want to get so more information about pohmelfs ; i want to get
pohmelfs server and pohmelfs client that i don't find it in the internet ,
please help me
thank you.
2013/4/8 Hasinoliva MIARIMANJATO <hasinoliva@...il.com>
> Hi i want to get so more information about pohmelfs ; i want to get
> pohmelfs server and pohmelfs client that i don't find it in the internet ,
> please help me
>
> thank you.
>
>
> 2013/4/5 H. Peter Anvin <hpa@...or.com>
>
> On 04/05/2013 12:36 AM, Ingo Molnar wrote:
>> >
>> > * Ingo Molnar <mingo@...nel.org> wrote:
>> >
>> >>
>> >> * Kees Cook <keescook@...omium.org> wrote:
>> >>
>> >>> This provides routines for selecting a randomized kernel base offset,
>> >>> bounded by e820 details. It tries to use RDRAND and falls back to
>> RDTSC.
>> >>> If "noaslr" is on the kernel command line, no offset will be used.
>> >>
>> >> Would it make sense to also add three other sources of entropy:
>> >
>> > In any case, would it be possible to also mix these bootup sources of
>> > entropy into our regular random pool?
>> >
>> > That would improve random pool entropy on all Linux systems, not just
>> > those that choose to enable kernel-base-address randomization.
>> >
>>
>> I think we already do at least some of these, but at this point, for any
>> non-RDRAND-capable hardware we could almost certainly do better for any
>> definition of anything at all.
>>
>> RDRAND is obviously the ultimate solution here.
>>
>> -hpa
>>
>>
>>
>
Content of type "text/html" skipped
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.
