Linux PAM: Difference between revisions

Revision as of 12:39, 4 June 2014

Revision as of 15:54, 19 August 2014

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.

ThereLinux-PAM areseparates fourthe groupstasks forof authentication into four independent management groups:

* Accountaccount 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.

* Authenticationauthentication 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.

* Passwordpassword 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]].

* Sessionsession 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]]