|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: Shell Q
From: Mike Tatroe (MTatroe
BOSCOMM.NET)Date: Mon Aug 14 2000 - 09:19:03 CDT
- Next message: Patrik Sternudd: "Re: Shell Q"
- Previous message: Martin Hepworth: "Re: password history for Solaris"
- Maybe in reply to: C.M. Wong: "Shell Q"
- Next in thread: Patrik Sternudd: "Re: Shell Q"
- Maybe reply: Mike Tatroe: "Re: Shell Q"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
IMHO, it's not normal to replace root's shell because you shouldn't
be doing things as root so often that you can't just switch to $SHELL after
you become root. Or use sudo.
-- Mike Tatroe Phone: 781-994-3217 UNIX Administrator Fax: (781) 994-8255 Boston Communications Group Email: mtatroeboscomm.net
> -----Original Message----- > From: C.M. Wong [mailto:wongcm
EP.COM.MY] > Sent: Sunday, August 13, 2000 11:37 PM > To: FOCUS-SUN
SECURITYFOCUS.COM > Subject: Shell Q > > > Hi All, > > Forgive my ignorance, but what is the diff between /sbin/sh > and /bin/sh as > both are different in sizes? I was thinking of using another sh (tcsh > actually) as a replacement for users and root alike. Security > wise, is it > viable if I just replace root's sh at the passwd file? I have > read somewhere > that it's not advisable to replace root's shell since if the > machine crashes > etc, the replacement shell might not work and there is no > where we can get > back in. Probably a better place would be profile, but how do you guys > normally do it? TIA. > > Rgrds, > Wong. >
- Next message: Patrik Sternudd: "Re: Shell Q"
- Previous message: Martin Hepworth: "Re: password history for Solaris"
- Maybe in reply to: C.M. Wong: "Shell Q"
- Next in thread: Patrik Sternudd: "Re: Shell Q"
- Maybe reply: Mike Tatroe: "Re: Shell Q"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]