login(1)

NAME | SYNOPSIS | DESCRIPTION | SECURITY | OPTIONS | EXIT STATUS | FILES | ATTRIBUTES | SUMMARY OF TRUSTED SOLARIS CHANGES | SEE ALSO | DIAGNOSTICS | WARNINGS

NAME

login- Sign on to the system

SYNOPSIS

login [-p] [-d device] [-h hostname| [terminal]| -r hostname| [-T]| [-U uid]] [name[environ...]]

DESCRIPTION

The login command is used at the beginning of each terminal session to identify oneself to the system. login is invoked by the system when a connection is first established, after the previous user has terminated the login shell by issuing the exit command.

If login is invoked as a command, it must replace the initial command interpreter. To invoke login in this fashion, type:

---

exec login

---

from the initial shell. The C shell and Korn shell have their own builtins of login. See ksh(1) and csh(1) for descriptions of login builtins and usage.

login asks for your user name if it is not supplied as an argument, and your password, if appropriate. Where possible, echoing is turned off while you type your password, so it will not appear on the written record of the session.

If you make any mistake in the login procedure, the message:

---

Login incorrect

---

is printed and a new login prompt will appear. If you make five incorrect login attempts, all five may be logged in /var/adm/loginlog, if it exists. The TTY line will be dropped.

If password aging is turned on and the password has "aged" [see passwd(1) for more information], login is denied with a message to use the desktop to log in and change the password.

After a successful login, accounting files are updated. Device owner, group, and permissions are set according to the contents of the /etc/logindevperm file, and the time you last logged in is printed (see logindevperm(4)).

Except for remote logins, login asks you to select the sensitivity label (SL) at which you will operate for this terminal session. You must enter a label that you are authorized to use and that is valid for the device.

The user-ID, group-ID, supplementary group list, and working directory are initialized, and the command interpreter (usually ksh) is started.

The basic environment is initialized to:

---

HOME=your-login-directory
LOGNAME=your-login-name
PATH=/usr/bin:
SHELL=last-field-of-passwd-entry
MAIL=/var/mail/
TZ=timezone-specification

---

For Bourne shell and Korn shell logins, the shell executes /etc/profile and $HOME/.profile, if it exists. For C shell logins, the shell executes /etc/.login, $HOME/.cshrc, and $HOME/.login. The default /etc/profile and /etc/.login files check quotas (see quota(1M)), print /etc/motd, and check for mail. None of the messages are printed if the file $HOME/.hushlogin exists. The name of the command interpreter is set to - (dash), followed by the last component of the interpreter's path name, for example, -sh.

If the login-shell field in the password file (see passwd(4)) is empty, then the default command interpreter, /usr/bin/sh, is used. If this field is * (asterisk), then the named directory becomes the root directory. At that point, login is re-executed at the new level, which must have its own root structure.

The environment may be expanded or modified by supplying additional arguments to login, either at execution time or when login requests your login name. The arguments may take either the form xxx or xxx=yyy. Arguments without an = (equal sign) are placed in the environment as:

---

Ln=xxx

---

where n is a number starting at 0 and is incremented each time a new variable name is required. Variables containing an = (equal sign) are placed in the environment without modification. If they already appear in the environment, then they replace the older values.

There are two exceptions: The variables PATH and SHELL cannot be changed. This prevents people logged into restricted shell environments from spawning secondary shells that are not restricted. login understands simple single-character quoting conventions. Typing a \ (backslash) in front of a character quotes it and allows the inclusion of such characters as spaces and tabs.

Alternatively, you can pass the current environment by supplying the -p flag to login. This flag indicates that all currently defined environment variables should be passed, if possible, to the new environment. This option does not bypass any environment variable restrictions mentioned above. Environment variables specified on the login line take precedence, if a variable is passed by both methods.

