Date: Tue, 29 Jun 2004 09:39:03 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: clayton rollins <crollins666@hotmail.com> Cc: freebsd@stateautomation.com Subject: Re: [from newbies] RE: Command path Message-ID: <20040629083903.GB4372@happy-idiot-talk.infracaninophile.co.uk> In-Reply-To: <Sea1-F67sWHOg3V5EUH0005cc79@hotmail.com> References: <Sea1-F67sWHOg3V5EUH0005cc79@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--2B/JsCI69OhZNC5r
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Jun 29, 2004 at 08:11:12AM +0000, clayton rollins wrote:
=20
> In sh, you could do:
> 'PATH=3D.:$PATH'
>=20
> in (t)csh, you could do:
> 'setenv PATH .:$PATH'
Generally you should be exceedingly careful about putting '.' onto
your $PATH. You should certainly not put '.' into root's $PATH, and
preferably not at the beginning of the $PATH for ordinary users.
ie. If you must put '.' in your path, do it like this:
PATH=3D${PATH}:. ; export PATH
or
setenv PATH ${PATH}:.
The danger with having '.' on a the $PATH is that you can trick
(deliberately or not) people into running trojan programs. Bad for
ordinary users, disasterous for root.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
--2B/JsCI69OhZNC5r
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
iD8DBQFA4SqniD657aJF7eIRAlYxAKCNLf6+FT6WvJ/eI6C7g7eTJKF4bwCeP/bi
TlCTUoOKOf3WHxgkd+g7VQM=
=z0Tj
-----END PGP SIGNATURE-----
--2B/JsCI69OhZNC5r--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040629083903.GB4372>