Re: Buffer overflow prevention
From: Jonathan A. Zdziarski (jonathan_at_networkdweebs.com)
Date: 08/13/03
- Previous message: Phrack Staff: "Phrack #61 is OUT!"
- In reply to: Eygene A. Ryabinkin: "Buffer overflow prevention"
- Next in thread: Andreas Beck: "Re: Buffer overflow prevention"
- Reply: Andreas Beck: "Re: Buffer overflow prevention"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: "Eygene A. Ryabinkin" <rea@rea.mbslab.kiae.ru> Date: 13 Aug 2003 14:26:04 -0400
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.
- Previous message: Phrack Staff: "Phrack #61 is OUT!"
- In reply to: Eygene A. Ryabinkin: "Buffer overflow prevention"
- Next in thread: Andreas Beck: "Re: Buffer overflow prevention"
- Reply: Andreas Beck: "Re: Buffer overflow prevention"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Loading