[10282] in bugtraq
Re: Buffer overflow in BASH
daemon@ATHENA.MIT.EDU (Adam D. McKenna)
Tue Apr 20 14:10:34 1999
Date: Mon, 19 Apr 1999 14:59:06 -0400
Reply-To: "Adam D. McKenna" <adam@FLOUNDER.NET>
From: "Adam D. McKenna" <adam@FLOUNDER.NET>
X-To: Wojciech Purczynski <wojtek@ROUTER.ELZAB.COM.PL>
To: BUGTRAQ@NETSPACE.ORG
I really don't see the point of people posting bash bugs here. Especially
not bugs in old versions. There are a lot of bash bugs, you can't gain any
extra priveleges by exploiting them though.
--Adam
from bash(1):
BUG REPORTS
If you find a bug in bash, you should report it. But
first, you should make sure that it really is a bug, and
that it appears in the latest version of bash that you
have.
Once you have determined that a bug actually exists, use
the bashbug command to submit a bug report. If you have a
fix, you are encouraged to mail that as well! Suggestions
and `philosophical' bug reports may be mailed to bug-
bash@prep.ai.MIT.Edu or posted to the Usenet newsgroup
gnu.bash.bug.
ALL bug reports should include:
The version number of bash
The hardware and operating system
The compiler used to compile
A description of the bug behaviour
A short script or `recipe' which exercises the bug
bashbug inserts the first three items automatically into
the template it provides for filing a bug report.
Comments and bug reports concerning this manual page
should be directed to chet@ins.CWRU.Edu.
