Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Pluggable Authentication Modules


Related Topics
EVR

In the News (Wed 23 Dec 09)

  
  Pluggable Authentication Modules - Wikipedia, the free encyclopedia
Pluggable authentication modules or PAM are a mechanism to integrate multiple low-level authentication schemes into a high-level API, which allows for programs that rely on authentication to be written independently of the underlying authentication scheme.
PAM were first developed in 1996 by Sun Microsystems, and are currently supported in AIX, HP-UX, Solaris, Linux, FreeBSD, Mac OS X and NetBSD.
PAM was later standardized as part of the XOpen UNIX standardization process, resulting in the XSSO standard.
en.wikipedia.org /wiki/Pluggable_Authentication_Modules   (238 words)

  
 [No title]   (Site not responding. Last check: 2007-10-06)
PAM, as discussed in this document, is a generalization of the approach first introduced in [1].
PAM makes no assumptions about how data is encapsulated for exchanges between the server and the client, only that full octet sequences can be freely exchanged without corruption.
PAM represents a server-driven authentication model, so by default any available agent may be invoked in the authentication process.
www.kernel.org /pub/linux/libs/pam/pre/doc/current-draft.txt   (3136 words)

  
 Pluggable Authentication Modules for Linux | Linux Journal
That is, the pluggability of PAM is dynamic and thus at the discretion of the local system administrator.
Modules of account-management type can be used to restrict users from logging in at certain times of the day/week or for enforcing password expiration.
This module can be configured to permit or deny access to users based on their terminal line, the time they are logging in and what they intend to do.
www.linuxjournal.com /article/2120   (3555 words)

  
 Chapter 25: PAM - Pluggable Authentication Modules   (Site not responding. Last check: 2007-10-06)
Which authentication module is to be attatched is dependent upon the local system setup and is at the discretion of the local system administrator.
PAM is designed to provide the system administrator with a great deal of flexibility in configuring the privilege granting applications of their system.
After the module was used to check if the users name and password are valid (at the very beginning of the configuration file), now the account component is used to check if the users password is about to expire and prompt the user for a new password if this is the case.
linux.rsquare.nl /geekbook/chapter25.html   (4267 words)

  
 Linux: PAM (Pluggable Authentication Modules) - Authentication   (Site not responding. Last check: 2007-10-06)
