diff options
Diffstat (limited to 'docs/htmldocs/Samba3-HOWTO/pam.html')
| -rw-r--r-- | docs/htmldocs/Samba3-HOWTO/pam.html | 210 |
1 files changed, 105 insertions, 105 deletions
diff --git a/docs/htmldocs/Samba3-HOWTO/pam.html b/docs/htmldocs/Samba3-HOWTO/pam.html index a58cb8bdb9..e6693b7c1e 100644 --- a/docs/htmldocs/Samba3-HOWTO/pam.html +++ b/docs/htmldocs/Samba3-HOWTO/pam.html @@ -1,30 +1,30 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 28. PAM-Based Distributed Authentication</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.72.0"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="ProfileMgmt.html" title="Chapter 27. Desktop Profile Management"><link rel="next" href="integrate-ms-networks.html" title="Chapter 29. Integrating MS Windows Networks with Samba"></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 28. PAM-Based Distributed Authentication</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ProfileMgmt.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="integrate-ms-networks.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pam"></a>Chapter 28. PAM-Based Distributed Authentication</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Langasek</span></h3><div class="affiliation"><div class="address"><p><code class="email"><<a href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>></code></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="pam.html#id429934">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="pam.html#id430534">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id430584">PAM Configuration Syntax</a></span></dt><dt><span class="sect2"><a href="pam.html#id431487">Example System Configurations</a></span></dt><dt><span class="sect2"><a href="pam.html#id431757"><code class="filename">smb.conf</code> PAM Configuration</a></span></dt><dt><span class="sect2"><a href="pam.html#id431817">Remote CIFS Authentication Using <code class="filename">winbindd.so</code></a></span></dt><dt><span class="sect2"><a href="pam.html#id431902">Password Synchronization Using <code class="filename">pam_smbpass.so</code></a></span></dt></dl></dd><dt><span class="sect1"><a href="pam.html#id432259">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id432269">pam_winbind Problem</a></span></dt><dt><span class="sect2"><a href="pam.html#id432358">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><p> -<a class="indexterm" name="id429865"></a> -<a class="indexterm" name="id429872"></a> -<a class="indexterm" name="id429878"></a> -<a class="indexterm" name="id429885"></a> +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 28. PAM-Based Distributed Authentication</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.1"><link rel="start" href="index.html" title="The Official Samba 3.2.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="ProfileMgmt.html" title="Chapter 27. Desktop Profile Management"><link rel="next" href="integrate-ms-networks.html" title="Chapter 29. Integrating MS Windows Networks with Samba"></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 28. PAM-Based Distributed Authentication</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ProfileMgmt.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="integrate-ms-networks.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="pam"></a>Chapter 28. PAM-Based Distributed Authentication</h2></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="surname">Terpstra</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jht@samba.org">jht@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Stephen</span> <span class="surname">Langasek</span></h3><div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:vorlon@netexpress.net">vorlon@netexpress.net</a>></code></p></div></div></div></div><div><p class="pubdate">May 31, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="pam.html#id2687494">Features and Benefits</a></span></dt><dt><span class="sect1"><a href="pam.html#id2688125">Technical Discussion</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2688178">PAM Configuration Syntax</a></span></dt><dt><span class="sect2"><a href="pam.html#id2689176">Example System Configurations</a></span></dt><dt><span class="sect2"><a href="pam.html#id2689482"><code class="filename">smb.conf</code> PAM Configuration</a></span></dt><dt><span class="sect2"><a href="pam.html#id2689563">Remote CIFS Authentication Using <code class="filename">winbindd.so</code></a></span></dt><dt><span class="sect2"><a href="pam.html#id2689671">Password Synchronization Using <code class="filename">pam_smbpass.so</code></a></span></dt></dl></dd><dt><span class="sect1"><a href="pam.html#id2690064">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="pam.html#id2690075">pam_winbind Problem</a></span></dt><dt><span class="sect2"><a href="pam.html#id2690173">Winbind Is Not Resolving Users and Groups</a></span></dt></dl></dd></dl></div><p> +<a class="indexterm" name="id2687418"></a> +<a class="indexterm" name="id2687425"></a> +<a class="indexterm" name="id2687432"></a> +<a class="indexterm" name="id2687439"></a> This chapter should help you to deploy Winbind-based authentication on any PAM-enabled UNIX/Linux system. Winbind can be used to enable user-level application access authentication from any MS Windows NT domain, MS Windows 200x Active Directory-based domain, or any Samba-based domain environment. It will also help you to configure PAM-based local host access controls that are appropriate to your Samba configuration. </p><p> -<a class="indexterm" name="id429899"></a> -<a class="indexterm" name="id429906"></a> +<a class="indexterm" name="id2687456"></a> +<a class="indexterm" name="id2687463"></a> In addition to knowing how to configure Winbind into PAM, you will learn generic PAM management possibilities and in particular how to deploy tools like <code class="filename">pam_smbpass.so</code> to your advantage. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> The use of Winbind requires more than PAM configuration alone. -Please refer to <a href="winbind.html" title="Chapter 24. Winbind: Use of Domain Accounts">Winbind: Use of Domain Accounts</a>, for further information regarding Winbind. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id429934"></a>Features and Benefits</h2></div></div></div><p> -<a class="indexterm" name="id429941"></a> -<a class="indexterm" name="id429948"></a> -<a class="indexterm" name="id429955"></a> -<a class="indexterm" name="id429961"></a> -<a class="indexterm" name="id429970"></a> -<a class="indexterm" name="id429977"></a> -<a class="indexterm" name="id429984"></a> -<a class="indexterm" name="id429991"></a> +Please refer to <a class="link" href="winbind.html" title="Chapter 24. Winbind: Use of Domain Accounts">Winbind: Use of Domain Accounts</a>, for further information regarding Winbind. +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2687494"></a>Features and Benefits</h2></div></div></div><p> +<a class="indexterm" name="id2687502"></a> +<a class="indexterm" name="id2687509"></a> +<a class="indexterm" name="id2687516"></a> +<a class="indexterm" name="id2687522"></a> +<a class="indexterm" name="id2687532"></a> +<a class="indexterm" name="id2687538"></a> +<a class="indexterm" name="id2687545"></a> +<a class="indexterm" name="id2687552"></a> A number of UNIX systems (e.g., Sun Solaris), as well as the xxxxBSD family and Linux, now utilize the Pluggable Authentication Modules (PAM) facility to provide all authentication, authorization, and resource control services. Prior to the introduction of PAM, a decision @@ -33,17 +33,17 @@ would require the provision of alternatives for all programs that provide securi Such a choice would involve provision of alternatives to programs such as <code class="literal">login</code>, <code class="literal">passwd</code>, <code class="literal">chown</code>, and so on. </p><p> -<a class="indexterm" name="id430029"></a> -<a class="indexterm" name="id430035"></a> -<a class="indexterm" name="id430042"></a> -<a class="indexterm" name="id430049"></a> +<a class="indexterm" name="id2687594"></a> +<a class="indexterm" name="id2687600"></a> +<a class="indexterm" name="id2687607"></a> +<a class="indexterm" name="id2687614"></a> PAM provides a mechanism that disconnects these security programs from the underlying authentication/authorization infrastructure. PAM is configured by making appropriate modifications to one file, <code class="filename">/etc/pam.conf</code> (Solaris), or by editing individual control files that are located in <code class="filename">/etc/pam.d</code>. </p><p> -<a class="indexterm" name="id430073"></a> -<a class="indexterm" name="id430079"></a> +<a class="indexterm" name="id2687641"></a> +<a class="indexterm" name="id2687647"></a> On PAM-enabled UNIX/Linux systems, it is an easy matter to configure the system to use any authentication backend so long as the appropriate dynamically loadable library modules are available for it. The backend may be local to the system or may be centralized on a @@ -51,94 +51,94 @@ remote server. </p><p> PAM support modules are available for: </p><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/passwd</code></span></dt><dd><p> -<a class="indexterm" name="id430107"></a> -<a class="indexterm" name="id430114"></a> -<a class="indexterm" name="id430120"></a> -<a class="indexterm" name="id430127"></a> -<a class="indexterm" name="id430134"></a> -<a class="indexterm" name="id430141"></a> +<a class="indexterm" name="id2687678"></a> +<a class="indexterm" name="id2687685"></a> +<a class="indexterm" name="id2687691"></a> +<a class="indexterm" name="id2687698"></a> +<a class="indexterm" name="id2687705"></a> +<a class="indexterm" name="id2687712"></a> There are several PAM modules that interact with this standard UNIX user database. The most common are called <code class="filename">pam_unix.so</code>, <code class="filename">pam_unix2.so</code>, <code class="filename">pam_pwdb.so</code> and <code class="filename">pam_userdb.so</code>. </p></dd><dt><span class="term">Kerberos</span></dt><dd><p> -<a class="indexterm" name="id430182"></a> -<a class="indexterm" name="id430189"></a> -<a class="indexterm" name="id430196"></a> -<a class="indexterm" name="id430202"></a> -<a class="indexterm" name="id430209"></a> +<a class="indexterm" name="id2687754"></a> +<a class="indexterm" name="id2687761"></a> +<a class="indexterm" name="id2687768"></a> +<a class="indexterm" name="id2687775"></a> +<a class="indexterm" name="id2687782"></a> The <code class="filename">pam_krb5.so</code> module allows the use of any Kerberos-compliant server. This tool is used to access MIT Kerberos, Heimdal Kerberos, and potentially Microsoft Active Directory (if enabled). </p></dd><dt><span class="term">LDAP</span></dt><dd><p> -<a class="indexterm" name="id430233"></a> -<a class="indexterm" name="id430240"></a> -<a class="indexterm" name="id430247"></a> -<a class="indexterm" name="id430254"></a> -<a class="indexterm" name="id430260"></a> -<a class="indexterm" name="id430267"></a> +<a class="indexterm" name="id2687807"></a> +<a class="indexterm" name="id2687814"></a> +<a class="indexterm" name="id2687821"></a> +<a class="indexterm" name="id2687828"></a> +<a class="indexterm" name="id2687835"></a> +<a class="indexterm" name="id2687842"></a> The <code class="filename">pam_ldap.so</code> module allows the use of any LDAP v2- or v3-compatible backend server. Commonly used LDAP backend servers include OpenLDAP v2.0 and v2.1, Sun ONE iDentity server, Novell eDirectory server, and Microsoft Active Directory. </p></dd><dt><span class="term">NetWare Bindery</span></dt><dd><p> -<a class="indexterm" name="id430292"></a> -<a class="indexterm" name="id430299"></a> -<a class="indexterm" name="id430306"></a> -<a class="indexterm" name="id430313"></a> +<a class="indexterm" name="id2687869"></a> +<a class="indexterm" name="id2687876"></a> +<a class="indexterm" name="id2687883"></a> +<a class="indexterm" name="id2687890"></a> The <code class="filename">pam_ncp_auth.so</code> module allows authentication off any bindery-enabled NetWare Core Protocol-based server. </p></dd><dt><span class="term">SMB Password</span></dt><dd><p> -<a class="indexterm" name="id430336"></a> -<a class="indexterm" name="id430343"></a> -<a class="indexterm" name="id430350"></a> +<a class="indexterm" name="id2687915"></a> +<a class="indexterm" name="id2687922"></a> +<a class="indexterm" name="id2687929"></a> This module, called <code class="filename">pam_smbpass.so</code>, allows user authentication of the passdb backend that is configured in the Samba <code class="filename">smb.conf</code> file. </p></dd><dt><span class="term">SMB Server</span></dt><dd><p> -<a class="indexterm" name="id430379"></a> -<a class="indexterm" name="id430386"></a> +<a class="indexterm" name="id2687960"></a> +<a class="indexterm" name="id2687966"></a> The <code class="filename">pam_smb_auth.so</code> module is the original MS Windows networking authentication tool. This module has been somewhat outdated by the Winbind module. </p></dd><dt><span class="term">Winbind</span></dt><dd><p> -<a class="indexterm" name="id430410"></a> -<a class="indexterm" name="id430417"></a> -<a class="indexterm" name="id430424"></a> -<a class="indexterm" name="id430430"></a> +<a class="indexterm" name="id2687992"></a> +<a class="indexterm" name="id2687998"></a> +<a class="indexterm" name="id2688005"></a> +<a class="indexterm" name="id2688012"></a> The <code class="filename">pam_winbind.so</code> module allows Samba to obtain authentication from any MS Windows domain controller. It can just as easily be used to authenticate users for access to any PAM-enabled application. </p></dd><dt><span class="term">RADIUS</span></dt><dd><p> -<a class="indexterm" name="id430455"></a> +<a class="indexterm" name="id2688038"></a> There is a PAM RADIUS (Remote Access Dial-In User Service) authentication module. In most cases, administrators need to locate the source code for this tool and compile and install it themselves. RADIUS protocols are used by many routers and terminal servers. </p></dd></dl></div><p> -<a class="indexterm" name="id430472"></a> -<a class="indexterm" name="id430479"></a> +<a class="indexterm" name="id2688058"></a> +<a class="indexterm" name="id2688065"></a> Of the modules listed, Samba provides the <code class="filename">pam_smbpasswd.so</code> and the <code class="filename">pam_winbind.so</code> modules alone. </p><p> -<a class="indexterm" name="id430501"></a> -<a class="indexterm" name="id430508"></a> -<a class="indexterm" name="id430515"></a> -<a class="indexterm" name="id430522"></a> +<a class="indexterm" name="id2688088"></a> +<a class="indexterm" name="id2688095"></a> +<a class="indexterm" name="id2688102"></a> +<a class="indexterm" name="id2688109"></a> Once configured, these permit a remarkable level of flexibility in the location and use of distributed Samba domain controllers that can provide wide-area network bandwidth, efficient authentication services for PAM-capable systems. In effect, this allows the deployment of centrally managed and maintained distributed authentication from a single-user account database. -</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id430534"></a>Technical Discussion</h2></div></div></div><p> -<a class="indexterm" name="id430542"></a> -<a class="indexterm" name="id430548"></a> -<a class="indexterm" name="id430555"></a> -<a class="indexterm" name="id430562"></a> +</p></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2688125"></a>Technical Discussion</h2></div></div></div><p> +<a class="indexterm" name="id2688133"></a> +<a class="indexterm" name="id2688139"></a> +<a class="indexterm" name="id2688146"></a> +<a class="indexterm" name="id2688153"></a> PAM is designed to provide system administrators with a great deal of flexibility in configuration of the privilege-granting applications of their system. The local configuration of system security controlled by PAM is contained in one of two places: either the single system file <code class="filename">/etc/pam.conf</code> or the <code class="filename">/etc/pam.d/</code> directory. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id430584"></a>PAM Configuration Syntax</h3></div></div></div><p> -<a class="indexterm" name="id430592"></a> -<a class="indexterm" name="id430599"></a> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2688178"></a>PAM Configuration Syntax</h3></div></div></div><p> +<a class="indexterm" name="id2688186"></a> +<a class="indexterm" name="id2688193"></a> In this section we discuss the correct syntax of and generic options respected by entries to these files. PAM-specific tokens in the configuration file are case insensitive. The module paths, however, are case sensitive, since they indicate a file's name and reflect the case dependence of typical file systems. The @@ -148,8 +148,8 @@ In addition to the lines described below, there are two special characters provi of the system administrator: comments are preceded by a “<span class="quote">#</span>” and extend to the next end-of-line; also, module specification lines may be extended with a “<span class="quote">\</span>”-escaped newline. </p><p> -<a class="indexterm" name="id430625"></a> -<a class="indexterm" name="id430632"></a> +<a class="indexterm" name="id2688225"></a> +<a class="indexterm" name="id2688232"></a> If the PAM authentication module (loadable link library file) is located in the default location, then it is not necessary to specify the path. In the case of Linux, the default location is <code class="filename">/lib/security</code>. If the module @@ -157,12 +157,12 @@ is located outside the default, then the path must be specified as: </p><pre class="programlisting"> auth required /other_path/pam_strange_module.so </pre><p> -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id430654"></a>Anatomy of <code class="filename">/etc/pam.d</code> Entries</h4></div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2688257"></a>Anatomy of <code class="filename">/etc/pam.d</code> Entries</h4></div></div></div><p> The remaining information in this subsection was taken from the documentation of the Linux-PAM project. For more information on PAM, see -<a href="http://ftp.kernel.org/pub/linux/libs/pam/" target="_top">the Official Linux-PAM home page</a>. +<a class="ulink" href="http://ftp.kernel.org/pub/linux/libs/pam/" target="_top">the Official Linux-PAM home page</a>. </p><p> -<a class="indexterm" name="id430678"></a> +<a class="indexterm" name="id2688283"></a> A general configuration line of the <code class="filename">/etc/pam.conf</code> file has the following form: </p><pre class="programlisting"> service-name module-type control-flag module-path args @@ -172,9 +172,9 @@ We explain the meaning of each of these tokens. The second (and more recently ad way of configuring Linux-PAM is via the contents of the <code class="filename">/etc/pam.d/</code> directory. Once we have explained the meaning of the tokens, we describe this method. </p><div class="variablelist"><dl><dt><span class="term">service-name</span></dt><dd><p> -<a class="indexterm" name="id430720"></a> -<a class="indexterm" name="id430727"></a> -<a class="indexterm" name="id430734"></a> +<a class="indexterm" name="id2688328"></a> +<a class="indexterm" name="id2688335"></a> +<a class="indexterm" name="id2688342"></a> The name of the service associated with this entry. Frequently, the service-name is the conventional name of the given application for example, <code class="literal">ftpd</code>, <code class="literal">rlogind</code> and <code class="literal">su</code>, and so on. @@ -186,28 +186,28 @@ Once we have explained the meaning of the tokens, we describe this method. </p></dd><dt><span class="term">module-type</span></dt><dd><p> One of (currently) four types of module. The four types are as follows: </p><div class="itemizedlist"><ul type="disc"><li><p> -<a class="indexterm" name="id430797"></a> -<a class="indexterm" name="id430804"></a> +<a class="indexterm" name="id2688410"></a> +<a class="indexterm" name="id2688417"></a> <em class="parameter"><code>auth:</code></em> This module type provides two aspects of authenticating the user. It establishes that the user is who he or she claims to be by instructing the application to prompt the user for a password or other means of identification. Second, the module can grant group membership (independently of the <code class="filename">/etc/groups</code> file) or other privileges through its credential-granting properties. </p></li><li><p> -<a class="indexterm" name="id430830"></a> -<a class="indexterm" name="id430837"></a> +<a class="indexterm" name="id2688446"></a> +<a class="indexterm" name="id2688453"></a> <em class="parameter"><code>account:</code></em> This module performs non-authentication-based account management. It is typically used to restrict/permit access to a service based on the time of day, currently available system resources (maximum number of users), or perhaps the location of the user login. For example, the “<span class="quote">root</span>” login may be permitted only on the console. </p></li><li><p> -<a class="indexterm" name="id430861"></a> +<a class="indexterm" name="id2688480"></a> <em class="parameter"><code>session:</code></em> Primarily, this module is associated with doing things that need to be done for the user before and after he or she can be given service. Such things include logging information concerning the opening and closing of some data exchange with a user, mounting directories, and so on. </p></li><li><p> -<a class="indexterm" name="id430880"></a> +<a class="indexterm" name="id2688501"></a> <em class="parameter"><code>password:</code></em> This last module type is required for updating the authentication token associated with the user. Typically, there is one module for each “<span class="quote">challenge/response</span>” authentication <em class="parameter"><code>(auth)</code></em> module type. @@ -221,10 +221,10 @@ Once we have explained the meaning of the tokens, we describe this method. <code class="filename">/etc/pam.conf</code> file; earlier entries are executed before later ones. As of Linux-PAM v0.60, this control-flag can be defined with one of two syntaxes. </p><p> -<a class="indexterm" name="id430936"></a> -<a class="indexterm" name="id430943"></a> -<a class="indexterm" name="id430950"></a> -<a class="indexterm" name="id430957"></a> +<a class="indexterm" name="id2688566"></a> +<a class="indexterm" name="id2688573"></a> +<a class="indexterm" name="id2688580"></a> +<a class="indexterm" name="id2688586"></a> The simpler (and historical) syntax for the control-flag is a single keyword defined to indicate the severity of concern associated with the success or failure of a specific module. There are four such keywords: <em class="parameter"><code>required</code></em>, <em class="parameter"><code>requisite</code></em>, @@ -350,13 +350,13 @@ user_name=“<span class="quote">%u</span>” and password=PASSWORD(R Any line in one of the configuration files that is not formatted correctly will generally tend (erring on the side of caution) to make the authentication process fail. A corresponding error is written to the system log files with a call to syslog(3). - </p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id431487"></a>Example System Configurations</h3></div></div></div><p> + </p></dd></dl></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689176"></a>Example System Configurations</h3></div></div></div><p> The following is an example <code class="filename">/etc/pam.d/login</code> configuration file. This example had all options uncommented and is probably not usable because it stacks many conditions before allowing successful completion of the login process. Essentially, all conditions can be disabled by commenting them out, except the calls to <code class="filename">pam_pwdb.so</code>. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id431510"></a>PAM: Original Login Config</h4></div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2689202"></a>PAM: Original Login Config</h4></div></div></div><p> </p><pre class="programlisting"> #%PAM-1.0 # The PAM configuration file for the “<span class="quote">login</span>” service @@ -373,7 +373,7 @@ session required pam_pwdb.so # password required pam_cracklib.so retry=3 password required pam_pwdb.so shadow md5 </pre><p> -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id431534"></a>PAM: Login Using <code class="filename">pam_smbpass</code></h4></div></div></div><p> +</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2689230"></a>PAM: Login Using <code class="filename">pam_smbpass</code></h4></div></div></div><p> PAM allows use of replaceable modules. Those available on a sample system include: </p><p><code class="prompt">$</code><strong class="userinput"><code>/bin/ls /lib/security</code></strong> </p><pre class="programlisting"> @@ -456,17 +456,17 @@ authentication to be configured in a single central file. The on the basis that it allows for easier administration. As with all issues in life, though, every decision has trade-offs, so you may want to examine the PAM documentation for further helpful information. -</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id431757"></a><code class="filename">smb.conf</code> PAM Configuration</h3></div></div></div><p> -There is an option in <code class="filename">smb.conf</code> called <a class="indexterm" name="id431775"></a>obey pam restrictions. +</p></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689482"></a><code class="filename">smb.conf</code> PAM Configuration</h3></div></div></div><p> +There is an option in <code class="filename">smb.conf</code> called <a class="link" href="smb.conf.5.html#OBEYPAMRESTRICTIONS">obey pam restrictions</a>. The following is from the online help for this option in SWAT: </p><div class="blockquote"><blockquote class="blockquote"><p> When Samba is configured to enable PAM support (i.e., <code class="option">--with-pam</code>), this parameter will control whether or not Samba should obey PAM's account and session management directives. The default behavior is to use PAM for clear-text authentication only and to ignore any account or session management. Samba always -ignores PAM for authentication in the case of <a class="indexterm" name="id431795"></a>encrypt passwords = yes. +ignores PAM for authentication in the case of <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS">encrypt passwords = yes</a>. The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB password encryption. -</p><p>Default: <a class="indexterm" name="id431807"></a>obey pam restrictions = no</p></blockquote></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id431817"></a>Remote CIFS Authentication Using <code class="filename">winbindd.so</code></h3></div></div></div><p> +</p><p>Default: <a class="link" href="smb.conf.5.html#OBEYPAMRESTRICTIONS">obey pam restrictions = no</a></p></blockquote></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689563"></a>Remote CIFS Authentication Using <code class="filename">winbindd.so</code></h3></div></div></div><p> All operating systems depend on the provision of user credentials acceptable to the platform. UNIX requires the provision of a user identifier (UID) as well as a group identifier (GID). These are both simple integer numbers that are obtained from a password backend such @@ -484,7 +484,7 @@ enumeration command. The allocated UNIX IDs are stored in a database file under lock directory and will be remembered. </p><p> The astute administrator will realize from this that the combination of <code class="filename">pam_smbpass.so</code>, -<code class="literal">winbindd</code>, and a distributed <a class="indexterm" name="id431866"></a>passdb backend +<code class="literal">winbindd</code>, and a distributed <a class="link" href="smb.conf.5.html#PASSDBBACKEND">passdb backend</a> such as <em class="parameter"><code>ldap</code></em> will allow the establishment of a centrally managed, distributed user/password database that can also be used by all PAM-aware (e.g., Linux) programs and applications. This arrangement can have particularly potent advantages compared with the use of Microsoft Active Directory Service (ADS) insofar as @@ -493,7 +493,7 @@ the reduction of wide-area network authentication traffic. The RID to UNIX ID database is the only location where the user and group mappings are stored by <code class="literal">winbindd</code>. If this file is deleted or corrupted, there is no way for <code class="literal">winbindd</code> to determine which user and group IDs correspond to Windows NT user and group RIDs. -</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id431902"></a>Password Synchronization Using <code class="filename">pam_smbpass.so</code></h3></div></div></div><p> +</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2689671"></a>Password Synchronization Using <code class="filename">pam_smbpass.so</code></h3></div></div></div><p> <code class="filename">pam_smbpass</code> is a PAM module that can be used on conforming systems to keep the <code class="filename">smbpasswd</code> (Samba password) database in sync with the UNIX password file. PAM is an API supported @@ -505,13 +505,13 @@ support for authenticating against a remote SMB server, or if you are concerned about the presence of SUID root binaries on your system, it is recommended that you use <code class="filename">pam_winbind</code> instead. </p><p> -Options recognized by this module are shown in <a href="pam.html#smbpassoptions" title="Table 28.1. Options recognized by pam_smbpass">next table</a>. +Options recognized by this module are shown in <a class="link" href="pam.html#smbpassoptions" title="Table 28.1. Options recognized by pam_smbpass">next table</a>. </p><div class="table"><a name="smbpassoptions"></a><p class="title"><b>Table 28.1. Options recognized by <em class="parameter"><code>pam_smbpass</code></em></b></p><div class="table-contents"><table summary="Options recognized by pam_smbpass" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left">debug</td><td align="justify">Log more debugging info.</td></tr><tr><td align="left">audit</td><td align="justify">Like debug, but also logs unknown usernames.</td></tr><tr><td align="left">use_first_pass</td><td align="justify">Do not prompt the user for passwords; take them from PAM_ items instead.</td></tr><tr><td align="left">try_first_pass</td><td align="justify">Try to get the password from a previous PAM module; fall back to prompting the user.</td></tr><tr><td align="left">use_authtok</td><td align="justify">Like try_first_pass, but *fail* if the new PAM_AUTHTOK has not been previously set (intended for stacking password modules only).</td></tr><tr><td align="left">not_set_pass</td><td align="justify">Do not make passwords used by this module available to other modules.</td></tr><tr><td align="left">nodelay</td><td align="justify">dDo not insert ~1-second delays on authentication failure.</td></tr><tr><td align="left">nullok</td><td align="justify">Null passwords are allowed.</td></tr><tr><td align="left">nonull</td><td align="justify">Null passwords are not allowed. Used to override the Samba configuration.</td></tr><tr><td align="left">migrate</td><td align="justify">Only meaningful in an “<span class="quote">auth</span>” context; used to update smbpasswd file with a password used for successful authentication.</td></tr><tr><td align="left">smbconf=<em class="replaceable"><code>file</code></em></td><td align="justify">Specify an alternate path to the <code class="filename">smb.conf</code> file.</td></tr></tbody></table></div></div><p><br class="table-break"> </p><p> The following are examples of the use of <code class="filename">pam_smbpass.so</code> in the format of the Linux <code class="filename">/etc/pam.d/</code> files structure. Those wishing to implement this tool on other platforms will need to adapt this appropriately. -</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id432107"></a>Password Synchronization Configuration</h4></div></div></div><p> +</p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2689889"></a>Password Synchronization Configuration</h4></div></div></div><p> The following is a sample PAM configuration that shows the use of pam_smbpass to make sure <code class="filename">private/smbpasswd</code> is kept in sync when <code class="filename">/etc/passwd (/etc/shadow)</code> is changed. It is useful when an expired password might be changed by an @@ -528,7 +528,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password required pam_smbpass.so nullok use_authtok try_first_pass session required pam_unix.so -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id432147"></a>Password Migration Configuration</h4></div></div></div><p> +</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2689935"></a>Password Migration Configuration</h4></div></div></div><p> The following PAM configuration shows the use of <code class="filename">pam_smbpass</code> to migrate from plaintext to encrypted passwords for Samba. Unlike other methods, this can be used for users who have never connected to Samba shares: @@ -548,7 +548,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password optional pam_smbpass.so nullok use_authtok try_first_pass session required pam_unix.so -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id432188"></a>Mature Password Configuration</h4></div></div></div><p> +</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2689983"></a>Mature Password Configuration</h4></div></div></div><p> The following is a sample PAM configuration for a mature <code class="filename">smbpasswd</code> installation. <code class="filename">private/smbpasswd</code> is fully populated, and we consider it an error if the SMB password does not exist or does not match the UNIX password. @@ -564,7 +564,7 @@ password requisite pam_cracklib.so retry=3 password requisite pam_unix.so shadow md5 use_authtok try_first_pass password required pam_smbpass.so use_authtok use_first_pass session required pam_unix.so -</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id432223"></a>Kerberos Password Integration Configuration</h4></div></div></div><p> +</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2690023"></a>Kerberos Password Integration Configuration</h4></div></div></div><p> The following is a sample PAM configuration that shows <em class="parameter"><code>pam_smbpass</code></em> used together with <em class="parameter"><code>pam_krb5</code></em>. This could be useful on a Samba PDC that is also a member of a Kerberos realm. @@ -581,10 +581,10 @@ password requisite pam_cracklib.so retry=3 password optional pam_smbpass.so nullok use_authtok try_first_pass password required pam_krb5.so use_authtok try_first_pass session required pam_krb5.so -</pre></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id432259"></a>Common Errors</h2></div></div></div><p> +</pre></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2690064"></a>Common Errors</h2></div></div></div><p> PAM can be fickle and sensitive to configuration glitches. Here we look at a few cases from the Samba mailing list. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id432269"></a>pam_winbind Problem</h3></div></div></div><p> +</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690075"></a>pam_winbind Problem</h3></div></div></div><p> A user reported, <span class="emphasis"><em>I have the following PAM configuration</em></span>: </p><p> </p><pre class="programlisting"> @@ -608,11 +608,11 @@ password required /lib/security/pam_stack.so service=system-auth <code class="filename">/etc/pam.d/system-auth</code> and copy only what you need from it into your <code class="filename">/etc/pam.d/login</code> file. Alternatively, if you want all services to use Winbind, you can put the Winbind-specific stuff in <code class="filename">/etc/pam.d/system-auth</code>. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id432358"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p> + </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2690173"></a>Winbind Is Not Resolving Users and Groups</h3></div></div></div><p> “<span class="quote"> My <code class="filename">smb.conf</code> file is correctly configured. I have specified - <a class="indexterm" name="id432374"></a>idmap uid = 12000 - and <a class="indexterm" name="id432382"></a>idmap gid = 3000-3500, + <a class="link" href="smb.conf.5.html#IDMAPUID">idmap uid = 12000</a> + and <a class="link" href="smb.conf.5.html#IDMAPGID">idmap gid = 3000-3500,</a> and <code class="literal">winbind</code> is running. When I do the following it all works fine. </span>” </p><pre class="screen"> |