Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <20040511180755.29751.qmail@web61006.mail.yahoo.com> Date: Tue, 11 May 2004 11:07:55 -0700 (PDT) From: Rocket Boy Subject: Fwd: RE: Problems with Indirect Interpretation (#!/bin/csh, #!/bin/tcsh, #!/bin/perl, etc...) To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="0-1048901606-1084298875=:28611" --0-1048901606-1084298875=:28611 Content-Type: text/plain; charset=us-ascii Content-Id: Content-Disposition: inline Note: forwarded message attached. __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover --0-1048901606-1084298875=:28611 Content-Type: message/rfc822 Received: from [65.202.226.14] by web61004.mail.yahoo.com via HTTP; Tue, 11 May 2004 11:07:07 PDT Date: Tue, 11 May 2004 11:07:07 -0700 (PDT) From: Rocket Boy Subject: RE: Problems with Indirect Interpretation (#!/bin/csh, #!/bin/tcsh, #!/bin/perl, etc...) To: dk AT artimi DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Length: 893 I suppose putting the '.' at the end of $PATH would be a compromise since the directories should be scanned in thier order in $PATH right? > -----Original Message----- > From: cygwin-owner On Behalf Of Rocket Boy > Sent: 11 May 2004 18:44 > This indeed appears to be the problem. I figured it > something that basic. Though I searched the web for > days I couldn't find the same symptoms discussed > elsewhere. > > The FAQ says that it is not recommended to add . to > $PATH. Anyone, know a compelling reason not to? It's a security measure for the medium-to-fairly paranoid. :-O Basically it protects you against the possibility that some virus/trojan might e.g. dump a copy of itself under the filename 'ls' into your home dir or somewhere. If you had '.' in the $PATH, as soon as you log in and run ls, you'd end up executing the trojanned version; if you don't have . in your $PATH, you know for sure that you'll always be executing the version in /bin, which presumably (on a well secured system) will be read-only to everyone except root, and hence less likely to have been trojanned/infected. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover --0-1048901606-1084298875=:28611 Content-Type: text/plain; charset=us-ascii -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/ --0-1048901606-1084298875=:28611--