The user is then prompted for a password, where appropriate. Echoing is disabled to prevent revealing the password. Only a small number of password failures are permitted before
If password aging has been enabled for your account, you may be prompted for a new password before proceeding. You will be forced to provide your old password and the new password before continuing. Please refer to
After a successful login, you will be informed of any system messages and the presence of mail. You may turn off the printing of the system message file,
in your login directory. The mail message will be one of "\fIYou have new mail.\fR", "\fIYou have mail.\fR", or "\fINo Mail.\fR" according to the condition of your mailbox.
are set according to the appropriate fields in the password entry. Ulimit, umask and nice values may also be set according to entries in the GECOS field.
An initialization script for your command interpreter may also be executed. Please see the appropriate manual section for more information on this function.
.PP
A subsystem login is indicated by the presence of a "*" as the first character of the login shell. The given home directory will be used as the root of a new file system which the user is actually logged into.
program is NOT responsible for removing users from the utmp file. It is the responsibility of
\fBgetty\fR(8)
and
\fBinit\fR(8)
to clean up apparent ownership of a terminal session. If you use
\fBlogin\fR
from the shell prompt without
\fBexec\fR, the user you use will continue to appear to be logged in even after you log out of the "subsession".
.PP
As any program,
\fBlogin\fR
appearance could be faked. If non\-trusted users have a physical access to the machine, an attacker could use this to obtain the password of the next person sitting in front of the machine. Under Linux, the SAK mecanism can be used by users to initiate of a trusted path and prevent this kind of attack.