lkml.org 
[lkml]   [2013]   [Oct]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [RFC] perf: mmap2 not covering VM_CLONE regions
From
On Wed, Oct 2, 2013 at 3:01 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, Oct 02, 2013 at 02:59:32PM +0200, Stephane Eranian wrote:
>> On Wed, Oct 2, 2013 at 2:46 PM, Peter Zijlstra <peterz@infradead.org> wrote:
>> > On Wed, Oct 02, 2013 at 02:39:53PM +0200, Ingo Molnar wrote:
>> >> - then there are timing attacks, and someone having access to a PMU
>> >> context and who can trigger this SHA1 computation arbitrarily in task
>> >> local context can run very accurate and low noise timing attacks...
>> >>
>> >> I don't think the kernel's sha_transform() is hardened against timing
>> >> attacks, it's performance optimized so it has variable execution time
>> >> highly dependent on plaintext input - which leaks information about the
>> >> plaintext.
>> >
>> > Typical user doesn't have enough priv to profile kernel space; once you
>> > do you also have enough priv to see kernel addresses outright (ie.
>> > kallsyms etc..).
>> >
>> I was going to say just that. But that's not the default, paranoid level
>> is at 1 by default and not 2. So I supposedly can still do:
>
> Oh right you are.. so yes that's a very viable avenue.

You mean simply encoding the vma->vm_mm as the ino number, for instance.


\
 
 \ /
  Last update: 2013-10-02 15:41    [W:0.164 / U:1.928 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site