Module Name; Module Arguments; Sample Pam Configuration Files - Red Hat ENTERPRISE LINUX 4.5.0 Reference Manual

Table of Contents

Advertisement

Chapter 16. Pluggable Authent...
A newer control flag syntax which allows for more precise control is now available for PAM.
Please see the PAM documentation located in the
directory for information on this new syntax (where
for PAM).

3.3. Module Name

The module name provides PAM the name of the pluggable module containing the specified
module interface. Under older versions of Red Hat Enterprise Linux, the full path to the module
was provided within the PAM configuration file, such as
However, since the advent of multilib systems, which store 64-bit PAM modules within the
directory, the directory name is omitted because the application is linked to
/lib64/security/
the appropriate version of

3.4. Module Arguments

PAM uses arguments to pass information to a pluggable module during authentication for some
modules.
For example, the
pam_userdb.so
authenticate the user. Berkeley DB is an open source database system embedded in many
applications. The module takes a
use for the requested service.
A typical
pam_userdb.so
auth required pam_userdb.so db=<path-to-file>
In the previous example, replace
database file.
Invalid arguments are ignored and do not otherwise affect the success or failure of the PAM
module. However, most modules report errors to the

4. Sample PAM Configuration Files

Below is a sample PAM application configuration file:
#%PAM-1.0 auth required pam_securetty.so auth required pam_unix.so shadow
nullok auth required pam_nologin.so account required pam_unix.so password
required pam_cracklib.so retry=3 password required pam_unix.so shadow nullok
use_authtok session required pam_unix.so
The first line is a comment as denoted by the hash mark (
Lines two through four stack three modules for login authentication.
300
, which can locate the correct version of the module.
libpam
module uses secrets stored in a Berkeley DB file to
argument so that Berkeley DB knows which database to
db
line within a PAM configuration file looks like this:
<path-to-file>
/usr/share/doc/pam-<version-number>/
is the version number
<version-number>
/lib/security/pam_stack.so
with the full path to the Berkeley DB
/var/log/messages
) at the beginning of the line.
#
.
file.

Advertisement

Table of Contents
loading

Table of Contents