RootZanli & NinjaCr3

: / usr / share / doc / pam-devel / html /
Filename : adg-glossary.html
back
<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Chapter 7. Glossary of PAM related terms</title><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="Linux-PAM_ADG.html" title="The Linux-PAM Application Developers' Guide"><link rel="up" href="Linux-PAM_ADG.html" title="The Linux-PAM Application Developers' Guide"><link rel="prev" href="adg-porting.html" title="Chapter 6. Porting legacy applications"><link rel="next" href="adg-example.html" title="Chapter 8. An example application"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 7. Glossary of PAM related terms</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="adg-porting.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="adg-example.html">Next</a></td></tr></table><hr></div><div class="chapter"><div class="titlepage"><div><div><h1 class="title"><a name="adg-glossary"></a>Chapter 7. Glossary of PAM related terms</h1></div></div></div><p>
      The following are a list of terms used within this document.
    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">Authentication token</span></dt><dd><p>
            Generally, this is a password. However, a user can authenticate
            him/herself in a variety of ways. Updating the user's
            authentication token thus corresponds to
            <span class="emphasis"><em>refreshing</em></span> the object they use to
            authenticate themself with the system. The word password is
            avoided to keep open the possibility that the authentication
            involves a retinal scan or other non-textual mode of
            challenge/response.
          </p></dd><dt><span class="term">Credentials</span></dt><dd><p>
            Having successfully authenticated the user, PAM is able to
            establish certain characteristics/attributes of the user.
            These are termed <span class="emphasis"><em>credentials</em></span>. Examples
            of which are group memberships to perform privileged tasks
            with, and <span class="emphasis"><em>tickets</em></span> in the form of
            environment variables etc. . Some user-credentials, such as
            the user's UID and GID (plus default group memberships) are
            not deemed to be PAM-credentials. It is the responsibility
            of the application to grant these directly.
          </p></dd></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="adg-porting.html">Prev</a> </td><td width="20%" align="center"> </td><td width="40%" align="right"> <a accesskey="n" href="adg-example.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 6. Porting legacy applications </td><td width="20%" align="center"><a accesskey="h" href="Linux-PAM_ADG.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 8. An example application</td></tr></table></div></body></html>