Jump to content

Linux PAM: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
No edit summary
BG19bot (talk | contribs)
m WP:CHECKWIKI error fix for #03. Missing Reflist. Do general fixes if a problem exists. - using AWB (11700)
Line 1: Line 1:
{{nofootnotes|date=September 2010}}
{{more footnotes|date=September 2010}}
{{Infobox software
{{Infobox software
| name =
| name =
Line 40: Line 40:
* [[OpenPAM]]
* [[OpenPAM]]
* [[fprint]]
* [[fprint]]

==References==
{{Reflist}}


==External links==
==External links==
Line 51: Line 54:
[[Category:Linux kernel features]]
[[Category:Linux kernel features]]
[[Category:Computer access control frameworks]]
[[Category:Computer access control frameworks]]



{{Security-software-stub}}
{{Security-software-stub}}

Revision as of 10:28, 8 November 2015

Stable release
1.1.8 / September 19, 2013; 11 years ago (2013-09-19)
Repository
Written inC
Operating systemLinux
Typeauthentication
LicenseGNU General Public License or Revised BSD License
Websitewww.linux-pam.org

Linux Pluggable Authentication Modules (PAM) provide dynamic authentication support for applications and services in a GNU/Linux or GNU/kFreeBSD[1] 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.

See also

References