| 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
| ||
|
Date: Mon, 11 Dec 2006 20:53:57 +0100 From: Eric Piel <Eric.Piel@...mplin-utc.net> To: Kyle McMartin <kyle@...ntu.com> Cc: John Richard Moser <nigelenki@...cast.net>, linux-kernel@...r.kernel.org Subject: Re: noexec=on doesn't work 12/09/2006 09:03 PM, Kyle McMartin wrote/a écrit: > On Sat, Dec 09, 2006 at 02:34:47PM -0500, John Richard Moser wrote: >> I have filed this as a distro bug with Ubuntu; it may be their issue, I >> haven't dug deep enough to find out. I am posting this here to disperse >> the information breadth-first instead of depth-first, which will shorten >> the bug's life cycle if it turns out to be an upstream bug. >> > > NX requires the 64-bit page table entries (ie, PAE) which requires > CONFIG_HIGHMEM64G. Somehow there is a problem: a user can explicitly put "noexec=on" and it will be silently ignored if the kernel doesn't have PAE support. I guess that currently no message is written because "noexec=on" is the _default_. Still, it would be fair to the user who added "noexec=on" on its command line that if it is not respected, either because the hardware doesn't support it or because the kernel doesn't support it, we display a warning saying it's hopeless. I'll send a patch if it seems meaningful to you, c u Eric - 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