Linux PAM: Difference between revisions

Stable release	1.1.8 / September 19, 2013; 11 years ago
Repository	github.com/linux-pam/linux-pam ;
Written in	C
Operating system	Linux
Type	authentication
License	GNU General Public License or Revised BSD License
Website	www.linux-pam.org

Browse history interactively

← Previous edit Next edit →

Content deleted Content added

VisualWikitext

Inline

Revision as of 15:54, 19 August 2014

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.

Linux-PAM separates the tasks of authentication into four independent management groups:

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.

External links

This security software article is a stub. You can help Wikipedia by expanding it.

@@ Line 1: / Line 1: @@
 {{nofootnotes|date=September 2010}}
+{{Infobox software
+| name                   =
+| title                  =
+| logo                   = <!-- Image name is enough -->
+| logo caption           =
+| logo size              =
+| logo alt               =
+| screenshot             = <!-- Image name is enough -->
+| caption                =
+| screenshot size        =
+| screenshot alt         =
+| author                 =
+| developer              =
+| released               = <!-- {{Start date and age|YYYY|MM|DD|df=yes/no}} -->
+| discontinued           =
+| latest release version = 1.1.8
+| latest release date    = {{Start date and age|2013|09|19}}
+| latest preview version =
+| latest preview date    = <!-- {{Start date and age|YYYY|MM|DD|df=yes/no}} -->
+| status                 =
+| programming language   = [[C (programming language)|C]]
+| operating system       = [[Linux]]
+| platform               =
+| size                   =
+| genre                  = authentication
+| license                = [[GNU General Public License]] or [[Revised BSD License]]
+| website                = {{URL|http://www.linux-pam.org/}}
+}}
 '''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:
+Linux-PAM separates the tasks of authentication into four independent management groups:
+* 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 (cryptography)|keyring]].
-* 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.
+* 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.
-* 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 (cryptography)|keyring]].
+* session modules define actions that are performed at the beginning and end of sessions. A session starts after the user has successfully authenticated.
-* 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==
+{{Portal|Linux|Free software}}
 * [[OpenPAM]]
 * [[fprint]]