Re: SV: Avoiding Buffer Overflows
From: Trano (Trano@gmx.net)Date: 01/10/02
- Previous message: S. Sargent \: "Re: Question about security !!!"
- In reply to: lists@notatla.demon.co.uk: "Re: SV: Avoiding Buffer Overflows"
- Next in thread: lists@notatla.demon.co.uk: "Re: SV: Avoiding Buffer Overflows"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Thu, 10 Jan 2002 08:01:16 +0100 From: Trano <Trano@gmx.net> To: "lists@notatla.demon.co.uk" <security-discuss@linuxsecurity.com>
Hi.
> Yes. You need to return from the current function for the return address
> to be used.
Hum, sorry I don't understand you completely.
Could you show me how the stack looks like in the example with the
exit-call?
In a 'normal' case it would look like this:
[100 byte buf][4 byte EBP][4 byte EIP]
If you now start the program with more than 108 chars as argument it
should exit with "Segmentation fault [...] in address 0x41414141",
shouldn't it?
But I can't see why it sould behave in another way when exit is
used... :-/
thx&bye
Tom
------------------------------------------------------------------------
To unsubscribe email security-discuss-request@linuxsecurity.com
with "unsubscribe" in the subject of the message.
- Previous message: S. Sargent \: "Re: Question about security !!!"
- In reply to: lists@notatla.demon.co.uk: "Re: SV: Avoiding Buffer Overflows"
- Next in thread: lists@notatla.demon.co.uk: "Re: SV: Avoiding Buffer Overflows"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]