Académique Documents
Professionnel Documents
Culture Documents
html
The basic Pluggable Authentication Module and how to configure it and write a login app
Summary: The Pluggable Authentication Module (PAM) API exposes a set of functions that application programmers use for security-related
functions like user authentication, data encryption, LDAP, and more. In this article, get a basic guide to the PAM model on Linux, see how to
configure PAM, and learn how to design a sample PAM login application in 10 easy steps.
For Linux users, sharing files securely is a cumbersome task. For example, needing to recall multiple passwords is taxing, and redesigning system
access applications (like login, su, password, ftp, etc.) is time-consuming. Adding to the difficulty is the process of authentication, where a system
identifies a user and provides deserved access control to that user.
PAM is an API that takes care of authenticating a user to a service. Before PAM, applications like login (and rlogin, telnet, rsh) looked for the
username in /etc/passwd, then compared the two and authenticated the user-typed name. All applications used these shared services, although the
implementation details and authority to configure them was not shared.
Next, application developers tried coding their own processes. With this came the need to separate the application and security module (a common
security module can be shared by applications and can be configured as needed).
The PAM mechanism integrates multiple low-level authentication schemes into a high-level API that allows programs that rely on authentication
to be written independently of the underlying authentication scheme. The principal feature of PAM is the dynamic configuration of authentication
through either an /etc/pam.d or /etc/pam.conf file.
PAM can be configured to deny certain programs the right to authenticate users and to warn when certain programs attempt to authenticate. PAM
programs make use of PAM modules (authentication modules): They are attached to applications at runtime in order to work.
Figure 1. PAM library parses the config file and loads modules to it
PAM was first developed by Sun Microsystems in 1995 and is supported by the following operating system versions (and higher):
RedHat 5.0
SUSE 6.2
Debian 2.2
Mandrake 5.2
http://www.ibm.com/developerworks/linux/library/l-pam/index.html
Caldera 1.3
TurboLinux 3.6
PAM is also supported by recent versions of Solaris™, AIX®, HP-UX, and Mac OS® X. PAM was later standardized as a part of X/Open UNIX®
standardization process (in the X/Open single sign-on service (XSSO) architecture).
Though they are not strictly classified, you could say there are three kinds of PAM:
1. Linux-PAM: Linux-PAM covers all of the PAM discussed in this article. The main architecture of PAM on any of the Linux platforms is
similar to the Linux-PAM version.
2. OpenPAM: OpenPAM is another implementation of PAM developed by Dag-Erling Smorgrav at NAI labs as part of DARPA-CHATS
research program. Because it is open source, it is mainly used by FreeBSD, NetBSD, and applications (plus Mac OS X).
3. Java™ PAM or JPam: PAM is basically a standard authentication module supporting Linux and UNIX. JPam acts as a bridge between the
Java part and the usual PAM. JPam enables the use of PAM modules or facilities (like auth, account, passwd, session, etc.) by Java-based
applications. It features JAAS and direct APIs and support for most Unix OS and architectures.
Although these are different PAMs, their primary functionality remains the same.
PAM modules are classified into module type. Any given module should implement at least one of the four module type functions:
PAM provides different functional capabilities, such as single sign-on authentication, access control, and more. The implementation of each are
handled by different modules. Here are some of the major modules:
pam_access delivers log-daemon-style login access control using login/domain names depending on pre-defined rules in /etc/security
/access.conf.
pam_cracklib checks the passwords against the password rules.
pam_env sets/unsets environment variables from /etc/security/pam_env_conf.
pam_debug debugs PAM.
pam_deny locks out PAM modules.
pam_echo prints messages.
pam_exec executes an external command.
pam_ftp is the module for anonymous access.
pam_localuser requires the user to be listed in /etc/passwd.
pam_unix provides traditional password authentication from /etc/passwd.
There are many other modules (pam_userdb, pam_warn, pam_xauth), which take a set of values which they return. (Details of these modules can
be found in the PAM administration guide in Resources.)
Configuring PAM
PAM configuration is generally implemented in the configuration file residing in /etc/pam.d or /etc/pam.conf (for old versions).
For each service that uses PAM, there is a corresponding file in the directory, which contains the rules or instructions for how authentication and
account information should be obtained for that service. There is usually one rule per line.
The modules are invoked in the order in which they are listed in the configuration file, depending on what the Control_flag for each entry allows.
Control_flag values include:
Required: All required modules in a stack must pass for a successful result. If one or more of the required module fails, all of the required
modules in the stack are implemented, but the first error is returned.
Sufficient: If a module flagged as sufficient succeeds and no previous required or sufficient modules have failed, then all remaining modules
in the stack are ignored and success is returned.
Optional: If none of the modules in the stack are required and no sufficient modules have succeeded, then at least one optional module of the
service/application must succeed.
Table 1 shows some examples of PAM configuration files on various operating systems.
The default PAM configuration file /etc/pam.d is used for all other services that are not explicitly configured and is perhaps the simplest and
most robust default file upon which PAM relies. The internals look something like this:
/etc/pam.d/other File
This file is very simple. For all module types, the Control_flag is the same: required. Two modules are called:
Therefore, any service that uses PAM must be explicitly configured to allow authentication; otherwise, attempts will fail.
These 10 steps can help you implement your own PAM application and help you understand the workings of a PAM session:
1. Include header files for the PAM implementation (for example, pam_appl.h, pam_misc.h).
2. In the main function, initialize the PAM library libpam.so (which loads the modules specified in the configuration file for application) using
a unique handle.
3. Attempt authentication for all modules and handle failure scenarios.
4. Check for user credential and account details.
5. Open a new PAM session.
http://www.ibm.com/developerworks/linux/library/l-pam/index.html
In conclusion
Relying on PAM to help wrangle low-level authentication efforts into a more manageable whole is a sound move to simplifying this security
mechanism. In this article, you've learned:
Now you can move onto the more advanced topics in using PAM modules—starting with the Resources below..
Resources
Learn
The Linux-PAM guides offer documentation on systems administration issues, module writing, and application development.
Here's the view of PAM from the SUSE Linux Unofficial FAQ.
Take a look at the X/Open Single Sign-on Service (XSSO) architecture model.
In the developerWorks Linux zone, find more resources for Linux developers (including developers who are new to Linux), and scan our
most popular articles and tutorials.
With IBM trial software, available for download directly from developerWorks, build your next development project on Linux.
Discuss
Get involved in the developerWorks community through blogs, forums, podcasts, and spaces.
Vishal Srivistava has worked with the many flavors of UNIX and Linux at the core level. Since June 2007, Srivistava has been with IBM India
Software Labs and is currently a part of team responsible for the development of the core engine of IBM IIS. This position has given him lots of
experience in configuring the team application to use PAM on a multitude of UNIX platforms.
http://www.ibm.com/developerworks/linux/library/l-pam/index.html
Close [x]
IBM ID:
Need an IBM ID?
Forgot your IBM ID?
Password:
Forgot your password?
Change your password
The first time you sign into developerWorks, a profile is created for you. Select information in your developerWorks profile is displayed to the
public, but you may edit the information at any time. Your first name, last name (unless you choose to hide them), and display name will
accompany the content that you post.
Close [x]
The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies
the content you post on developerWorks.
Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be
your email address for privacy reasons.
1 star 1 star
2 stars 2 stars
3 stars 3 stars
4 stars 4 stars
5 stars 5 stars
Add comment: