Re: Linux Security
From: E. Charters (echarters_at_sympatico.ca)
Date: 02/18/05
- Previous message: dude84: "Linux Security"
- In reply to: dude84: "Linux Security"
- Next in thread: dude84: "Re: Linux Security"
- Reply: dude84: "Re: Linux Security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 18 Feb 2005 02:04:13 -0500
did you terminate the string you stacked with a newline character?
--> "\n" ??
otherwise the standard C function printf will fail when you pass it the
address of the stack, which is what I presume you passed it.
The other problem is that stdio.h was not known to be included in your
routine. How do you include it, such that the function knows where to
send the io?
C may be low level and all, but mixing it with assembler may be fraught
with problemos.
EC<:-}
dude84 wrote:
> Hi,
>
> I need assistance with learning how to write assembler code (custom)
> that will work with computer security related issues like a stack based
> buffer overflow. Can anyone point me in the direction of a newsgroup
> that could help me with this?
> I've written a piece of assembler that calls the printf function, and
> when I pass it into the buffer on my machine it does nothing and
> segmentation faults. I'm using gas with gcc. I push the string onto
> the stack call the function, add the memory space back to the stack, and
> call the function to exit the program. I need someone's help to explain
> why the hex code from this program does nothing.
>
>
- Previous message: dude84: "Linux Security"
- In reply to: dude84: "Linux Security"
- Next in thread: dude84: "Re: Linux Security"
- Reply: dude84: "Re: Linux Security"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
