From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,b4846bde7eaac045 X-Google-Attributes: gid103376,public From: Stefan Skoglund Subject: Re: gnat on linux (strange problems and behaviour) Date: 1999/08/21 Message-ID: <37BEA492.413D9707@ebox.tninet.se>#1/1 X-Deja-AN: 515474837 Content-Transfer-Encoding: 7bit References: <37B0B4CB.E15ECC72@billybob.demon.co.uk> <37B3D56F.AB39C948@billybob.demon.co.uk> <87pv0sm30x.fsf@antinea.enst.fr> Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@algo.net X-Trace: zingo.tninet.se 935240609 8904 195.100.241.100 (21 Aug 1999 13:03:29 GMT) Organization: Telenordia Mime-Version: 1.0 NNTP-Posting-Date: 21 Aug 1999 13:03:29 GMT Newsgroups: comp.lang.ada Date: 1999-08-21T13:03:29+00:00 List-Id: Samuel Tardieu wrote: > Well, it is a safe choice not to have "." in your PATH as far as > security is concerned: you can be in whatever directory you want, you > will not take the risk of calling commands outside of the safe PATH > you defined unless you explicitely provide the "./". > > Of course, if you are not using a multiuser system, this is overkill. > a software package should never require . in the PATH. This is most definitely broken !!! Consider the existence of trojans.