Linux PAM: Difference between revisions
Content deleted Content added
Added great description of Linux-Pam. Parts of its explanation should be added to this article. |
|||
| Line 17: | Line 17: | ||
* [http://www.kernel.org/pub/linux/libs/pam/ Linux-PAM page] |
* [http://www.kernel.org/pub/linux/libs/pam/ Linux-PAM page] |
||
* [http://linux.die.net/man/8/pam.d pam.d(8) - Linux man page] |
* [http://linux.die.net/man/8/pam.d pam.d(8) - Linux man page] |
||
* [http://www.kernel.org/pub/linux/libs/pam/whatispam.html |
* [http://www.kernel.org/pub/linux/libs/pam/whatispam.html What is Linux-PAM?] |
||
[[Category:Linux]] |
[[Category:Linux]] |
||
Revision as of 04:51, 2 November 2010
 | This article includes a list of references, related reading, or external links, but its sources remain unclear because it lacks inline citations. (September 2010) |
 |
Linux Pluggable Authentication Modules (PAM) provide dynamic authorization for applications and services in a Linux system. Linux PAM is evolved from the Unix Pluggable Authentication Modules architecture.
There are four groups for independent management:
- Account modules check that the specified account is a valid authentication target under current conditions. This may include conditions like account expiration, time of day, and that the user has access to the requested service.
- Authentication modules verify the user's identity, for example by requesting and checking a password or other secret. They may also pass authentication information on to other systems like a keyring.
- Password modules are responsible for updating passwords, and are generally coupled to modules employed in the authentication step. They may also be used to enforce strong passwords.
- Session modules define actions that are performed at the beginning and end of sessions. A session starts after the user has successfully authenticated.
See also
External links
 | This software article is a stub. You can help Wikipedia by expanding it. |