From: jnf <xjnfx@doityourself.com>
To: Elias Athanasopoulos <eathan@otenet.gr>, ashtrax <xlp@emtel.net.co>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: A exploitable C program
Date: Sun, 14 Jul 2002 02:22:51 -0700 (PDT) [thread overview]
Message-ID: <20020714092251.C9EF82757@sitemail.everyone.net> (raw)
for starts i would go with what Elias had to say, if you dont understand anything of it, perhaps you should start a little higher and just concentrate on the system. c/asm would be where i focused, and i would get handy with a debugger.
here is a link to a paper that i think helps ease people into buffer overflows better than smashing the stack, as i think smashing the stack kinda assumes a basic knowledge of whats going on to some degree, i dunno their both great papers:
http://minimum.inria.fr/%7Eraynal/full-page.php3?page=116
and then these are what ive been working on and i think their the coolest thing since, well i dunno what- but i enjoy them alot:
http://community.core-sdi.com/~gera/InsecureProgramming/
really beyond how c and how those calls in c break into asm, i highly advice you understand the stack and how instructions that manipulate it work...bla bla bla im not gonna say anything you cant learn from reading
_____________________________________________________________
Sign up for FREE email from DoItYourself.com at http://doityourself.com
_____________________________________________________________
Promote your group and strengthen ties to your members with email@yourgroup.org by Everyone.net http://www.everyone.net/?btn=tag
next reply other threads:[~2002-07-14 9:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 9:22 jnf [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-12 14:49 A exploitable C program Huber, George K CECOM RDEC STCD SRI
2002-07-12 4:33 ashtrax
2002-07-12 10:01 ` Elias Athanasopoulos
2002-07-12 20:30 ` ashtrax
2002-07-13 8:27 ` Elias Athanasopoulos
2002-07-15 17:41 ` Marius Nita
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020714092251.C9EF82757@sitemail.everyone.net \
--to=xjnfx@doityourself.com \
--cc=eathan@otenet.gr \
--cc=linux-c-programming@vger.kernel.org \
--cc=xlp@emtel.net.co \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).