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 From: "Dave Korn" To: Subject: RE: Problems with Indirect Interpretation (#!/bin/csh, #!/bin/tcsh, #!/bin/perl, etc...) Date: Tue, 11 May 2004 18:50:59 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: <20040511174418.42681.qmail@web61002.mail.yahoo.com> Message-ID: X-OriginalArrivalTime: 11 May 2004 17:50:59.0647 (UTC) FILETIME=[84CB3CF0:01C43780] > -----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/