|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: PATH variable in zip-slackware 2.0.35
kay (kay
PHREEDOM.ORG)Sun, 3 Jan 1999 04:04:55 +0200
- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: The Forlorn: "l0phtcrack 2.5 released"
- Previous message: Gene Spafford: "Vulnerability database workshop"
- In reply to: Karl Stevens: "Re: PATH variable in zip-slackware 2.0.35"
- Next in thread: Karl Stevens: "Re: PATH variable in zip-slackware 2.0.35"
Sorry for continuing this really unnecessary thread... On Mon, 4 Jan 1999, Karl Stevens wrote: > Actually, this is the default path for USERS, not for root (Slackware 3.4, > 3.5, 3.6) The default path for root is > /usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin This is not true. This is output from a clean Slackware 3.6: bash# echo $PATH /usr/local/qt/bin:/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin: \ /usr/bin:/usr/X11R6/bin:/usr/andrew/bin:/usr/openwin/bin:/usr/games:. A quick look through the init scripts reveals no distinguish whether they run as root, other privileged uid, or something. > The problem specified in the previous posts is only present in the zipslack > distribution. This is not true as well. If it was only present in zipslack noone would care. I personally wouldn't run a secure server on zipslack/umsdos. -- kay // kayphreedom.org
- Next message: The Forlorn: "l0phtcrack 2.5 released"
- Previous message: Gene Spafford: "Vulnerability database workshop"
- In reply to: Karl Stevens: "Re: PATH variable in zip-slackware 2.0.35"
- Next in thread: Karl Stevens: "Re: PATH variable in zip-slackware 2.0.35"