linux-c-programming.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ashtrax <xlp@emtel.net.co>
To: linux-c-programming@vger.kernel.org
Subject: A exploitable C program
Date: Thu, 11 Jul 2002 23:33:56 -0500	[thread overview]
Message-ID: <20020711233356.F343@nietzsche.metrotel.net.co> (raw)

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?

bye.
p.s. Why I cant 'get' with majordomo all the list archives? (get linux-c-programming <date>)




             reply	other threads:[~2002-07-12  4:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-12  4:33 ashtrax [this message]
2002-07-12 10:01 ` A exploitable C program Elias Athanasopoulos
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=20020711233356.F343@nietzsche.metrotel.net.co \
    --to=xlp@emtel.net.co \
    --cc=linux-c-programming@vger.kernel.org \
    /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).