Pluggable authentication modules are at the core of user authentication in any modern linux distribution.
PAM can be configured to deny certain programs the right to authenticate users, to only allow certain users to be authenticated, to warn when certain programs attempt to authenticate, or even to deprive all users of login privileges.
Most of the required modules are pam_unix.so (the main authentication module), the single requisite module is pam_securetty.so (checks make sure the user is logging in on a secure console), and the only optional module is pam_lastlogin.so (the module that retrieves information on the user's most recent login).
www.linuxforum.com /linux-user-authentication/x101.html   (1256 words)

  
 Pluggable Authentication Modules (PAM) Documentation
The PAM configuration files specify which groups are required by each PAM-enabled application, and which PAM modules are to be invoked for each group within each application.
Note that this separation of PAM modules from PAM-enabled commands means that once an application is coded to use PAM, it can be configured to use different authentication mechanisms without any changes being made to it.
The following PAM modules are implemented in the PAM libraries on UnixWare: Their functions and arguments are the same as documented in the PAM System Administrator's Guide, except as noted below.
ou800doc.caldera.com /en/SEC_pam/pamintro.html   (910 words)

  
 Chapter 20. PAM — Pluggable Authentication Modules
PAM modules are available on a system-wide basis, so they can be requested by any application.
Whenever a newly required authentication scheme is needed, it is sufficient to adapt or write a suitable PAM module for use by the program in question.
Different types of modules have different purposes, for example, one module checks the password, another one verifies the location from which the system is accessed, and yet another one reads user-specific settings.
www-uxsup.csx.cam.ac.uk /pub/doc/suse/sles9/adminguide-sles9/ch20.html   (715 words)

  
 Chapter 16. Pluggable Authentication Modules (PAM)
PAM policies are defined on a per-service basis, so all servers that claim the same service name will be subject to the same policy.
A PAM module is a self-contained piece of program code that implements the primitives in one or more facilities for one particular mechanism; possible mechanisms for the authentication facility, for instance, include the UNIX® password database, NIS, LDAP and Radius.
Although Solaris™; PAM modules commonly have a version number, they're not truly versioned, because the number is a part of the module name and must be included in the configuration.
www.netbsd.org /guide/en/chap-pam.html   (3984 words)

  
 pam.conf(5) - Pluggable Authentication Modules
PAM Is a system of libraries that handle the authentication tasks of applications (services) on the system.
The principal feature of the PAM approach is that the nature of the authentication is dynamically configurable.
Not all authentications are of this type, there exist hardware based authentication schemes (such as the use of smart-cards and biometric devices), with suitable modules, these may be substituted seamlessly for more standard approaches to authentication - such is the flexibility of
www.gsp.com /cgi-bin/man.cgi?section=5&topic=pam.conf   (820 words)

  
 RFC NNN
The authentication infrastructure and its components may have to be modified or replaced either because some deficiencies have been found in the current algorithms, or because sites want to enforce a different security policy than what was provided by the system vendor.
Once the primary password is verified, the authentication modules would obtain the other passwords for their own mechanisms by decrypting the mechanism-specific encrypted password with the primary password, and passing it to the authentication service.
Another design decision we have made is that PAM gives only the user name to all the underlying PAM modules, hence it is the responsibility of the PAM modules to convert the name to their own internal format.
www.opengroup.org /tech/rfc/rfc86.0.html   (6352 words)

  
 Pluggable Authentication Modules (PAM)
When you log in to a system, you provide your username and password, and the login process uses the username and password to authenticate the login — to verify that you are who you say you are.
Pluggable Authentication Modules (PAM) is a way of allowing the system administrator to set an authentication policy without having to recompile authentication programs.
PAM can be implemented with various applications without having to recompile the applications to specifically support PAM.
www.redhat.com /docs/manuals/linux/RHL-7.2-Manual/ref-guide/ch-pam.html   (279 words)

  
 Appendix A Pluggable Authentication Modules
While some Solaris PAM modules are LDAP-aware, other modules do not use LDAP in a way that triggers Identity Synchronization for Windows’ interception actions.
Furthermore, the binding mechanism you use must be a form that presents the user's password in a non-obfuscated manner, such as a simple bind, which precludes the use of SASL and Digest mechanisms.
When you are finished configuring the LDAP repository for PAM, continue to Step 3: Populating the LDAP Repository.
docs.sun.com /source/817-6200/appendixA.html   (4550 words)

  
 Pluggable Authentication Modules (PAM)   (Site not responding. Last check: 2007-10-06)
In HP-UX 10.30, PAM is put in the OS-Core fileset, which used to be in the CDE-PAM fileset in HP-UX 10.20.
PAM interfaces for applications (that is, PAM APIs) are supported.
This file is used to configure PAM on a per-user basis.
docs.hp.com /en/5965-4406/ch02s22.html   (270 words)

  
 AntiOnline - PAM (Pluggable Authentication Modules) Security
The Pluggable Authentication Modules for Linux is a collection of shared libraries, which provide the authentication modules.
If other authentication mechanisms are to be used such as chip cards instead of passwords, then several programs have to be executed which perform an authentication which will work together with a chip card.
Since PAM creates a layer between an application and the authentication mechanism, many other “single-steps” for the authentication process can be configured here with great detail.
www.antionline.com /showthread.php?threadid=240119   (969 words)

  
 Pluggable Authentication Modules
This article describes the underlying principles and mechanisms of the Pluggable Authentication Modules (PAM) library, and explains how to configure PAM, how to integrate PAM into applications, and how to write PAM modules.
The Pluggable Authentication Modules (PAM) library is a generalized API for authentication-related services which allows a system administrator to add new authentication methods simply by installing new PAM modules, and to modify authentication policies by editing configuration files.
PAM was defined and developed in 1995 by Vipin Samar and Charlie Lai of Sun Microsystems, and has not changed much since.
www.freebsd.org /doc/en_US.ISO8859-1/articles/pam   (358 words)

  
 Understanding Pluggable Authentication Modules (PAM)
Think of a PAM module as a separate program, that can be plugged into other programs as needed.
Since this is a "sufficient" task, if the module passes, control of the authentication process skips the remaining "auth" steps and jumps to the next phase, the "password" realm.
So in short, Pluggable Authentication Modules are like an Erector(TM) set; the system administrator can use different modules to perform different tasks, and tie them in with other applications on the system.
faculty.acu.edu /~westk/pam.html   (739 words)

  
 SecuriTeam™ - Linux Pluggable Authentication Modules (PAM) insecurity.
Linux Pluggable Authentication Modules provide a way to develop programs that are independent of authentication scheme.
These modules are vulnerable to an attack which might be exploited to gain read/write permissions to the /etc/shadow file.
Linux Pluggable Authentication Modules version 0.64-2 (as well as previous ones), are vulnerable to an attack which may be exploited to gain read/write permissions to the /etc/shadow file.
www.securiteam.com /exploits/3W5QEQUNFM.html   (376 words)

  
 Pluggable Authentication Modules - pam_sm_chauthtok()
Upon successful completion of the call, the authentication token of the user will be ready for change or will be changed (depending upon the flag) in accordance with the authentication scheme configured within the system.
During this stage, the password modules should only perform preliminary checks (ping remote name services to see if they are ready for updates, for example).
Specifies the module options, which are interpreted and processed by the password management module.
www.opengroup.org /onlinepubs/008329799/pam_sm_chauthtok.htm   (530 words)

  
 Pluggable Authentication Modules (PAM)   (Site not responding. Last check: 2007-10-06)
PAM uses a pluggable, modular architecture, which affords the system administrator a great deal of flexibility in setting authentication policies for the system.
In most situations, the default PAM configuration file for a PAM-aware application is sufficient.
Provides a common authentication scheme that can be used with a wide variety of applications.
www.php-editors.com /linuxredhat/ch-pam.html   (201 words)

  
 PAM, pluggable authentication modules « WordPress Support
It would be very interesting to add PAM support to the authentication mechanism.
Authentication against PAM (once installed with php_pam) is as easy as: pam_auth($username, $password, &$pam_error);
Would certainly be good, as it'd be nice to be able to use a universal login system no matter what blog/cms vs forum vs wiki vs whatever you happen to want to combine -- if everybody would adopt an open login system, it'd be a great help.
wordpress.org /support/topic/28000   (191 words)

  
 Authentication - Pluggable Authentication Modules
PAM (Pluggable Authentication Modules) Pluggable authentication modules are at the core of user authentication in any modern linux
7.2 Modules pam_cracklib: uses the cracklib library to check the "strength" of a password and to check it was not built based on the old one.
Pluggable Authentication Modules StyX styx at mailbox.as Fri Mar 9 13:40:12 MST 2001.
authentication.chaokeng.com /pluggableauthenticationmodules   (698 words)

  
 PAM (Pluggable Authentication Modules)   (Site not responding. Last check: 2007-10-06)
If pam was detected on your system during compilation, wzdftpd can try to authenticate to the PAM subsystem by sending the login and password.
To change a password, you have to specify the old password (this is needed by PAM).
When changing a password using the pam method, be advised that pam will handle the password change, and that this will probably also mean changing it on the system.
www.wzdftpd.net /fulldocs/auth_pam.php   (113 words)

  
 What are Pluggable Authentication Modules?
Pluggable Authentication Modules (PAM) are an enhancement to Unix authentication which enable a wide range of identity management databases to be utilized in addition to the standard /etc/passwd file.
Pluggable Authentication Modules have been created to allow authentication from sources such as Kerberos, RADIUS, S/key, DCE, Active Directory, and RSA SecureID.
The Pluggable Authentication Module architecture was designed by Sun Microsystems and incorporated in Solaris 2.6.
www.tech-faq.com /pluggable-authentication-modules.shtml   (190 words)

  
 Sys Admin > v09, i09: PAM -- Pluggable Authentication Modules
PAM (Pluggable Authentication Modules) provides the backbone of most authentication in modern Linux systems (and can be implemented in others, such as Solaris), yet it is typically ignored and woefully under-utilized.
With shadow passwords, instead of keeping the user data and encrypted password in the same file, the password was kept in a separate file that only the system could access.
Unfortunately, any program that needed to authenticate users had to be recompiled with shadow password support, and this process could take quite a while because every network daemon, and numerous local utilities, had to be updated.
www.samag.com /documents/s=1161/sam0009a/0009a.htm   (778 words)

  
 PAM (Pluggable Authentication Modules)
(the main authentication module), the single requisite module is
(the module that retrieves information on the user's most recent login).
Except for this minor difference, all the rest of the configuration PAM syntax applies.
docmirror.net /en/linux/howto/admin/User-Authentication-HOWTO/x115.html   (1182 words)

  
 Pluggable Authentication Modules for Windows NT - Itoi, Honeyman (ResearchIndex)   (Site not responding. Last check: 2007-10-06)
If your firewall is blocking outgoing connections to port 3125, you can use these links to download local copies.
Abstract: To meet the challenge of integrating new methods and technologies into the Internet security framework, it is useful to hide low-level authentication mechanisms from application programmers, system administrators, and users, replacing them with abstractions at a higher level.
The Pluggable Authentication Method approach popular in Linux, Solaris, and CDE offers one such abstraction.
citeseer.ist.psu.edu /492866.html   (228 words)

  
 A Linux-PAM page   (Site not responding. Last check: 2007-10-06)
Info on PAM modules and applications that reside around the 'net.
The XSSO spec which is X/Open's attempt to absorb PAM into something bigger (draft from 1997 courteously made available to us by Vipin).
All of the source code for PAM is here.
www.kernel.org /pub/linux/libs/pam   (335 words)

  
 Security
Security packages recognize users, authenticate code objects, grant trusted objects access to system resources, allow trusted objects to perform actions that affect system resources, and transport messages and data across a network using secure transport protocols and encrypted data formats.
The Java security APIs span a wide range of areas, including cryptography, public key infrastructure, secure communication, authentication, and access control.
Java security technology provides the developer with a comprehensive security framework for writing applications, and also provides the user or administrator with a a set of tools to securely manage applications.
java.sun.com /security/jaas/doc/pam.html   (293 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.