[lkml]   [2011]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] x86-64, vsyscalls: Rename UNSAFE_VSYSCALLS to COMPAT_VSYSCALLS
On Mon, Jun 06, 2011 at 12:24:19PM +0200, Ingo Molnar wrote:
> When: When glibc 2.14 or newer is ubitquitous. Perhaps mid-2012.
> -Why: Having user-executable code at a fixed address is a security problem.
> - Turning off CONFIG_UNSAFE_VSYSCALLS mostly removes the risk but will
> +Why: Having user-executable syscall invoking code at a fixed addresses makes
> + it easier for attackers to exploit security holes.
> + Turning off CONFIG_COMPAT_VSYSCALLS mostly removes the risk but will
> make the time() function slower on glibc versions 2.13 and below.
> Who: Andy Lutomirski <>

I'd suggest 2013 or 2014, at least. People using Ubuntu LTS and RHEL
6 are stuck back at glibc 2.11, and many of those users do like being
able to upgrade to newer kernels. And there are probably are a large
number of static binaries around.

Maybe in 2012 or so we change the to be 'no' (and I'd suggest adding a
comment in the feature-removal-schedule.txt file that this will also
break static binaries).


- Ted

 \ /
  Last update: 2011-06-06 14:23    [W:0.139 / U:2.652 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site