Date: Mon, 7 Jan 2008 17:04:39 +0000 From: Mike Bristow <mike@urgle.com> To: Erik Osterholm <freebsd-lists-erik@erikosterholm.org>, Steve Franks <stevefranks@ieee.org>, User Questions <freebsd-questions@freebsd.org> Subject: Re: home dir executable (!/bin/sh, chmod+x) shell scripts won't run without "sh <script>" Message-ID: <20080107170439.GA39088@wafer.urgle.com> In-Reply-To: <20080107165047.GA12249@aleph.cepheid.org> References: <539c60b90801070752l3d0e571cq8f7b1b519e1e808c@mail.gmail.com> <5D884B59-3CEF-4F81-B35D-4E54F5D6301C@gmail.com> <539c60b90801070813h537451e8q9264897bc9404260@mail.gmail.com> <20080107165047.GA12249@aleph.cepheid.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 07, 2008 at 10:50:47AM -0600, Erik Osterholm wrote: > The '.' notation for the current working directory enables you to add > the current directory you happen to be in as part of your path (thus > making it searched when executing a command), however this has serious > security implciations, so if you think that it's something you really > want to do, you'll have to find out from someone else how to do it. OTOH, having ~/bin in the path has no security implications at all - assuming your scripts are OK, of course. -- Shenanigans! Shenanigans! Best of 3! -- Flash
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080107170439.GA39088>