bugtraq - Re: Buffer overflow prevention

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: <F289F033-CE8B-11D7-B43D-000393CC2E90@iki.fi>
Date: Thu, 14 Aug 2003 22:17:29 +0300
From: Timo Sirainen <tss@....fi>
To: Mariusz Woloszyn <emsi@...rtners.pl>
Subject: Re: Buffer overflow prevention

On Thursday, Aug 14, 2003, at 20:26 Europe/Helsinki, Mariusz Woloszyn 
wrote:

> On Thu, 14 Aug 2003, Stephen Clowater wrote:
>
>> Also, you can use chpax, and turn on a non-executable stack, and with 
>> a small
> It's been proved many times that non-executable stack adds NO security 
> at
> all.
> Every single class of vulnerabilities exploitable with executable stack
> can be also exploited with non-executable stack.

What he forgot to mention is that PAX and grsec also gives you 
non-executable heap and randomized address bases to prevent 
return-to-libc attacks. AFAIK all those combined do bring real security 
against generic exploits.