From: "Russ Cox" <rsc@plan9.bell-labs.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: Sat, 20 Sep 2003 14:01:46 -0400 [thread overview]
Message-ID: <34b8becbb30946e8fd4397ce2952e9e6@plan9.bell-labs.com> (raw)
In-Reply-To: <200309201757.h8KHv3j24962@augusta.math.psu.edu>
> Funny you should mention that... it's exactly what I was thinking of
> in terms of NOT eliminating compatibility. I suppose the obvious answer
> would be to just recompile it with g++ or otherwise release it (mpm).
it's not just mpm. i can run almost every binary that has
ever been compiled on plan 9 (for my current architecture).
that's useful occasionally, and it's 100 lines of code to implement.
if you don't want to carry it around, you could chop it out
of your copy, but there are much bigger things you could drop
instead.
next prev parent reply other threads:[~2003-09-20 18: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
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 [this message]
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=34b8becbb30946e8fd4397ce2952e9e6@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).