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] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrUHOe3yP2nyijU8HwUpE6CmSHJWgEGwgEJvdu3BhO+B1A@mail.gmail.com>
Date:	Tue, 11 Mar 2014 10:16:53 -0700
From:	Andy Lutomirski <luto@...capital.net>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Stefani Seibold <stefani@...bold.net>,
	"the arch/x86 maintainers" <x86@...nel.org>,
	Dave Jones <davej@...hat.com>,
	Martin Runge <Martin.Runge@...de-schwarz.com>,
	Andreas Brief <Andreas.Brief@...de-schwarz.com>
Subject: Re: [PATCH v2] x86: Remove compat vdso support

On Tue, Mar 11, 2014 at 10:09 AM, Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
> On Tue, Mar 11, 2014 at 9:50 AM, Andy Lutomirski <luto@...capital.net> wrote:
>> Looking forward, would it be reasonable to have an extensible set of
>> flags that live in the ELF interpreter's headers somewhere
>
> No. Not reasonable. The whole "32-bit x86" and "looking forward"
> combination makes absolutely zero sense.
>
> I can pretty much guarantee that even *phones* will be 64-bit if/when
> x86 ever gets there. They'll need it just for ARM emulation, I bet.
>
> So 32-bit x86 is dead, dead, dead. There's absolutely no future to it.
> We're not adding new stuff to "future-proof" it.

One of those flags is for 64-bit code, though -- it would be nice if
the tasks that don't use the legacy vsyscall page could tell the
kernel, which would allow them to opt into full ASLR.  (There are lots
of legacy programs around that need vsyscall emulation, so there's no
practical way to turn it off with a config option for a very long
time, but vsyscall emulation would be trivial to turn on and off
per-process.)

--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