From: I phantom <left1st@hotmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan 9 buffer overflow exploit explained in Phrack Volume 0x0b, Issue 0x3e, Phile #0x09 of 0x0f
Date: Mon, 22 Sep 2003 09:01:14 +0000 [thread overview]
Message-ID: <ebb45842.0309210710.4840223b@posting.google.com> (raw)
In-Reply-To: <20030920153514.GA25835@folly>
markus@openbsd.org (Markus Friedl) wrote in message news:<20030920153514.GA25835@folly>...
> AFAIK, phrack 62 is fake, a hoax.
>
> On Sat, Sep 20, 2003 at 02:55:37AM -0400, Russ Cox wrote:
> > He exploited a buffer overrun in his own program.
> > It would be more interesting if he exploited a buffer
> > overrun in some system program, preferably one that
> > listens to the network. But then, he'd still be none.
> >
> > Russ
If you had actually bothered to read the introduction you would know
that
Phrack 62 is not fake but merely a change of direction. But actually
reading..... (a zine, documentation, literature, openssh code) is 2
much to expect from anyone@openbsd.org. To everyone else on this list,
I apologize.
next prev parent reply other threads:[~2003-09-22 9:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-20 6:49 Vester Thacker
2003-09-20 6:55 ` Russ Cox
2003-09-20 15:35 ` Markus Friedl
2003-09-22 9:01 ` I phantom [this message]
2003-09-20 17:14 ` Dan Cross
2003-09-20 17:22 ` Russ Cox
2003-09-20 17:49 ` Dan Cross
2003-09-20 17:53 ` William K. Josephson
2003-09-20 17:57 ` Dan Cross
2003-09-20 18:01 ` Russ Cox
2003-09-20 18:37 ` Dan Cross
2003-09-20 18:39 ` Russ Cox
2003-09-20 18:44 ` [9fans] mpm again Russ Cox
2003-09-20 19:07 ` [9fans] Plan 9 buffer overflow exploit explained in Phrack Volume 0x0b, Issue 0x3e, Phile #0x09 of 0x0f William K. Josephson
2003-09-20 20:12 ` David Presotto
2003-09-20 20:10 ` David Presotto
2003-09-20 8:07 Charles Forsyth
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=ebb45842.0309210710.4840223b@posting.google.com \
--to=left1st@hotmail.com \
--cc=9fans@cse.psu.edu \
/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).