🚀 go-pugleaf

> Subject: 4.3 /bin/passwd does not deal with /etc/shells properly
> Repeat-By:
>	Run passwd to request a new shell. Ask for a shell that is
>	before your old shell in the list in /etc/shells.

> Subject: 4.3 vipw does not allow root to have a shell in /etc/shells
> Repeat-By:
>	Edit the password file with vipw, and try to change root's
>	shell to a shell listed in /etc/shells, but not /bin/sh or
>	/bin/csh, (e.g., /bin/ksh). Watch vipw complain about mangling
>	the password file.

Could someone explain what this /etc/shells silliness is all about?
Why joe user can't change his shell to whatever he pleases??  I see no
reason to restrict users in their choice of shells - in fact, this is
one of the things usually quoted as a great strength of UNIX.  Or is
this an attempt to protect people from themselves?  Why assume they
*need* protection from themselves?  If I wanted to run another shell on
a system with this sort of stupidity I'd just specify /bin/sh and have
a one-line .profile
exec /.../myshell "$@"
or use /bin/csh and have a similar .cshrc -- so you really don't buy
anything.  Just user aggravation and extra trash to maintain.

By the way, I would argue that the second "bug" I quoted above is not a
bug.  One of the uses of root is to fix things when they break.
Suppose ksh is broken?  Then you can't log in as root, you have to boot
single-user (involving bringing the system down).

					der Mouse

USA: {ihnp4,decvax,akgua,utzoo,etc}!utcsri!mcgill-vision!mouse
     think!mosart!mcgill-vision!mouse
Europe: mcvax!decvax!utcsri!mcgill-vision!mouse
ARPAnet: think!mosart!mcgill-vision!mouse@harvard.harvard.edu

[USA NSA food: terrorist, cryptography, DES, drugs, CIA, secret, decode]