OSEC

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: Anders Jennerberg (ajennerbMSI-UK.COM)
Date: Mon Aug 14 2000 - 09:54:32 CDT

First the difference between the different sh shells:

/sbin/sh is statically linked (does not need any libraries) and it is on the
root partition.

/bin/sh is dynamically linked (needs libraries) and /bin is a link to
/usr/bin
so it is on the /usr partition.

This means that as long as you have /sbin/sh as root shell, you will always
be able
to log in if the root partition works. Gives better chance of repair...

For your problem, make an alias sut='/usr/bin/su root -c /usr/bin/tcsh'. The
times
you log in as root, just type the shellname (4 letters). If it's not in your
path, modify
/etc/default/su (uncomment/modify the SUPATH variable).

/Anders Jennerbeg
Systems Administrator
MSI Ltd

-----Original Message-----
From: C.M. Wong [mailto:wongcmEP.COM.MY]
Sent: 14 August 2000 04:37
To: FOCUS-SUNsecurityfocus.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.