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: 13 Aug 2003 14:26:04 -0400 From: "Jonathan A. Zdziarski" <jonathan@...workdweebs.com> To: "Eygene A. Ryabinkin" <rea@....mbslab.kiae.ru> Subject: Re: Buffer overflow prevention I think this is overkill and will probably cause your applications to run much slower than they already do. I don't see why one couldn't simply put the variable information *after* the rest of the stack information, instead of before, and have the kernel zero out the next stack frame before it gets written to (although this may cause some performance problems in itself). This would prevent a buffer overflow from A) overwriting SS:ESP and B) overflowing code onto the next stackframe.
Powered by blists - more mailing lists