linux-kernel - Re: NonExecutable Bit in 32Bit

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]

Date:	Tue, 24 Apr 2007 09:46:12 +0200
From:	"Tuncer Ayaz" <tuncer.ayaz@...il.com>
To:	"William Heimbigner" <icxcnika@....tar.cc>
Cc:	"Cestonaro, Thilo (external)" 
	<Thilo.Cestonaro.external@...itsu-siemens.com>,
	linux-kernel@...r.kernel.org
Subject: Re: NonExecutable Bit in 32Bit

On 4/24/07, William Heimbigner <icxcnika@....tar.cc> wrote:
> On Tue, 24 Apr 2007, Cestonaro, Thilo (external) wrote:
>
> > Hey,
> >
> > is it right, that the NX Bit is not used under i386-Arch but
> > under x86_64-Arch?
> > When yes, is there a special argument for it not to be used?
> >
> > Ciao Thilo
> I don't think so - some i386 cpus definitely have support for
> the NX bit.
>

In detail:
1) if your CPU has NX support (some 32bit Xeons do)
2) it is not disabled in the BIOS
3) you see 'nx' in the 'flags' line in /proc/cpuinfo
4) and you have a kernel with the following config options
CONFIG_HIGHMEM64G=y
CONFIG_HIGHMEM=y
CONFIG_X86_PAE=y

NX should just work.

[snip]
-
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/