To enable remote logins by administrative users (that is, administrative roles), edit the /etc/default/login file by inserting a pound sign (#) before the CONSOLE=/dev/console entry. See FILES.

SECURITY

login uses pam(3) for authentication, account management, session management, and password management. The PAM configuration policy, listed through /etc/pam.conf, specifies the modules to be used for login. Here is a partial pam.conf file with entries for the login command using the UNIX authentication, account management, session management, and password management module.

---

login auth required /usr/lib/security/pam_unix.so.1 login account required /usr/lib/security/pam_unix.so.1 login session required /usr/lib/security/pam_unix.so.1 login password required /usr/lib/security/pam_unix.so.1

---

If there are no entries for the login service, then the entries for the "other" service will be used. If multiple authentication modules are listed, then the user may be prompted for multiple passwords.

When login is invoked through rlogind or telnetd, the service name used by PAM is rlogin or telnet respectively.

OPTIONS

The following options are supported:

-d device

login accepts a device option, device. device is taken as the path name of the TTY port on which login is to operate. The use of the device option can be expected to improve login performance because login will not need to call ttyname(3C).

-h hostname [ terminal ]

Used by in.telnetd(1M) to pass information about the remote host and terminal type.

-p

Used to pass environment variables to the login shell.

-r hostname

Used by in.rlogind(1M) to pass information about the remote host.

-T

in.rlogind(1M) uses this option to indicate that the trusted path process attribute is set on the remote host for the process invoking rlogin.

-U uid

in.rlogind(1M) uses this option to pass information about the UID of the invoker of rlogin. If uid and name are both passed by in.rlogind(1M), the UID of name must match the uid value or login is denied.

EXIT STATUS

Upon success, login returns 0. Upon failure, login returns a nonzero value.

FILES

$HOME/.cshrc

initial commands for each csh

$HOME/.hushlogin

suppresses login messages

$HOME/.login

user's login commands for csh

$HOME/.profile

user's login commands for sh and ksh

$HOME/.rhosts

private list of trusted hostname/username combinations

/etc/.login

system-wide csh login commands

/etc/logindevperm

login-based device permissions

/etc/motd

message-of-the-day

/etc/nologin

message displayed to users attempting to login during machine shutdown

/etc/passwd

password file

/etc/profile

system-wide sh and ksh login commands

/etc/shadow

list of users' encrypted passwords

/usr/bin/sh

user's default command interpreter

/var/adm/lastlog

time of last login

/var/adm/loginlog

record of failed login attempts

/var/adm/utmp

accounting

/var/adm/wtmp

accounting

/var/mail/your-name

mailbox for user your-name

/etc/default/login

Default value can be set for the following flags in /etc/default/login. For example: TIMEZONE=EST5EDT

TIMEZONE

Sets the TZ environment variable of the shell (see environ(5)).

HZ

Sets the HZ environment variable of the shell.

ULIMIT

Sets the file size limit for the login. Units are disk blocks. Default is zero (no limit).

CONSOLE

If this flag is set, administrative users can log in only on that device. This setting will not prevent execution of remote commands with rsh(1). Comment out this line to allow login by administrative users.

PASSREQ

Determines if login requires a non-null password.

ALTSHELL

Determines if login should set the SHELL environment variable.

PATH

Sets the initial shell PATH variable.

SUPATH

Sets the initial shell PATH variable for root.

TIMEOUT

Sets the number of seconds (between 0 and 900) to wait before abandoning a login session.

UMASK

Sets the initial shell file creation mode mask. See umask(1).

SYSLOG

Determines whether the syslog(3) LOG_AUTH facility should be used to log all root logins at level LOG_NOTICE and multiple failed login attempts atLOG_CRIT.

SLEEPTIME

If present, sets the number of seconds to wait before login failure is printed to the screen and another login attempt is allowed. Default is 4 seconds. Minimum is 0 seconds. Maximum is 5 seconds.

RETRIES

Sets the number of retries for logging in (see pam(3)). The default is 5.

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	SUNWcsu

SUMMARY OF TRUSTED SOLARIS CHANGES

You are prompted to select the label for your session at login time (except for remote login). Restrictions on labels and UIDs apply. The DESCRIPTION section explains these restrictions. The Trusted Solaris environment adds two options: -T and -U. (See OPTIONS.)

SEE ALSO

Trusted Solaris 7 Reference Manual

passwd(1), in.rlogind(1M)

SunOS 5.7 Reference Manual

csh(1), exit(1), ksh(1), mail(1), mailx(1), newgrp(1), rlogin(1), rsh(1), sh(1), shell_builtins(1), telnet(1), umask(1), in.telnetd(1M), logins(1M), su(1M), syslogd(1M), pam(3), rcmd( 3N), syslog(3), ttyname(3C), hosts.equiv(4), logindevperm(4), loginlog(4), nologin(4), pam.conf(4), passwd(4), profile(4), shadow(4), utmp(4), wtmp(4), attributes(5), environ(5), pam_unix( 5), termio(7I)

DIAGNOSTICS

Login incorrect

The user name or the password cannot be matched.

Not on system console

Administrative user login denied. Check the CONSOLE setting in /etc/default/login.

No directory! Logging in with home=/

The user's home directory named in the passwd(4) database cannot be found or has the wrong permissions. Contact your system administrator.

No shell

Cannot execute the shell named in the passwd(4) database. Contact your system administrator.

NO LOGINS: System going down in N minutes

The machine is in the process of being shut down and logins have been disabled.

WARNINGS

Users with a UID greater than 76695844 are not subject to password aging, and the system does not record their last login time.

If you use the CONSOLE setting to disable administrative user logins, make sure that remote command execution by administrative users is also disabled. See rsh(1), rcmd(3N), and hosts.equiv(4) for further details.

Trusted Solaris 7  Last Revised 18 Mar 1998

NAME | SYNOPSIS | DESCRIPTION | SECURITY | OPTIONS | EXIT STATUS | FILES | ATTRIBUTES | SUMMARY OF TRUSTED SOLARIS CHANGES | SEE ALSO | DIAGNOSTICS | WARNINGS