full-disclosure - Re: The story of the Linux kernel 3.x...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <mpro.m440sh02tmwog0cxi.taviso@cmpxchg8b.com>
Date: Wed, 16 May 2012 11:53:06 +0200
From: Tavis Ormandy <taviso@...xchg8b.com>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: The story of the Linux kernel 3.x...

Adam Zabrocki <pi3@....com.pl> wrote:
>
> Btw. I wonder why no-one point this out before... Btw2. Go and write
> reliable exploit for kernel 3.x ;p
> 

You must be using CONFIG_COMPAT_VDSO, it's rarely used unless you need
compatibility with an ancient libc that was released during the narrow
window where the vdso was mapped at a static location.

Any libc released since ~2006 would never need it, and will determine the
vdso location at runtime from auxv.

If any distribution ships a kernel with this option enabled, then you've
found a real issue that needs to be fixed. Did you configure it yourself, or
are you using a stock kernel?

Tavis.

-- 
-------------------------------------
taviso@...xchg8b.com | pgp encrypted mail preferred
-------------------------------------------------------

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/