calife(1) [debian man page]

CALIFE(1)						    BSD General Commands Manual 						 CALIFE(1)

NAME

     calife -- becomes root (or another user) legally.

SYNOPSIS

     calife [-] [login]

	    or

     ... [-] [login] for some sites (check with your administrator).

DESCRIPTION

     Calife requests user's own password for becoming login (or root, if no login is provided), and switches to that user and group ID after veri-
     fying proper rights to do so.  A shell is then executed.  If calife is executed by root, no password is requested and a shell with the appro-
     priate user ID is executed.

     The invoked shell is the user's own except when a shell is specified in the configuration file calife.auth.

     If ``-'' is specified on the command line, user's profile files are read as if it was a login shell.

     This is not the traditional behavior of su.

     Only users specified in calife.auth can use calife to become another one with this method.

     You can specify in the calife.auth file the list of logins allowed for users when using calife.  See calife.auth(5) for more details.

     calife.auth is installed as /etc/calife.auth.

FILES

     /etc/calife.auth  List of users authorized to use calife and the users they can become.
     /etc/calife.out   This script is executed just after getting out of calife.

SEE ALSO

     su(1), calife.auth(5), group(5), environ(7)

ENVIRONMENT

     The original environment is kept. This is not a security problem as you have to be yourself at login (i.e. it does not have the same security
     implications as in su(1) ).

     Environment variables used by calife:

     HOME  Default home directory of real user ID.

     PATH  Default search path of real user ID unless modified as specified above.

     TERM  Provides terminal type which may be retained for the substituted user ID.

     USER  The user ID is always the effective ID (the target user ID) after an su unless the user ID is 0 (root).

BUGS

     The MD5-based crypt(3) function is slower and probably stronger than the DES-based one but it is usable only among FreeBSD 2.0+ systems.

HISTORY

     A calife command appeared in DG/UX, written for Antenne 2 in 1991. It has evolved considerably since this period with more OS support, user
     lists handling and improved logging.

     PAM support was introduced in 2005 to port it to MacOS X variants (Panther and up).

AUTHOR

     Ollivier Robert <roberto@keltia.freenix.fr>

BSD
								September 25, 1994							       BSD

chsh(1) 						      General Commands Manual							   chsh(1)

NAME

       chsh - change default login shell

SYNOPSIS

       login-name [shell]

       login-name [shell]

       login-name [shell]

       login-name [shell]

DESCRIPTION

       The command changes the login-shell for a user's login name in the repository (see passwd(1)).

       The  DCE  repository is only available if Integrated Login has been configured; see auth.adm(1M).  If Integrated Login has been configured,
       other considerations apply.  A user with appropriate DCE privileges is capable of modifying a user's shell;  this  is  not  dependent  upon
       superuser privileges.

       If the repository is not specified (as in [login-name]), the login shell is changed in the file only.

       Run after running to make sure the information was processed correctly.

   Notes
       The  command  is  a hard link to the command. When is executed, actually the command gets executed with appropriate arguments to change the
       user login shell in the repository specified in command line. If no repository is specified, the login shell is changed in the file.

   Arguments
	      login-name  A login name of a user.

	      shell	  The absolute path name of a shell.  If the file exists, the new login shell must be listed in that file.  Otherwise, you
			  can specify one of the standard shells listed in the getusershell(3C) manual entry.  If shell is omitted, it defaults to
			  the POSIX shell,

   Options
       The following option is recognized:

	      Specify the repository to which the operation is to be applied.
		     Supported repositories include and

   Security Restrictions
       You must have appropriate privileges to use the optional login-name argument to change another user's login shell.

NETWORKING FEATURES

   NFS
       File can be implemented as a Network Information Service (NIS) database.

EXAMPLES

       To change the login shell for user to the default:

       To change the login shell for user to the C shell:

       To change the login shell for user to the Korn shell in the DCE registry:

WARNINGS

       If two or more users try to write the file at the same time, a passwd locking mechanism was devised.  If this locking  fails  after  subse-
       quent retrying, terminates.

AUTHOR

       was developed by HP and the University of California, Berkeley.

FILES

SEE ALSO

       chfn(1), csh(1), ksh(1), passwd(1), sh(1), sh-posix(1), getusershell(3C), pam(3), passwd(4), shells(4).

																	   chsh(1)