From: Elias Athanasopoulos <eathan@otenet.gr>
To: ashtrax <xlp@emtel.net.co>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: A exploitable C program
Date: Fri, 12 Jul 2002 13:01:06 +0300 [thread overview]
Message-ID: <20020712130106.A4048@neutrino.particles.org> (raw)
In-Reply-To: <20020711233356.F343@nietzsche.metrotel.net.co>; from xlp@emtel.net.co on Thu, Jul 11, 2002 at 11:33:56PM -0500
On Thu, Jul 11, 2002 at 11:33:56PM -0500, ashtrax wrote:
> Hi, I keep trying to understand buffer overflow, I would like you help me finding a exploitable C program, not so complex, that demands me a serious and deep analysis of how find shellcode, elf disamble and other process I already ignore.
> I want to have the ability of release proof of concept exploit and understand credentials, setiud root and all secure programming topics.
> What program do you suggest for have a good start?
Please, use a mail client with a sane wrapping.
The most combrehensive tutorial regarding buffer overflow, AFAIK, is:
http://www.shmoo.com/phrack/Phrack49/p49-14
It doesn't cover non-executable stacks though. I doubt that you'll test
your code in an OS which provides non-executable stacks.
Elias
--
http://gnewtellium.sourceforge.net MP3 is not a crime.
next prev parent reply other threads:[~2002-07-12 10:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 4:33 A exploitable C program ashtrax
2002-07-12 10:01 ` Elias Athanasopoulos [this message]
2002-07-12 20:30 ` ashtrax
2002-07-13 8:27 ` Elias Athanasopoulos
2002-07-15 17:41 ` Marius Nita
-- strict thread matches above, loose matches on Subject: below --
2002-07-12 14:49 Huber, George K CECOM RDEC STCD SRI
2002-07-14 9:22 jnf
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=20020712130106.A4048@neutrino.particles.org \
--to=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).