The following are optional arguments which are likely to be understood by any module. Arguments (including these) are in general optional.
debug
Use the syslog(3)
call to log debugging information to the system
log files.
no_warn
Instruct module to not give warning messages to the application.
use_first_pass
The module should not prompt the user for a password. Instead, it
should obtain the previously typed password (from the preceding
auth
module), and use that. If that doesn't work, then the user
will not be authenticated. (This option is intended for auth
and password
modules only).
try_first_pass
The module should attempt authentication with the previously typed
password (from the preceding auth
module). If that doesn't work,
then the user is prompted for a password. (This option is intended for
auth
modules only).
use_mapped_pass
This argument is not currently supported by any of the modules in the Linux-PAM distribution because of possible consequences associated with U.S. encryption exporting restrictions. Within the U.S., module developers are, of course, free to implement it (as are developers in other countries). For compatibility reasons we describe its use as suggested in the DCE-RFC 86.0, see section bibliography for a pointer to this document.
The use_mapped_pass
argument instructs the module to take the
clear text authentication token entered by a previous module (that
requests such a token) and use it to generate an encryption/decryption
key with which to safely store/retrieve the authentication token
required for this module. In this way the user can enter a single
authentication token and be quietly authenticated by a number of
stacked modules. Obviously a convenient feature that necessarily
requires some reliably strong encryption to make it secure.
This argument is intended for the auth
and password
module
types only.