debug
Turns on debugging via syslog(3).
audit
A little more extreme than debug.
quiet
Turns off informational messages namely messages about session open and close via syslog(3).
nullok
The default action of this module is to not permit the user access to a service if their official
password is blank. The nullok argument overrides this default.
nullresetok
Allow users to authenticate with blank password if password reset is enforced even if nullok is not
set. If password reset is not required and nullok is not set the authentication with blank password
will be denied.
try_first_pass
Before prompting the user for their password, the module first tries the previous stacked module's
password in case that satisfies this module as well.
use_first_pass
The argument use_first_pass forces the module to use a previous stacked modules password and will
never prompt the user - if no password is available or the password is not appropriate, the user will
be denied access.
nodelay
This argument can be used to discourage the authentication component from requesting a delay should
the authentication as a whole fail. The default action is for the module to request a
delay-on-failure of the order of two seconds.
use_authtok
When password changing enforce the module to set the new password to the one provided by a previously
stacked password module (this is used in the example of the stacking of the pam_passwdqc module
documented below).
authtok_type=type
This argument can be used to modify the password prompt when changing passwords to include the type
of the password. Empty by default.
nis
NIS RPC is used for setting new passwords.
remember=n
The last n passwords for each user are saved in /etc/security/opasswd in order to force password
change history and keep the user from alternating between the same password too frequently. The MD5
password hash algorithm is used for storing the old passwords. Instead of this option the
pam_pwhistory module should be used.
shadow
Try to maintain a shadow based system.
md5
When a user changes their password next, encrypt it with the MD5 algorithm.
bigcrypt
When a user changes their password next, encrypt it with the DEC C2 algorithm.
sha256
When a user changes their password next, encrypt it with the SHA256 algorithm. The SHA256 algorithm
must be supported by the crypt(3) function.
sha512
When a user changes their password next, encrypt it with the SHA512 algorithm. The SHA512 algorithm
must be supported by the crypt(3) function.
blowfish
When a user changes their password next, encrypt it with the blowfish algorithm. The blowfish
algorithm must be supported by the crypt(3) function.
gost_yescrypt
When a user changes their password next, encrypt it with the gost-yescrypt algorithm. The
gost-yescrypt algorithm must be supported by the crypt(3) function.
yescrypt
When a user changes their password next, encrypt it with the yescrypt algorithm. The yescrypt
algorithm must be supported by the crypt(3) function.
rounds=n
Set the optional number of rounds of the SHA256, SHA512, blowfish, gost-yescrypt, and yescrypt
password hashing algorithms to n.
broken_shadow
Ignore errors reading shadow information for users in the account management module.
minlen=n
Set a minimum password length of n characters. The max. for DES crypt based passwords is 8
characters.
obscure
Enable some extra checks on password strength. These checks are based on the "obscure" checks in the
original shadow package. The behavior is similar to the pam_cracklib module, but for
non-dictionary-based checks. The following checks are implemented:
Palindrome
Verifies that the new password is not a palindrome of (i.e., the reverse of) the previous one.
CaseChangeOnly
Verifies that the new password isn't the same as the old one with a change of case.
Similar
Verifies that the new password isn't too much like the previous one.
Simple
Is the new password too simple? This is based on the length of the password and the number of
different types of characters (alpha, numeric, etc.) used.
Rotated
Is the new password a rotated version of the old password? (E.g., "billy" and "illyb")
no_pass_expiry
When set ignore password expiration as defined by the shadow entry of the user. The option has an
effect only in case pam_unix was not used for the authentication or it returned authentication
failure meaning that other authentication source or method succeeded. The example can be public key
authentication in sshd. The module will return PAM_SUCCESS instead of eventual PAM_NEW_AUTHTOK_REQD
or PAM_AUTHTOK_EXPIRED.
Invalid arguments are logged with syslog(3).