Date: Mon, 7 Jan 2008 14:03:01 -0500 From: Bill Moran <wmoran@potentialtech.com> To: Mike Jeays <mike.jeays@rogers.com> Cc: freebsd-questions@freebsd.org Subject: Re: home dir executable (!/bin/sh, chmod+x) shell scripts won't run without "sh <script>" Message-ID: <20080107140301.0cf14870.wmoran@potentialtech.com> In-Reply-To: <200801071321.41458.mike.jeays@rogers.com> References: <539c60b90801070752l3d0e571cq8f7b1b519e1e808c@mail.gmail.com> <20080107165047.GA12249@aleph.cepheid.org> <20080107170439.GA39088@wafer.urgle.com> <200801071321.41458.mike.jeays@rogers.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In response to Mike Jeays <mike.jeays@rogers.com>: > On January 7, 2008 12:04:39 pm Mike Bristow wrote: > > 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. > > I don't see anything especially bad about putting "." as the last item in the > PATH on a personal desktop machine. It is convenient, IMHO worth the risk. > If my desktop gets hacked, I have worse problems to worry about than this. Personally, I recommend creating a ~/bin directory and adding that to your search path. You're much less likely to accidentally download a trojan script into ~/bin than you are to ~, and it serves to keep your stuff more organized. -- Bill Moran http://www.potentialtech.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080107140301.0cf14870.wmoran>