Date: Wed, 11 Oct 2000 16:15:31 +0200 From: Peter van Dijk <petervd@vuurwerk.nl> To: freebsd-security@FreeBSD.ORG Subject: Re: ncurses buffer overflows (fwd) Message-ID: <20001011161531.C52149@vuurwerk.nl> In-Reply-To: <20001011080628.F387D1F22@static.unixfreak.org>; from dima@unixfreak.org on Wed, Oct 11, 2000 at 01:06:28AM -0700 References: <20001010214332.G25121@149.211.6.64.reflexcom.com> <20001011080628.F387D1F22@static.unixfreak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Oct 11, 2000 at 01:06:28AM -0700, Dima Dorfman wrote: [snip] > "Me too." It was my impression that the whole '#!/path/to/shell' > thing started when people expressed a desire to use csh for their > scripts, so someone hacked execve in their kernel to look for '#' as > the first byte in the file, and if it's there, execute whatever > command follows. Since not all kernels had this hack, the script > would still get executed with sh on some systems, so it was decided > that the sh comment character be used to keep the old hosts happy. It requires #!, not just #. Greetz, Peter. -- [ircoper] petervd@vuurwerk.nl - Peter van Dijk / Hardbeat [student] Undernet:#groningen/wallops | IRCnet:/#alliance [developer] EFnet:#qmail _____________ [disbeliever - the world is backwards] (__VuurWerk__(--*- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001011161531.C52149>