diff options
Diffstat (limited to 'docs/htmldocs/Samba3-HOWTO/passdb.html')
| -rw-r--r-- | docs/htmldocs/Samba3-HOWTO/passdb.html | 1178 |
1 files changed, 589 insertions, 589 deletions
diff --git a/docs/htmldocs/Samba3-HOWTO/passdb.html b/docs/htmldocs/Samba3-HOWTO/passdb.html index ccade68a35..187df73316 100644 --- a/docs/htmldocs/Samba3-HOWTO/passdb.html +++ b/docs/htmldocs/Samba3-HOWTO/passdb.html @@ -1,18 +1,18 @@ -<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 11. Account Information Databases</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="NetworkBrowsing.html" title="Chapter 10. Network Browsing"><link rel="next" href="groupmapping.html" title="Chapter 12. Group Mapping: MS Windows and UNIX"></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 11. Account Information Databases</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetworkBrowsing.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="groupmapping.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><div><h2 class="title"><a name="passdb"></a>Chapter 11. Account Information Databases</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="orgname">The Samba Team</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">John</span> <span class="othername">H.</span> <span class="orgname">Samba Team</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">Gerald</span> <span class="othername">(Jerry)</span> <span class="orgname">Samba Team</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="orgname">Samba Team</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="orgname">Samba Team</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span> <div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Olivier (lem)</span> <span class="orgname">IDEALX</span> <span class="surname">Lemaire</span></h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>></code></p></div></div></div></div><div><p class="pubdate">May 24, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="passdb.html#id2587269">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2587306">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2587489">New Account Storage Systems</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#passdbtech">Technical Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2588057">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2588577">Mapping User Identifiers between MS Windows and UNIX</a></span></dt><dt><span class="sect2"><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589125">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2589538">LDAP Directories and Windows Computer Accounts</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#acctmgmttools">Account Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2589979">The smbpasswd Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The pdbedit Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2592519">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2592573">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592649">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2592915">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2593073">ldapsam</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id2595597">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id2595603">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id2595641">Configuration of auth methods</a></span></dt></dl></dd></dl></div><p> -<a class="indexterm" name="id2587072"></a> -<a class="indexterm" name="id2587079"></a> -<a class="indexterm" name="id2587086"></a> -<a class="indexterm" name="id2587092"></a> +<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 11. Account Information Databases</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"><link rel="home" href="index.html" title="The Official Samba 3.5.x HOWTO and Reference Guide"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="prev" href="NetworkBrowsing.html" title="Chapter 10. Network Browsing"><link rel="next" href="groupmapping.html" title="Chapter 12. Group Mapping: MS Windows and UNIX"></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 11. Account Information Databases</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="NetworkBrowsing.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="groupmapping.html">Next</a></td></tr></table><hr></div><div class="chapter" title="Chapter 11. Account Information Databases"><div class="titlepage"><div><div><h2 class="title"><a name="passdb"></a>Chapter 11. Account Information Databases</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Jelmer</span> <span class="othername">R.</span> <span class="surname">Vernooij</span></h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jelmer@samba.org">jelmer@samba.org</a>></code></p></div></div></div></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">Gerald</span> <span class="othername">(Jerry)</span> <span class="surname">Carter</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jerry@samba.org">jerry@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Jeremy</span> <span class="surname">Allison</span></h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:jra@samba.org">jra@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Guenther</span> <span class="surname">Deschner</span></h3><span class="contrib">LDAP updates</span> <div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:gd@samba.org">gd@samba.org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Olivier (lem)</span> <span class="surname">Lemaire</span></h3><div class="affiliation"><span class="orgname">IDEALX<br></span><div class="address"><p><code class="email"><<a class="email" href="mailto:olem@IDEALX.org">olem@IDEALX.org</a>></code></p></div></div></div></div><div><p class="pubdate">May 24, 2003</p></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><span class="sect1"><a href="passdb.html#id356961">Features and Benefits</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id356996">Backward Compatibility Account Storage Systems</a></span></dt><dt><span class="sect2"><a href="passdb.html#id357165">New Account Storage Systems</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#passdbtech">Technical Information</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id357700">Important Notes About Security</a></span></dt><dt><span class="sect2"><a href="passdb.html#id358180">Mapping User Identifiers between MS Windows and UNIX</a></span></dt><dt><span class="sect2"><a href="passdb.html#idmapbackend">Mapping Common UIDs/GIDs on Distributed Machines</a></span></dt><dt><span class="sect2"><a href="passdb.html#id358700">Comments Regarding LDAP</a></span></dt><dt><span class="sect2"><a href="passdb.html#id359075">LDAP Directories and Windows Computer Accounts</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#acctmgmttools">Account Management Tools</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id359487">The <code class="literal">smbpasswd</code> Tool</a></span></dt><dt><span class="sect2"><a href="passdb.html#pdbeditthing">The <code class="literal">pdbedit</code> Tool</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id361852">Password Backends</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id361898">Plaintext</a></span></dt><dt><span class="sect2"><a href="passdb.html#id361970">smbpasswd: Encrypted Password Database</a></span></dt><dt><span class="sect2"><a href="passdb.html#id362220">tdbsam</a></span></dt><dt><span class="sect2"><a href="passdb.html#id362365">ldapsam</a></span></dt></dl></dd><dt><span class="sect1"><a href="passdb.html#id364701">Common Errors</a></span></dt><dd><dl><dt><span class="sect2"><a href="passdb.html#id364707">Users Cannot Logon</a></span></dt><dt><span class="sect2"><a href="passdb.html#id364741">Configuration of <em class="parameter"><code>auth methods</code></em></a></span></dt></dl></dd></dl></div><p> +<a class="indexterm" name="id356776"></a> +<a class="indexterm" name="id356783"></a> +<a class="indexterm" name="id356790"></a> +<a class="indexterm" name="id356796"></a> Early releases of Samba-3 implemented new capability to work concurrently with multiple account backends. This capability was removed beginning with release of Samba 3.0.23. Commencing with Samba 3.0.23 it is possible to work with only one specified passwd backend. </p><p> -<a class="indexterm" name="id2587107"></a> -<a class="indexterm" name="id2587114"></a> -<a class="indexterm" name="id2587120"></a> -<a class="indexterm" name="id2587127"></a> -<a class="indexterm" name="id2587134"></a> -<a class="indexterm" name="id2587141"></a> +<a class="indexterm" name="id356809"></a> +<a class="indexterm" name="id356815"></a> +<a class="indexterm" name="id356822"></a> +<a class="indexterm" name="id356829"></a> +<a class="indexterm" name="id356836"></a> +<a class="indexterm" name="id356843"></a> The three passdb backends that are fully maintained (actively supported) by the Samba Team are: <code class="literal">smbpasswd</code> (being obsoleted), <code class="literal">tdbsam</code> (a tdb-based binary file format), and <code class="literal">ldapsam</code> (LDAP directory). Of these, only the <code class="literal">ldapsam</code> backend @@ -23,30 +23,30 @@ In a strict sense, there are three supported account storage and access systems. obsolete (smbpasswd). It is recommended to use the <code class="literal">tdbsam</code> method for all simple systems. Use <code class="literal">ldapsam</code> for larger and more complex networks. </p><p> -<a class="indexterm" name="id2587211"></a> -<a class="indexterm" name="id2587218"></a> -<a class="indexterm" name="id2587225"></a> -<a class="indexterm" name="id2587232"></a> -<a class="indexterm" name="id2587239"></a> -<a class="indexterm" name="id2587246"></a> -<a class="indexterm" name="id2587253"></a> +<a class="indexterm" name="id356908"></a> +<a class="indexterm" name="id356915"></a> +<a class="indexterm" name="id356922"></a> +<a class="indexterm" name="id356928"></a> +<a class="indexterm" name="id356935"></a> +<a class="indexterm" name="id356942"></a> +<a class="indexterm" name="id356949"></a> In a strict and literal sense, the passdb backends are account storage mechanisms (or methods) alone. The choice of terminology can be misleading, however we are stuck with this choice of wording. This chapter documents the nature of the account storage system with a focus on user and trust accounts. Trust accounts have two forms, machine trust accounts (computer accounts) and interdomain trust accounts. These are all treated as user-like entities. -</p><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2587269"></a>Features and Benefits</h2></div></div></div><p> +</p><div class="sect1" title="Features and Benefits"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id356961"></a>Features and Benefits</h2></div></div></div><p> Samba-3 provides for complete backward compatibility with Samba-2.2.x functionality as follows: -<a class="indexterm" name="id2587279"></a> -<a class="indexterm" name="id2587288"></a> -<a class="indexterm" name="id2587298"></a> -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2587306"></a>Backward Compatibility Account Storage Systems</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Plaintext</span></dt><dd><p> -<a class="indexterm" name="id2587323"></a> -<a class="indexterm" name="id2587330"></a> -<a class="indexterm" name="id2587337"></a> -<a class="indexterm" name="id2587343"></a> -<a class="indexterm" name="id2587350"></a> +<a class="indexterm" name="id356969"></a> +<a class="indexterm" name="id356978"></a> +<a class="indexterm" name="id356988"></a> +</p><div class="sect2" title="Backward Compatibility Account Storage Systems"><div class="titlepage"><div><div><h3 class="title"><a name="id356996"></a>Backward Compatibility Account Storage Systems</h3></div></div></div><div class="variablelist"><dl><dt><span class="term">Plaintext</span></dt><dd><p> +<a class="indexterm" name="id357012"></a> +<a class="indexterm" name="id357019"></a> +<a class="indexterm" name="id357026"></a> +<a class="indexterm" name="id357033"></a> +<a class="indexterm" name="id357040"></a> This isn't really a backend at all, but is listed here for simplicity. Samba can be configured to pass plaintext authentication requests to the traditional UNIX/Linux <code class="filename">/etc/passwd</code> and <code class="filename">/etc/shadow</code>-style subsystems. On systems that have Pluggable Authentication Modules @@ -54,10 +54,10 @@ as follows: protocol limitations imposed by MS Windows clients apply likewise. Please refer to <a class="link" href="passdb.html#passdbtech" title="Technical Information">Technical Information</a>, for more information regarding the limitations of plaintext password usage. </p></dd><dt><span class="term">smbpasswd</span></dt><dd><p> -<a class="indexterm" name="id2587397"></a> -<a class="indexterm" name="id2587404"></a> -<a class="indexterm" name="id2587411"></a> -<a class="indexterm" name="id2587418"></a> +<a class="indexterm" name="id357082"></a> +<a class="indexterm" name="id357089"></a> +<a class="indexterm" name="id357096"></a> +<a class="indexterm" name="id357103"></a> This option allows continued use of the <code class="filename">smbpasswd</code> file that maintains a plain ASCII (text) layout that includes the MS Windows LanMan and NT-encrypted passwords as well as a field that stores some @@ -69,32 +69,32 @@ as follows: This backend should be used only for backward compatibility with older versions of Samba. It may be deprecated in future releases. </p></dd><dt><span class="term">ldapsam_compat (Samba-2.2 LDAP Compatibility)</span></dt><dd><p> -<a class="indexterm" name="id2587457"></a> -<a class="indexterm" name="id2587464"></a> -<a class="indexterm" name="id2587471"></a> +<a class="indexterm" name="id357136"></a> +<a class="indexterm" name="id357143"></a> +<a class="indexterm" name="id357150"></a> There is a password backend option that allows continued operation with an existing OpenLDAP backend that uses the Samba-2.2.x LDAP schema extension. This option is provided primarily as a migration tool, although there is no reason to force migration at this time. This tool will eventually be deprecated. - </p></dd></dl></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2587489"></a>New Account Storage Systems</h3></div></div></div><p> + </p></dd></dl></div></div><div class="sect2" title="New Account Storage Systems"><div class="titlepage"><div><div><h3 class="title"><a name="id357165"></a>New Account Storage Systems</h3></div></div></div><p> Samba-3 introduces a number of new password backend capabilities. -<a class="indexterm" name="id2587498"></a> -<a class="indexterm" name="id2587507"></a> +<a class="indexterm" name="id357173"></a> +<a class="indexterm" name="id357182"></a> </p><div class="variablelist"><dl><dt><span class="term">tdbsam</span></dt><dd><p> -<a class="indexterm" name="id2587528"></a> -<a class="indexterm" name="id2587536"></a> -<a class="indexterm" name="id2587542"></a> +<a class="indexterm" name="id357204"></a> +<a class="indexterm" name="id357210"></a> +<a class="indexterm" name="id357217"></a> This backend provides a rich database backend for local servers. This backend is not suitable for multiple domain controllers (i.e., PDC + one or more BDC) installations. </p><p> -<a class="indexterm" name="id2587555"></a> -<a class="indexterm" name="id2587562"></a> -<a class="indexterm" name="id2587569"></a> -<a class="indexterm" name="id2587576"></a> -<a class="indexterm" name="id2587583"></a> -<a class="indexterm" name="id2587590"></a> +<a class="indexterm" name="id357228"></a> +<a class="indexterm" name="id357235"></a> +<a class="indexterm" name="id357242"></a> +<a class="indexterm" name="id357249"></a> +<a class="indexterm" name="id357256"></a> +<a class="indexterm" name="id357263"></a> The <span class="emphasis"><em>tdbsam</em></span> password backend stores the old <span class="emphasis"><em> smbpasswd</em></span> information plus the extended MS Windows NT/200x SAM information into a binary format TDB (trivial database) file. @@ -102,63 +102,63 @@ Samba-3 introduces a number of new password backend capabilities. to implement the same account and system access controls that are possible with MS Windows NT4/200x-based systems. </p><p> -<a class="indexterm" name="id2587613"></a> -<a class="indexterm" name="id2587620"></a> -<a class="indexterm" name="id2587627"></a> +<a class="indexterm" name="id357283"></a> +<a class="indexterm" name="id357290"></a> +<a class="indexterm" name="id357297"></a> The inclusion of the <span class="emphasis"><em>tdbsam</em></span> capability is a direct response to user requests to allow simple site operation without the overhead of the complexities of running OpenLDAP. It is recommended to use this only for sites that have fewer than 250 users. For larger sites or implementations, the use of OpenLDAP or of Active Directory integration is strongly recommended. </p></dd><dt><span class="term">ldapsam</span></dt><dd><p> -<a class="indexterm" name="id2587656"></a> -<a class="indexterm" name="id2587663"></a> +<a class="indexterm" name="id357322"></a> +<a class="indexterm" name="id357329"></a> This provides a rich directory backend for distributed account installation. </p><p> -<a class="indexterm" name="id2587674"></a> -<a class="indexterm" name="id2587681"></a> -<a class="indexterm" name="id2587688"></a> -<a class="indexterm" name="id2587695"></a> -<a class="indexterm" name="id2587702"></a> +<a class="indexterm" name="id357340"></a> +<a class="indexterm" name="id357346"></a> +<a class="indexterm" name="id357353"></a> +<a class="indexterm" name="id357360"></a> +<a class="indexterm" name="id357367"></a> Samba-3 has a new and extended LDAP implementation that requires configuration of OpenLDAP with a new format Samba schema. The new format schema file is included in the <code class="filename">examples/LDAP</code> directory of the Samba distribution. </p><p> -<a class="indexterm" name="id2587724"></a> -<a class="indexterm" name="id2587731"></a> -<a class="indexterm" name="id2587738"></a> -<a class="indexterm" name="id2587745"></a> -<a class="indexterm" name="id2587752"></a> +<a class="indexterm" name="id357387"></a> +<a class="indexterm" name="id357394"></a> +<a class="indexterm" name="id357401"></a> +<a class="indexterm" name="id357408"></a> +<a class="indexterm" name="id357414"></a> The new LDAP implementation significantly expands the control abilities that were possible with prior versions of Samba. It is now possible to specify - “<span class="quote">per-user</span>” profile settings, home directories, account access controls, and + <span class="quote">“<span class="quote">per-user</span>”</span> profile settings, home directories, account access controls, and much more. Corporate sites will see that the Samba Team has listened to their requests both for capability and greater scalability. - </p></dd></dl></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="passdbtech"></a>Technical Information</h2></div></div></div><p> -<a class="indexterm" name="id2587786"></a> -<a class="indexterm" name="id2587793"></a> + </p></dd></dl></div></div></div><div class="sect1" title="Technical Information"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="passdbtech"></a>Technical Information</h2></div></div></div><p> +<a class="indexterm" name="id357446"></a> +<a class="indexterm" name="id357452"></a> Old Windows clients send plaintext passwords over the wire. Samba can check these passwords by encrypting them and comparing them to the hash stored in the UNIX user database. </p><p> -<a class="indexterm" name="id2587806"></a> -<a class="indexterm" name="id2587813"></a> -<a class="indexterm" name="id2587820"></a> -<a class="indexterm" name="id2587827"></a> +<a class="indexterm" name="id357464"></a> +<a class="indexterm" name="id357471"></a> +<a class="indexterm" name="id357478"></a> +<a class="indexterm" name="id357484"></a> Newer Windows clients send encrypted passwords (LanMan and NT hashes) instead of plaintext passwords over the wire. The newest clients will send only encrypted passwords and refuse to send plaintext passwords unless their registry is tweaked. </p><p> -<a class="indexterm" name="id2587841"></a> -<a class="indexterm" name="id2587848"></a> +<a class="indexterm" name="id357497"></a> +<a class="indexterm" name="id357504"></a> Many people ask why Samba cannot simply use the UNIX password database. Windows requires passwords that are encrypted in its own format. The UNIX passwords can't be converted to Windows-style encrypted passwords. Because of that, you can't use the standard UNIX user database, and you have to store the LanMan and NT hashes somewhere else. </p><p> -<a class="indexterm" name="id2587864"></a> -<a class="indexterm" name="id2587872"></a> -<a class="indexterm" name="id2587878"></a> -<a class="indexterm" name="id2587885"></a> +<a class="indexterm" name="id357517"></a> +<a class="indexterm" name="id357524"></a> +<a class="indexterm" name="id357530"></a> +<a class="indexterm" name="id357537"></a> In addition to differently encrypted passwords, Windows also stores certain data for each user that is not stored in a UNIX user database: for example, workstations the user may logon from, the location where the user's profile is stored, and so on. Samba retrieves and stores this @@ -166,24 +166,24 @@ Samba-3 introduces a number of new password backend capabilities. tdbsam, and plain text file. For more information, see the man page for <code class="filename">smb.conf</code> regarding the <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a> parameter. </p><div class="figure"><a name="idmap-sid2uid"></a><p class="title"><b>Figure 11.1. IDMAP: Resolution of SIDs to UIDs.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-sid2uid.png" width="216" alt="IDMAP: Resolution of SIDs to UIDs."></div></div></div><br class="figure-break"><p> - <a class="indexterm" name="id2587975"></a> -<a class="indexterm" name="id2587981"></a> -<a class="indexterm" name="id2587988"></a> + <a class="indexterm" name="id357620"></a> +<a class="indexterm" name="id357626"></a> +<a class="indexterm" name="id357633"></a> The resolution of SIDs to UIDs is fundamental to correct operation of Samba. In both cases shown, if winbindd is not running or cannot be contacted, then only local SID/UID resolution is possible. See <a class="link" href="passdb.html#idmap-sid2uid" title="Figure 11.1. IDMAP: Resolution of SIDs to UIDs.">resolution of SIDs to UIDs</a> and <a class="link" href="passdb.html#idmap-uid2sid" title="Figure 11.2. IDMAP: Resolution of UIDs to SIDs.">resolution of UIDs to SIDs</a> diagrams. - </p><div class="figure"><a name="idmap-uid2sid"></a><p class="title"><b>Figure 11.2. IDMAP: Resolution of UIDs to SIDs.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-uid2sid.png" width="270" alt="IDMAP: Resolution of UIDs to SIDs."></div></div></div><br class="figure-break"><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2588057"></a>Important Notes About Security</h3></div></div></div><p> -<a class="indexterm" name="id2588065"></a> -<a class="indexterm" name="id2588072"></a> -<a class="indexterm" name="id2588080"></a> -<a class="indexterm" name="id2588087"></a> -<a class="indexterm" name="id2588093"></a> + </p><div class="figure"><a name="idmap-uid2sid"></a><p class="title"><b>Figure 11.2. IDMAP: Resolution of UIDs to SIDs.</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/idmap-uid2sid.png" width="270" alt="IDMAP: Resolution of UIDs to SIDs."></div></div></div><br class="figure-break"><div class="sect2" title="Important Notes About Security"><div class="titlepage"><div><div><h3 class="title"><a name="id357700"></a>Important Notes About Security</h3></div></div></div><p> +<a class="indexterm" name="id357707"></a> +<a class="indexterm" name="id357714"></a> +<a class="indexterm" name="id357721"></a> +<a class="indexterm" name="id357728"></a> +<a class="indexterm" name="id357735"></a> The UNIX and SMB password encryption techniques seem similar on the surface. This similarity is, however, only skin deep. The UNIX scheme typically sends clear-text passwords over the network when logging in. This is bad. The SMB encryption scheme never sends the clear-text password over the network, but it does store the 16-byte hashed values on disk. This is also bad. Why? Because the 16 byte hashed values - are a “<span class="quote">password equivalent.</span>” You cannot derive the user's password from them, but + are a <span class="quote">“<span class="quote">password equivalent.</span>”</span> You cannot derive the user's password from them, but they could potentially be used in a modified client to gain access to a server. This would require considerable technical knowledge on behalf of the attacker but is perfectly possible. You should therefore treat the data stored in whatever passdb @@ -191,217 +191,217 @@ Samba-3 introduces a number of new password backend capabilities. passwords of all your users. Its contents must be kept secret, and the file should be protected accordingly. </p><p> -<a class="indexterm" name="id2588123"></a> -<a class="indexterm" name="id2588129"></a> -<a class="indexterm" name="id2588136"></a> +<a class="indexterm" name="id357756"></a> +<a class="indexterm" name="id357763"></a> +<a class="indexterm" name="id357770"></a> Ideally, we would like a password scheme that involves neither plaintext passwords on the network nor plaintext passwords on disk. Unfortunately, this is not available because Samba is stuck with having to be compatible with other SMB systems (Windows NT, Windows for Workgroups, Windows 9x/Me). </p><p> -<a class="indexterm" name="id2588151"></a> -<a class="indexterm" name="id2588158"></a> +<a class="indexterm" name="id357782"></a> +<a class="indexterm" name="id357789"></a> Windows NT 4.0 Service Pack 3 changed the default setting so plaintext passwords are disabled from being sent over the wire. This mandates either the use of encrypted password support or editing the Windows NT registry to re-enable plaintext passwords. </p><p> -<a class="indexterm" name="id2588173"></a> -<a class="indexterm" name="id2588180"></a> +<a class="indexterm" name="id357802"></a> +<a class="indexterm" name="id357808"></a> The following versions of Microsoft Windows do not support full domain security protocols, although they may log onto a domain environment: - </p><div class="itemizedlist"><ul type="disc"><li><p>MS DOS Network client 3.0 with the basic network redirector installed.</p></li><li><p>Windows 95 with the network redirector update installed.</p></li><li><p>Windows 98 [Second Edition].</p></li><li><p>Windows Me.</p></li></ul></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -<a class="indexterm" name="id2588218"></a> -<a class="indexterm" name="id2588225"></a> -<a class="indexterm" name="id2588232"></a> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>MS DOS Network client 3.0 with the basic network redirector installed.</p></li><li class="listitem"><p>Windows 95 with the network redirector update installed.</p></li><li class="listitem"><p>Windows 98 [Second Edition].</p></li><li class="listitem"><p>Windows Me.</p></li></ul></div><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +<a class="indexterm" name="id357844"></a> +<a class="indexterm" name="id357851"></a> +<a class="indexterm" name="id357858"></a> MS Windows XP Home does not have facilities to become a domain member, and it cannot participate in domain logons. </p></div><p> The following versions of MS Windows fully support domain security protocols. - </p><div class="itemizedlist"><ul type="disc"><li><p>Windows NT 3.5x.</p></li><li><p>Windows NT 4.0.</p></li><li><p>Windows 2000 Professional.</p></li><li><p>Windows 200x Server/Advanced Server.</p></li><li><p>Windows XP Professional.</p></li></ul></div><p> -<a class="indexterm" name="id2588277"></a> -<a class="indexterm" name="id2588284"></a> -<a class="indexterm" name="id2588291"></a> -<a class="indexterm" name="id2588298"></a> -<a class="indexterm" name="id2588305"></a> -<a class="indexterm" name="id2588312"></a> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Windows NT 3.5x.</p></li><li class="listitem"><p>Windows NT 4.0.</p></li><li class="listitem"><p>Windows 2000 Professional.</p></li><li class="listitem"><p>Windows 200x Server/Advanced Server.</p></li><li class="listitem"><p>Windows XP Professional.</p></li></ul></div><p> +<a class="indexterm" name="id357899"></a> +<a class="indexterm" name="id357906"></a> +<a class="indexterm" name="id357913"></a> +<a class="indexterm" name="id357920"></a> +<a class="indexterm" name="id357927"></a> +<a class="indexterm" name="id357934"></a> All current releases of Microsoft SMB/CIFS clients support authentication via the SMB challenge/response mechanism described here. Enabling clear-text authentication does not disable the ability of the client to participate in encrypted authentication. Instead, it allows the client to negotiate either plaintext or encrypted password handling. </p><p> -<a class="indexterm" name="id2588328"></a> -<a class="indexterm" name="id2588335"></a> -<a class="indexterm" name="id2588342"></a> -<a class="indexterm" name="id2588349"></a> -<a class="indexterm" name="id2588356"></a> +<a class="indexterm" name="id357947"></a> +<a class="indexterm" name="id357954"></a> +<a class="indexterm" name="id357960"></a> +<a class="indexterm" name="id357967"></a> +<a class="indexterm" name="id357974"></a> MS Windows clients will cache the encrypted password alone. Where plaintext passwords are re-enabled through the appropriate registry change, the plaintext password is never cached. This means that in the event that a network connections should become disconnected (broken), only the cached (encrypted) password will be sent to the resource server to effect an auto-reconnect. If the resource server does not support encrypted passwords, the auto-reconnect will fail. Use of encrypted passwords is strongly advised. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2588373"></a>Advantages of Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> -<a class="indexterm" name="id2588384"></a> -<a class="indexterm" name="id2588391"></a> -<a class="indexterm" name="id2588398"></a> + </p><div class="sect3" title="Advantages of Encrypted Passwords"><div class="titlepage"><div><div><h4 class="title"><a name="id357986"></a>Advantages of Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> +<a class="indexterm" name="id357997"></a> +<a class="indexterm" name="id358004"></a> +<a class="indexterm" name="id358011"></a> Plaintext passwords are not passed across the network. Someone using a network sniffer cannot just record passwords going to the SMB server. - </p></li><li><p> -<a class="indexterm" name="id2588412"></a> -<a class="indexterm" name="id2588419"></a> -<a class="indexterm" name="id2588425"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id358024"></a> +<a class="indexterm" name="id358030"></a> +<a class="indexterm" name="id358037"></a> Plaintext passwords are not stored anywhere in memory or on disk. - </p></li><li><p> -<a class="indexterm" name="id2588438"></a> -<a class="indexterm" name="id2588445"></a> -<a class="indexterm" name="id2588452"></a> -<a class="indexterm" name="id2588459"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id358049"></a> +<a class="indexterm" name="id358056"></a> +<a class="indexterm" name="id358063"></a> +<a class="indexterm" name="id358070"></a> Windows NT does not like talking to a server that does not support encrypted passwords. It will refuse to browse the server if the server is also in user-level security mode. It will insist on prompting the user for the password on each connection, which is very annoying. The only thing you can do to stop this is to use SMB encryption. - </p></li><li><p> -<a class="indexterm" name="id2588476"></a> -<a class="indexterm" name="id2588483"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id358084"></a> +<a class="indexterm" name="id358090"></a> Encrypted password support allows automatic share (resource) reconnects. - </p></li><li><p> -<a class="indexterm" name="id2588496"></a> -<a class="indexterm" name="id2588502"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id358102"></a> +<a class="indexterm" name="id358109"></a> Encrypted passwords are essential for PDC/BDC operation. - </p></li></ul></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2588513"></a>Advantages of Non-Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul type="disc"><li><p> -<a class="indexterm" name="id2588525"></a> + </p></li></ul></div></div><div class="sect3" title="Advantages of Non-Encrypted Passwords"><div class="titlepage"><div><div><h4 class="title"><a name="id358119"></a>Advantages of Non-Encrypted Passwords</h4></div></div></div><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> +<a class="indexterm" name="id358130"></a> Plaintext passwords are not kept on disk and are not cached in memory. - </p></li><li><p> -<a class="indexterm" name="id2588537"></a> -<a class="indexterm" name="id2588544"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id358142"></a> +<a class="indexterm" name="id358149"></a> Plaintext passwords use the same password file as other UNIX services, such as Login and FTP. - </p></li><li><p> -<a class="indexterm" name="id2588557"></a> -<a class="indexterm" name="id2588564"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id358161"></a> +<a class="indexterm" name="id358168"></a> Use of other services (such as Telnet and FTP) that send plaintext passwords over the network makes sending them for SMB not such a big deal. - </p></li></ul></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2588577"></a>Mapping User Identifiers between MS Windows and UNIX</h3></div></div></div><p> -<a class="indexterm" name="id2588586"></a> -<a class="indexterm" name="id2588592"></a> -<a class="indexterm" name="id2588599"></a> + </p></li></ul></div></div></div><div class="sect2" title="Mapping User Identifiers between MS Windows and UNIX"><div class="titlepage"><div><div><h3 class="title"><a name="id358180"></a>Mapping User Identifiers between MS Windows and UNIX</h3></div></div></div><p> +<a class="indexterm" name="id358188"></a> +<a class="indexterm" name="id358194"></a> +<a class="indexterm" name="id358201"></a> Every operation in UNIX/Linux requires a user identifier (UID), just as in MS Windows NT4/200x this requires a security identifier (SID). Samba provides two means for mapping an MS Windows user to a UNIX/Linux UID. </p><p> -<a class="indexterm" name="id2588612"></a> -<a class="indexterm" name="id2588619"></a> -<a class="indexterm" name="id2588626"></a> -<a class="indexterm" name="id2588632"></a> -<a class="indexterm" name="id2588640"></a> +<a class="indexterm" name="id358213"></a> +<a class="indexterm" name="id358220"></a> +<a class="indexterm" name="id358226"></a> +<a class="indexterm" name="id358233"></a> +<a class="indexterm" name="id358240"></a> First, all Samba SAM database accounts require a UNIX/Linux UID that the account will map to. As users are added to the account information database, Samba will call the <a class="link" href="smb.conf.5.html#ADDUSERSCRIPT" target="_top">add user script</a> interface to add the account to the Samba host OS. In essence all accounts in the local SAM require a local user account. </p><p> - <a class="indexterm" name="id2588668"></a> - <a class="indexterm" name="id2588675"></a> - <a class="indexterm" name="id2588681"></a> - <a class="indexterm" name="id2588687"></a> - <a class="indexterm" name="id2588694"></a> - <a class="indexterm" name="id2588701"></a> - <a class="indexterm" name="id2588708"></a> + <a class="indexterm" name="id358265"></a> + <a class="indexterm" name="id358271"></a> + <a class="indexterm" name="id358278"></a> + <a class="indexterm" name="id358285"></a> + <a class="indexterm" name="id358291"></a> + <a class="indexterm" name="id358298"></a> + <a class="indexterm" name="id358305"></a> The second way to map Windows SID to UNIX UID is via the <span class="emphasis"><em>idmap uid</em></span> and <span class="emphasis"><em>idmap gid</em></span> parameters in <code class="filename">smb.conf</code>. Please refer to the man page for information about these parameters. These parameters are essential when mapping users from a remote (non-member Windows client or a member of a foreign domain) SAM server. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="idmapbackend"></a>Mapping Common UIDs/GIDs on Distributed Machines</h3></div></div></div><p> -<a class="indexterm" name="id2588747"></a> -<a class="indexterm" name="id2588754"></a> -<a class="indexterm" name="id2588760"></a> -<a class="indexterm" name="id2588767"></a> -<a class="indexterm" name="id2588774"></a> -<a class="indexterm" name="id2588780"></a> + </p></div><div class="sect2" title="Mapping Common UIDs/GIDs on Distributed Machines"><div class="titlepage"><div><div><h3 class="title"><a name="idmapbackend"></a>Mapping Common UIDs/GIDs on Distributed Machines</h3></div></div></div><p> +<a class="indexterm" name="id358341"></a> +<a class="indexterm" name="id358347"></a> +<a class="indexterm" name="id358354"></a> +<a class="indexterm" name="id358360"></a> +<a class="indexterm" name="id358367"></a> +<a class="indexterm" name="id358374"></a> Samba-3 has a special facility that makes it possible to maintain identical UIDs and GIDs on all servers in a distributed network. A distributed network is one where there exists a PDC, one or more BDCs, and/or one or more domain member servers. Why is this important? This is important if files are being shared over more than one protocol (e.g., NFS) and where users are copying files across UNIX/Linux systems using tools such as <code class="literal">rsync</code>. </p><p> -<a class="indexterm" name="id2588804"></a> -<a class="indexterm" name="id2588810"></a> -<a class="indexterm" name="id2588817"></a> -<a class="indexterm" name="id2588823"></a> -<a class="indexterm" name="id2588830"></a> -<a class="indexterm" name="id2588837"></a> -<a class="indexterm" name="id2588844"></a> - <a class="indexterm" name="id2588850"></a> +<a class="indexterm" name="id358393"></a> +<a class="indexterm" name="id358400"></a> +<a class="indexterm" name="id358407"></a> +<a class="indexterm" name="id358413"></a> +<a class="indexterm" name="id358420"></a> +<a class="indexterm" name="id358427"></a> +<a class="indexterm" name="id358433"></a> + <a class="indexterm" name="id358440"></a> The special facility is enabled using a parameter called <em class="parameter"><code>idmap backend</code></em>. The default setting for this parameter is an empty string. Technically it is possible to use an LDAP-based idmap backend for UIDs and GIDs, but it makes most sense when this is done for network configurations that also use LDAP for the SAM backend. <a class="link" href="passdb.html#idmapbackendexample" title="Example 11.1. Example Configuration with the LDAP idmap Backend">Example Configuration with the LDAP idmap Backend</a> shows that configuration. - </p><a class="indexterm" name="id2588880"></a><div class="example"><a name="idmapbackendexample"></a><p class="title"><b>Example 11.1. Example Configuration with the LDAP idmap Backend</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2588913"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap-server.quenya.org:636</code></em></td></tr><tr><td># Alternatively, this could be specified as:</td></tr><tr><td><a class="indexterm" name="id2588929"></a><em class="parameter"><code>idmap backend = ldap:ldaps://ldap-server.quenya.org</code></em></td></tr></table></div></div><br class="example-break"><p> -<a class="indexterm" name="id2588945"></a> -<a class="indexterm" name="id2588952"></a> + </p><a class="indexterm" name="id358465"></a><div class="example"><a name="idmapbackendexample"></a><p class="title"><b>Example 11.1. Example Configuration with the LDAP idmap Backend</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id358496"></a><em class="parameter"><code>idmap backend = ldap:ldap://ldap-server.quenya.org:636</code></em></td></tr><tr><td># Alternatively, this could be specified as:</td></tr><tr><td><a class="indexterm" name="id358512"></a><em class="parameter"><code>idmap backend = ldap:ldaps://ldap-server.quenya.org</code></em></td></tr></table></div></div><br class="example-break"><p> +<a class="indexterm" name="id358527"></a> +<a class="indexterm" name="id358534"></a> A network administrator who wants to make significant use of LDAP backends will sooner or later be exposed to the excellent work done by PADL Software. PADL <a class="ulink" href="http://www.padl.com" target="_top">http://www.padl.com</a> have produced and released to open source an array of tools that might be of interest. These tools include: - </p><div class="itemizedlist"><ul type="disc"><li><p> -<a class="indexterm" name="id2588976"></a> -<a class="indexterm" name="id2588982"></a> -<a class="indexterm" name="id2588989"></a> -<a class="indexterm" name="id2588996"></a> -<a class="indexterm" name="id2589003"></a> -<a class="indexterm" name="id2589009"></a> -<a class="indexterm" name="id2589016"></a> -<a class="indexterm" name="id2589023"></a> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> +<a class="indexterm" name="id358555"></a> +<a class="indexterm" name="id358562"></a> +<a class="indexterm" name="id358568"></a> +<a class="indexterm" name="id358575"></a> +<a class="indexterm" name="id358582"></a> +<a class="indexterm" name="id358589"></a> +<a class="indexterm" name="id358595"></a> +<a class="indexterm" name="id358602"></a> <span class="emphasis"><em>nss_ldap:</em></span> An LDAP name service switch (NSS) module to provide native name service support for AIX, Linux, Solaris, and other operating systems. This tool can be used for centralized storage and retrieval of UIDs and GIDs. - </p></li><li><p> -<a class="indexterm" name="id2589043"></a> -<a class="indexterm" name="id2589050"></a> -<a class="indexterm" name="id2589056"></a> -<a class="indexterm" name="id2589063"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id358620"></a> +<a class="indexterm" name="id358627"></a> +<a class="indexterm" name="id358634"></a> +<a class="indexterm" name="id358640"></a> <span class="emphasis"><em>pam_ldap:</em></span> A PAM module that provides LDAP integration for UNIX/Linux system access authentication. - </p></li><li><p> -<a class="indexterm" name="id2589082"></a> -<a class="indexterm" name="id2589088"></a> -<a class="indexterm" name="id2589095"></a> -<a class="indexterm" name="id2589102"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id358658"></a> +<a class="indexterm" name="id358665"></a> +<a class="indexterm" name="id358672"></a> +<a class="indexterm" name="id358678"></a> <span class="emphasis"><em>idmap_ad:</em></span> An IDMAP backend that supports the Microsoft Services for UNIX RFC 2307 schema available from the PADL Web <a class="ulink" href="http://www.padl.com/download/xad_oss_plugins.tar.gz" target="_top">site</a>. - </p></li></ul></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589125"></a>Comments Regarding LDAP</h3></div></div></div><p> -<a class="indexterm" name="id2589133"></a> -<a class="indexterm" name="id2589143"></a> -<a class="indexterm" name="id2589150"></a> -<a class="indexterm" name="id2589156"></a> + </p></li></ul></div></div><div class="sect2" title="Comments Regarding LDAP"><div class="titlepage"><div><div><h3 class="title"><a name="id358700"></a>Comments Regarding LDAP</h3></div></div></div><p> +<a class="indexterm" name="id358708"></a> +<a class="indexterm" name="id358717"></a> +<a class="indexterm" name="id358724"></a> +<a class="indexterm" name="id358731"></a> There is much excitement and interest in LDAP directories in the information technology world today. The LDAP architecture was designed to be highly scalable. It was also designed for use across a huge number of potential areas of application encompassing a wide range of operating systems and platforms. LDAP technologies are at the heart of the current generations of Federated Identity Management (FIM) solutions that can underlie a corporate Single Sign-On (SSO) environment. </p><p> -<a class="indexterm" name="id2589174"></a> -<a class="indexterm" name="id2589181"></a> -<a class="indexterm" name="id2589188"></a> -<a class="indexterm" name="id2589194"></a> +<a class="indexterm" name="id358744"></a> +<a class="indexterm" name="id358751"></a> +<a class="indexterm" name="id358758"></a> +<a class="indexterm" name="id358765"></a> LDAP implementations have been built across a wide variety of platforms. It lies at the core of Microsoft Windows Active Directory services (ADS), Novell's eDirectory, as well as many others. Implementation of the directory services LDAP involves interaction with legacy as well as new generation applications, all of which depend on some form of authentication services. </p><p> -<a class="indexterm" name="id2589211"></a> -<a class="indexterm" name="id2589218"></a> -<a class="indexterm" name="id2589225"></a> -<a class="indexterm" name="id2589232"></a> -<a class="indexterm" name="id2589238"></a> -<a class="indexterm" name="id2589245"></a> -<a class="indexterm" name="id2589252"></a> -<a class="indexterm" name="id2589259"></a> -<a class="indexterm" name="id2589266"></a> -<a class="indexterm" name="id2589273"></a> -<a class="indexterm" name="id2589280"></a> -<a class="indexterm" name="id2589287"></a> -<a class="indexterm" name="id2589294"></a> -<a class="indexterm" name="id2589300"></a> +<a class="indexterm" name="id358778"></a> +<a class="indexterm" name="id358785"></a> +<a class="indexterm" name="id358792"></a> +<a class="indexterm" name="id358798"></a> +<a class="indexterm" name="id358805"></a> +<a class="indexterm" name="id358812"></a> +<a class="indexterm" name="id358819"></a> +<a class="indexterm" name="id358826"></a> +<a class="indexterm" name="id358832"></a> +<a class="indexterm" name="id358839"></a> +<a class="indexterm" name="id358846"></a> +<a class="indexterm" name="id358853"></a> +<a class="indexterm" name="id358860"></a> +<a class="indexterm" name="id358866"></a> UNIX services can utilize LDAP directory information for authentication and access controls through intermediate tools and utilities. The total environment that consists of the LDAP directory and the middle-ware tools and utilities makes it possible for all user access to the UNIX platform @@ -410,12 +410,12 @@ Samba-3 introduces a number of new password backend capabilities. shells, mail and messaging systems, quota controls, printing systems, DNS servers, DHCP servers, and also Samba. </p><p> -<a class="indexterm" name="id2589321"></a> -<a class="indexterm" name="id2589328"></a> -<a class="indexterm" name="id2589334"></a> -<a class="indexterm" name="id2589341"></a> -<a class="indexterm" name="id2589348"></a> -<a class="indexterm" name="id2589355"></a> +<a class="indexterm" name="id358882"></a> +<a class="indexterm" name="id358888"></a> +<a class="indexterm" name="id358895"></a> +<a class="indexterm" name="id358902"></a> +<a class="indexterm" name="id358909"></a> +<a class="indexterm" name="id358916"></a> Many sites are installing LDAP for the first time in order to provide a scalable passdb backend for Samba. Others are faced with the need to adapt an existing LDAP directory to new uses such as for the Samba SAM backend. Whatever your particular need and attraction to Samba may be, @@ -423,37 +423,37 @@ Samba-3 introduces a number of new password backend capabilities. are of a durable nature for the site. These have far-reaching implications that affect long-term information systems management costs. </p><p> -<a class="indexterm" name="id2589374"></a> -<a class="indexterm" name="id2589381"></a> +<a class="indexterm" name="id358930"></a> +<a class="indexterm" name="id358937"></a> Do not rush into an LDAP deployment. Take the time to understand how the design of the Directory Information Tree (DIT) may impact current and future site needs, as well as the ability to meet them. The way that Samba SAM information should be stored within the DIT varies from site to site and with each implementation new experience is gained. It is well understood by LDAP veterans that first implementations create awakening, second implementations of LDAP create fear, and third-generation deployments bring peace and tranquility. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2589401"></a>Caution Regarding LDAP and Samba</h4></div></div></div><p> -<a class="indexterm" name="id2589409"></a> -<a class="indexterm" name="id2589416"></a> -<a class="indexterm" name="id2589423"></a> -<a class="indexterm" name="id2589430"></a> -<a class="indexterm" name="id2589437"></a> -<a class="indexterm" name="id2589444"></a> -<a class="indexterm" name="id2589451"></a> + </p><div class="sect3" title="Caution Regarding LDAP and Samba"><div class="titlepage"><div><div><h4 class="title"><a name="id358952"></a>Caution Regarding LDAP and Samba</h4></div></div></div><p> +<a class="indexterm" name="id358960"></a> +<a class="indexterm" name="id358967"></a> +<a class="indexterm" name="id358974"></a> +<a class="indexterm" name="id358980"></a> +<a class="indexterm" name="id358987"></a> +<a class="indexterm" name="id358994"></a> +<a class="indexterm" name="id359001"></a> Samba requires UNIX POSIX identity information as well as a place to store information that is specific to Samba and the Windows networking environment. The most used information that must be dealt with includes: user accounts, group accounts, machine trust accounts, interdomain trust accounts, and intermediate information specific to Samba internals. </p><p> -<a class="indexterm" name="id2589467"></a> -<a class="indexterm" name="id2589474"></a> -<a class="indexterm" name="id2589481"></a> +<a class="indexterm" name="id359014"></a> +<a class="indexterm" name="id359021"></a> +<a class="indexterm" name="id359028"></a> The example deployment guidelines in this book, as well as other books and HOWTO documents available from the internet may not fit with established directory designs and implementations. The existing DIT may not be able to accommodate the simple information layout proposed in common sources. Additionally, you may find that the common scripts and tools that are used to provision the LDAP directory for use with Samba may not suit your needs. </p><p> -<a class="indexterm" name="id2589499"></a> +<a class="indexterm" name="id359042"></a> It is not uncommon, for sites that have existing LDAP DITs to find necessity to generate a set of site-specific scripts and utilities to make it possible to deploy Samba within the scope of site operations. The way that user and group accounts are distributed throughout @@ -461,130 +461,130 @@ Samba-3 introduces a number of new password backend capabilities. the journey to it may be challenging. Take time to understand site needs and do not rush into deployment. </p><p> -<a class="indexterm" name="id2589517"></a> -<a class="indexterm" name="id2589524"></a> +<a class="indexterm" name="id359056"></a> +<a class="indexterm" name="id359063"></a> Above all, do not blindly use scripts and tools that are not suitable for your site. Check and validate all scripts before you execute them to make sure that the existing infrastructure will not be damaged by inadvertent use of an inappropriate tool. - </p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589538"></a>LDAP Directories and Windows Computer Accounts</h3></div></div></div><p> -<a class="indexterm" name="id2589547"></a> -<a class="indexterm" name="id2589554"></a> -<a class="indexterm" name="id2589560"></a> + </p></div></div><div class="sect2" title="LDAP Directories and Windows Computer Accounts"><div class="titlepage"><div><div><h3 class="title"><a name="id359075"></a>LDAP Directories and Windows Computer Accounts</h3></div></div></div><p> +<a class="indexterm" name="id359083"></a> +<a class="indexterm" name="id359090"></a> +<a class="indexterm" name="id359096"></a> Samba doesn't provide a turnkey solution to LDAP. It is best to deal with the design and configuration of an LDAP directory prior to integration with Samba. A working knowledge of LDAP makes Samba integration easy, and the lack of a working knowledge of LDAP can make it a frustrating experience. </p><p> -<a class="indexterm" name="id2589576"></a> -<a class="indexterm" name="id2589583"></a> -<a class="indexterm" name="id2589590"></a> +<a class="indexterm" name="id359109"></a> +<a class="indexterm" name="id359116"></a> +<a class="indexterm" name="id359123"></a> Computer (machine) accounts can be placed wherever you like in an LDAP directory subject to some constraints that are described in this chapter. </p><p> -<a class="indexterm" name="id2589603"></a> -<a class="indexterm" name="id2589609"></a> -<a class="indexterm" name="id2589616"></a> -<a class="indexterm" name="id2589623"></a> -<a class="indexterm" name="id2589630"></a> -<a class="indexterm" name="id2589637"></a> -<a class="indexterm" name="id2589644"></a> +<a class="indexterm" name="id359134"></a> +<a class="indexterm" name="id359141"></a> +<a class="indexterm" name="id359148"></a> +<a class="indexterm" name="id359155"></a> +<a class="indexterm" name="id359161"></a> +<a class="indexterm" name="id359168"></a> +<a class="indexterm" name="id359175"></a> The POSIX and sambaSamAccount components of computer (machine) accounts are both used by Samba. Thus, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats them. A user account and a machine account are indistinguishable from each other, except that the machine account ends in a $ character, as do trust accounts. </p><p> -<a class="indexterm" name="id2589660"></a> -<a class="indexterm" name="id2589667"></a> -<a class="indexterm" name="id2589674"></a> -<a class="indexterm" name="id2589681"></a> -<a class="indexterm" name="id2589688"></a> +<a class="indexterm" name="id359188"></a> +<a class="indexterm" name="id359195"></a> +<a class="indexterm" name="id359202"></a> +<a class="indexterm" name="id359208"></a> +<a class="indexterm" name="id359215"></a> The need for Windows user, group, machine, trust, and other accounts to be tied to a valid UNIX UID is a design decision that was made a long way back in the history of Samba development. It is unlikely that this decision will be reversed or changed during the remaining life of the Samba-3.x series. </p><p> -<a class="indexterm" name="id2589703"></a> -<a class="indexterm" name="id2589709"></a> -<a class="indexterm" name="id2589716"></a> +<a class="indexterm" name="id359228"></a> +<a class="indexterm" name="id359234"></a> +<a class="indexterm" name="id359241"></a> The resolution of a UID from the Windows SID is achieved within Samba through a mechanism that must refer back to the host operating system on which Samba is running. The NSS is the preferred mechanism that shields applications (like Samba) from the need to know everything about every host OS it runs on. </p><p> -<a class="indexterm" name="id2589731"></a> -<a class="indexterm" name="id2589737"></a> -<a class="indexterm" name="id2589744"></a> -<a class="indexterm" name="id2589751"></a> -<a class="indexterm" name="id2589758"></a> -<a class="indexterm" name="id2589764"></a> -<a class="indexterm" name="id2589771"></a> - Samba asks the host OS to provide a UID via the “<span class="quote">passwd</span>”, “<span class="quote">shadow</span>”, - and “<span class="quote">group</span>” facilities in the NSS control (configuration) file. The best tool +<a class="indexterm" name="id359253"></a> +<a class="indexterm" name="id359260"></a> +<a class="indexterm" name="id359267"></a> +<a class="indexterm" name="id359274"></a> +<a class="indexterm" name="id359280"></a> +<a class="indexterm" name="id359287"></a> +<a class="indexterm" name="id359294"></a> + Samba asks the host OS to provide a UID via the <span class="quote">“<span class="quote">passwd</span>”</span>, <span class="quote">“<span class="quote">shadow</span>”</span>, + and <span class="quote">“<span class="quote">group</span>”</span> facilities in the NSS control (configuration) file. The best tool for achieving this is left up to the UNIX administrator to determine. It is not imposed by Samba. Samba provides winbindd with its support libraries as one method. It is possible to do this via LDAP, and for that Samba provides the appropriate hooks so that all account entities can be located in an LDAP directory. </p><p> -<a class="indexterm" name="id2589799"></a> -<a class="indexterm" name="id2589806"></a> -<a class="indexterm" name="id2589813"></a> -<a class="indexterm" name="id2589820"></a> -<a class="indexterm" name="id2589826"></a> +<a class="indexterm" name="id359318"></a> +<a class="indexterm" name="id359325"></a> +<a class="indexterm" name="id359332"></a> +<a class="indexterm" name="id359338"></a> +<a class="indexterm" name="id359345"></a> For many the weapon of choice is to use the PADL nss_ldap utility. This utility must be configured so that computer accounts can be resolved to a POSIX/UNIX account UID. That is fundamentally an LDAP design question. The information provided on the Samba list and in the documentation is directed at providing working examples only. The design of an LDAP directory is a complex subject that is beyond the scope of this documentation. - </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="acctmgmttools"></a>Account Management Tools</h2></div></div></div><p> -<a class="indexterm" name="id2589857"></a> -<a class="indexterm" name="id2589864"></a> -<a class="indexterm" name="id2589870"></a> + </p></div></div><div class="sect1" title="Account Management Tools"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="acctmgmttools"></a>Account Management Tools</h2></div></div></div><p> +<a class="indexterm" name="id359371"></a> +<a class="indexterm" name="id359378"></a> +<a class="indexterm" name="id359385"></a> Samba provides two tools for management of user and machine accounts: <code class="literal">smbpasswd</code> and <code class="literal">pdbedit</code>. </p><p> -<a class="indexterm" name="id2589893"></a> -<a class="indexterm" name="id2589900"></a> -<a class="indexterm" name="id2589907"></a> +<a class="indexterm" name="id359407"></a> +<a class="indexterm" name="id359414"></a> +<a class="indexterm" name="id359421"></a> The <code class="literal">pdbedit</code> can be used to manage account policies in addition to Samba user account information. The policy management capability is used to administer domain default settings for password aging and management controls to handle failed login attempts. </p><p> -<a class="indexterm" name="id2589927"></a> -<a class="indexterm" name="id2589934"></a> -<a class="indexterm" name="id2589941"></a> -<a class="indexterm" name="id2589948"></a> +<a class="indexterm" name="id359439"></a> +<a class="indexterm" name="id359446"></a> +<a class="indexterm" name="id359452"></a> +<a class="indexterm" name="id359459"></a> Some people are confused when reference is made to <code class="literal">smbpasswd</code> because the name refers to a storage mechanism for SambaSAMAccount information, but it is also the name of a utility tool. That tool is destined to eventually be replaced by new functionality that is being added to the <code class="literal">net</code> toolset (see <a class="link" href="NetCommand.html" title="Chapter 13. Remote and Local Management: The Net Command">the Net Command</a>). -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2589979"></a>The <code class="literal">smbpasswd</code> Tool</h3></div></div></div><p> -<a class="indexterm" name="id2589993"></a> -<a class="indexterm" name="id2589999"></a> -<a class="indexterm" name="id2590006"></a> -<a class="indexterm" name="id2590013"></a> -<a class="indexterm" name="id2590020"></a> +</p><div class="sect2" title="The smbpasswd Tool"><div class="titlepage"><div><div><h3 class="title"><a name="id359487"></a>The <code class="literal">smbpasswd</code> Tool</h3></div></div></div><p> +<a class="indexterm" name="id359501"></a> +<a class="indexterm" name="id359508"></a> +<a class="indexterm" name="id359515"></a> +<a class="indexterm" name="id359522"></a> +<a class="indexterm" name="id359528"></a> The <code class="literal">smbpasswd</code> utility is similar to the <code class="literal">passwd</code> and <code class="literal">yppasswd</code> programs. It maintains the two 32 byte password fields in the passdb backend. This utility operates independently of the actual account and password storage methods used (as specified by the <em class="parameter"><code>passdb backend</code></em> in the <code class="filename">smb.conf</code> file). </p><p> -<a class="indexterm" name="id2590064"></a> -<a class="indexterm" name="id2590071"></a> +<a class="indexterm" name="id359570"></a> +<a class="indexterm" name="id359577"></a> <code class="literal">smbpasswd</code> works in a client-server mode where it contacts the local smbd to change the user's password on its behalf. This has enormous benefits. </p><p> -<a class="indexterm" name="id2590089"></a> -<a class="indexterm" name="id2590096"></a> +<a class="indexterm" name="id359594"></a> +<a class="indexterm" name="id359601"></a> <code class="literal">smbpasswd</code> has the capability to change passwords on Windows NT servers (this only works when the request is sent to the NT PDC if changing an NT domain user's password). </p><p> - <a class="indexterm" name="id2590115"></a> - <a class="indexterm" name="id2590122"></a> + <a class="indexterm" name="id359618"></a> + <a class="indexterm" name="id359625"></a> <code class="literal">smbpasswd</code> can be used to: - </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>add</em></span> user or machine accounts.</p></li><li><p><span class="emphasis"><em>delete</em></span> user or machine accounts.</p></li><li><p><span class="emphasis"><em>enable</em></span> user or machine accounts.</p></li><li><p><span class="emphasis"><em>disable</em></span> user or machine accounts.</p></li><li><p><span class="emphasis"><em>set to NULL</em></span> user passwords.</p></li><li><p><span class="emphasis"><em>manage</em></span> interdomain trust accounts.</p></li></ul></div><p> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="emphasis"><em>add</em></span> user or machine accounts.</p></li><li class="listitem"><p><span class="emphasis"><em>delete</em></span> user or machine accounts.</p></li><li class="listitem"><p><span class="emphasis"><em>enable</em></span> user or machine accounts.</p></li><li class="listitem"><p><span class="emphasis"><em>disable</em></span> user or machine accounts.</p></li><li class="listitem"><p><span class="emphasis"><em>set to NULL</em></span> user passwords.</p></li><li class="listitem"><p><span class="emphasis"><em>manage</em></span> interdomain trust accounts.</p></li></ul></div><p> To run smbpasswd as a normal user, just type: </p><p> </p><pre class="screen"> @@ -601,56 +601,56 @@ is being added to the <code class="literal">net</code> toolset (see <a class="li If the old value does not match the current value stored for that user, or the two new values do not match each other, then the password will not be changed. </p><p> -<a class="indexterm" name="id2590262"></a> +<a class="indexterm" name="id359761"></a> When invoked by an ordinary user, the command will allow only the user to change his or her own SMB password. </p><p> -<a class="indexterm" name="id2590274"></a> -<a class="indexterm" name="id2590281"></a> +<a class="indexterm" name="id359772"></a> +<a class="indexterm" name="id359778"></a> When run by root, <code class="literal">smbpasswd</code> may take an optional argument specifying the username whose SMB password you wish to change. When run as root, <code class="literal">smbpasswd</code> does not prompt for or check the old password value, thus allowing root to set passwords for users who have forgotten their passwords. </p><p> -<a class="indexterm" name="id2590308"></a> -<a class="indexterm" name="id2590314"></a> -<a class="indexterm" name="id2590321"></a> -<a class="indexterm" name="id2590328"></a> +<a class="indexterm" name="id359803"></a> +<a class="indexterm" name="id359809"></a> +<a class="indexterm" name="id359816"></a> +<a class="indexterm" name="id359823"></a> <code class="literal">smbpasswd</code> is designed to work in the way familiar to UNIX users who use the <code class="literal">passwd</code> or <code class="literal">yppasswd</code> commands. While designed for administrative use, this tool provides essential user-level password change capabilities. </p><p> -<a class="indexterm" name="id2590359"></a> +<a class="indexterm" name="id359852"></a> For more details on using <code class="literal">smbpasswd</code>, refer to the man page (the definitive reference). - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="pdbeditthing"></a>The <code class="literal">pdbedit</code> Tool</h3></div></div></div><p> - <a class="indexterm" name="id2590394"></a> - <a class="indexterm" name="id2590400"></a> - <a class="indexterm" name="id2590407"></a> - <a class="indexterm" name="id2590414"></a> + </p></div><div class="sect2" title="The pdbedit Tool"><div class="titlepage"><div><div><h3 class="title"><a name="pdbeditthing"></a>The <code class="literal">pdbedit</code> Tool</h3></div></div></div><p> + <a class="indexterm" name="id359885"></a> + <a class="indexterm" name="id359892"></a> + <a class="indexterm" name="id359899"></a> + <a class="indexterm" name="id359906"></a> <code class="literal">pdbedit</code> is a tool that can be used only by root. It is used to manage the passdb backend, as well as domain-wide account policy settings. <code class="literal">pdbedit</code> can be used to: - </p><div class="itemizedlist"><ul type="disc"><li><p>add, remove, or modify user accounts.</p></li><li><p>list user accounts.</p></li><li><p>migrate user accounts.</p></li><li><p>migrate group accounts.</p></li><li><p>manage account policies.</p></li><li><p>manage domain access policy settings.</p></li></ul></div><p> - <a class="indexterm" name="id2590473"></a> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>add, remove, or modify user accounts.</p></li><li class="listitem"><p>list user accounts.</p></li><li class="listitem"><p>migrate user accounts.</p></li><li class="listitem"><p>migrate group accounts.</p></li><li class="listitem"><p>manage account policies.</p></li><li class="listitem"><p>manage domain access policy settings.</p></li></ul></div><p> + <a class="indexterm" name="id359962"></a> Under the terms of the Sarbanes-Oxley Act of 2002, American businesses and organizations are mandated to implement a series of <code class="literal">internal controls</code> and procedures to communicate, store, and protect financial data. The Sarbanes-Oxley Act has far reaching implications in respect of: - </p><div class="orderedlist"><ol type="1"><li><p>Who has access to information systems that store financial data.</p></li><li><p>How personal and financial information is treated among employees and business - partners.</p></li><li><p>How security vulnerabilities are managed.</p></li><li><p>Security and patch level maintenance for all information systems.</p></li><li><p>How information systems changes are documented and tracked.</p></li><li><p>How information access controls are implemented and managed.</p></li><li><p>Auditability of all information systems in respect of change and security.</p></li><li><p>Disciplinary procedures and controls to ensure privacy.</p></li></ol></div><p> - <a class="indexterm" name="id2590546"></a> - <a class="indexterm" name="id2590552"></a> + </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Who has access to information systems that store financial data.</p></li><li class="listitem"><p>How personal and financial information is treated among employees and business + partners.</p></li><li class="listitem"><p>How security vulnerabilities are managed.</p></li><li class="listitem"><p>Security and patch level maintenance for all information systems.</p></li><li class="listitem"><p>How information systems changes are documented and tracked.</p></li><li class="listitem"><p>How information access controls are implemented and managed.</p></li><li class="listitem"><p>Auditability of all information systems in respect of change and security.</p></li><li class="listitem"><p>Disciplinary procedures and controls to ensure privacy.</p></li></ol></div><p> + <a class="indexterm" name="id360028"></a> + <a class="indexterm" name="id360034"></a> In short, the Sarbanes-Oxley Act of 2002 is an instrument that enforces accountability in respect of business related information systems so as to ensure the compliance of all information systems that are used to store personal information and particularly for financial records processing. Similar accountabilities are being demanded around the world. </p><p> - <a class="indexterm" name="id2590569"></a> - <a class="indexterm" name="id2590576"></a> - <a class="indexterm" name="id2590582"></a> - <a class="indexterm" name="id2590589"></a> - <a class="indexterm" name="id2590596"></a> + <a class="indexterm" name="id360048"></a> + <a class="indexterm" name="id360054"></a> + <a class="indexterm" name="id360061"></a> + <a class="indexterm" name="id360068"></a> + <a class="indexterm" name="id360075"></a> The need to be familiar with the Samba tools and facilities that permit information systems operation in compliance with government laws and regulations is clear to all. The <code class="literal">pdbedit</code> is currently the only Samba tool that provides the capacity to manage account and systems access controls @@ -660,27 +660,27 @@ is being added to the <code class="literal">net</code> toolset (see <a class="li Domain global policy controls available in Windows NT4 compared with Samba is shown in <a class="link" href="passdb.html#policycontrols" title="Table 11.1. NT4 Domain v's Samba Policy Controls">NT4 Domain v's Samba Policy Controls</a>. </p><div class="table"><a name="policycontrols"></a><p class="title"><b>Table 11.1. NT4 Domain v's Samba Policy Controls</b></p><div class="table-contents"><table summary="NT4 Domain v's Samba Policy Controls" border="1"><colgroup><col align="left"><col align="left"><col align="center"><col align="center"><col align="center"></colgroup><thead><tr><th align="left"><p>NT4 policy Name</p></th><th align="left"><p>Samba Policy Name</p></th><th align="center"><p>NT4 Range</p></th><th align="center"><p>Samba Range</p></th><th align="center"><p>Samba Default</p></th></tr></thead><tbody><tr><td align="left"><p>Maximum Password Age</p></td><td align="left"><p>maximum password age</p></td><td align="center"><p>0 - 999 (days)</p></td><td align="center"><p>0 - 4294967295 (sec)</p></td><td align="center"><p>4294967295</p></td></tr><tr><td align="left"><p>Minimum Password Age</p></td><td align="left"><p>minimum password age</p></td><td align="center"><p>0 - 999 (days)</p></td><td align="center"><p>0 - 4294967295 (sec)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Minimum Password Length</p></td><td align="left"><p>min password length</p></td><td align="center"><p>1 - 14 (Chars)</p></td><td align="center"><p>0 - 4294967295 (Chars)</p></td><td align="center"><p>5</p></td></tr><tr><td align="left"><p>Password Uniqueness</p></td><td align="left"><p>password history</p></td><td align="center"><p>0 - 23 (#)</p></td><td align="center"><p>0 - 4294967295 (#)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Account Lockout - Reset count after</p></td><td align="left"><p>reset count minutes</p></td><td align="center"><p>1 - 99998 (min)</p></td><td align="center"><p>0 - 4294967295 (min)</p></td><td align="center"><p>30</p></td></tr><tr><td align="left"><p>Lockout after bad logon attempts</p></td><td align="left"><p>bad lockout attempt</p></td><td align="center"><p>0 - 998 (#)</p></td><td align="center"><p>0 - 4294967295 (#)</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>*** Not Known ***</p></td><td align="left"><p>disconnect time</p></td><td align="center"><p>TBA</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>Lockout Duration</p></td><td align="left"><p>lockout duration</p></td><td align="center"><p>1 - 99998 (min)</p></td><td align="center"><p>0 - 4294967295 (min)</p></td><td align="center"><p>30</p></td></tr><tr><td align="left"><p>Users must log on in order to change password</p></td><td align="left"><p>user must logon to change password</p></td><td align="center"><p>0/1</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr><tr><td align="left"><p>*** Registry Setting ***</p></td><td align="left"><p>refuse machine password change</p></td><td align="center"><p>0/1</p></td><td align="center"><p>0 - 4294967295</p></td><td align="center"><p>0</p></td></tr></tbody></table></div></div><br class="table-break"><p> - <a class="indexterm" name="id2590979"></a> -<a class="indexterm" name="id2590986"></a> -<a class="indexterm" name="id2590993"></a> -<a class="indexterm" name="id2591000"></a> + <a class="indexterm" name="id360445"></a> +<a class="indexterm" name="id360451"></a> +<a class="indexterm" name="id360458"></a> +<a class="indexterm" name="id360465"></a> The <code class="literal">pdbedit</code> tool is the only one that can manage the account security and policy settings. It is capable of all operations that smbpasswd can do as well as a superset of them. </p><p> - <a class="indexterm" name="id2591019"></a> -<a class="indexterm" name="id2591026"></a> -<a class="indexterm" name="id2591033"></a> + <a class="indexterm" name="id360483"></a> +<a class="indexterm" name="id360489"></a> +<a class="indexterm" name="id360496"></a> One particularly important purpose of the <code class="literal">pdbedit</code> is to allow the import/export of account information from one passdb backend to another. - </p><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2591049"></a>User Account Management</h4></div></div></div><p> -<a class="indexterm" name="id2591057"></a> -<a class="indexterm" name="id2591064"></a> -<a class="indexterm" name="id2591071"></a> -<a class="indexterm" name="id2591078"></a> -<a class="indexterm" name="id2591084"></a> -<a class="indexterm" name="id2591091"></a> -<a class="indexterm" name="id2591098"></a> + </p><div class="sect3" title="User Account Management"><div class="titlepage"><div><div><h4 class="title"><a name="id360511"></a>User Account Management</h4></div></div></div><p> +<a class="indexterm" name="id360519"></a> +<a class="indexterm" name="id360526"></a> +<a class="indexterm" name="id360533"></a> +<a class="indexterm" name="id360539"></a> +<a class="indexterm" name="id360546"></a> +<a class="indexterm" name="id360553"></a> +<a class="indexterm" name="id360560"></a> The <code class="literal">pdbedit</code> tool, like the <code class="literal">smbpasswd</code> tool, requires that a POSIX user account already exists in the UNIX/Linux system accounts database (backend). Neither tool will call out to the operating system to create a user account because this is @@ -690,13 +690,13 @@ is being added to the <code class="literal">net</code> toolset (see <a class="li correctly created and changed. The use of the <code class="literal">pdbedit</code> tool does not make use of these interface scripts. </p><p> -<a class="indexterm" name="id2591142"></a> -<a class="indexterm" name="id2591149"></a> +<a class="indexterm" name="id360598"></a> +<a class="indexterm" name="id360605"></a> Before attempting to use the <code class="literal">pdbedit</code> tool to manage user and machine accounts, make certain that a system (POSIX) account has already been created. - </p><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591165"></a>Listing User and Machine Accounts</h5></div></div></div><p> -<a class="indexterm" name="id2591174"></a> -<a class="indexterm" name="id2591180"></a> + </p><div class="sect4" title="Listing User and Machine Accounts"><div class="titlepage"><div><div><h5 class="title"><a name="id360620"></a>Listing User and Machine Accounts</h5></div></div></div><p> +<a class="indexterm" name="id360628"></a> +<a class="indexterm" name="id360635"></a> The following is an example of the user account information that is stored in a tdbsam password backend. This listing was produced by running: </p><pre class="screen"> @@ -723,7 +723,7 @@ Password can change: Sat, 14 Dec 2002 14:37:03 GMT Password must change: Mon, 18 Jan 2038 20:14:07 GMT </pre><p> </p><p> -<a class="indexterm" name="id2591222"></a> +<a class="indexterm" name="id360669"></a> Accounts can also be listed in the older <code class="literal">smbpasswd</code> format: </p><pre class="screen"> <code class="prompt">root# </code><strong class="userinput"><code>pdbedit -Lw</code></strong> @@ -748,29 +748,29 @@ frodo$:1008:15891DC6B843ECA41249940C814E316B: marvel$:1011:BF709959C3C94E0B3958B7B84A3BB6F3: C610EFE9A385A3E8AA46ADFD576E6881:[W ]:LCT-40F07A4 </pre><p> -<a class="indexterm" name="id2591271"></a> -<a class="indexterm" name="id2591278"></a> -<a class="indexterm" name="id2591284"></a> -<a class="indexterm" name="id2591291"></a> -<a class="indexterm" name="id2591298"></a> -<a class="indexterm" name="id2591305"></a> +<a class="indexterm" name="id360707"></a> +<a class="indexterm" name="id360714"></a> +<a class="indexterm" name="id360721"></a> +<a class="indexterm" name="id360728"></a> +<a class="indexterm" name="id360734"></a> +<a class="indexterm" name="id360741"></a> The account information that was returned by this command in order from left to right consists of the following colon separated data: - </p><div class="itemizedlist"><ul type="disc"><li><p>Login ID.</p></li><li><p>UNIX UID.</p></li><li><p>Microsoft LanManager password hash (password converted to upper-case then hashed).</p></li><li><p>Microsoft NT password hash (hash of the case-preserved password).</p></li><li><p>Samba SAM Account Flags.</p></li><li><p>The LCT data (password last change time).</p></li></ul></div><p> -<a class="indexterm" name="id2591356"></a> -<a class="indexterm" name="id2591362"></a> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>Login ID.</p></li><li class="listitem"><p>UNIX UID.</p></li><li class="listitem"><p>Microsoft LanManager password hash (password converted to upper-case then hashed).</p></li><li class="listitem"><p>Microsoft NT password hash (hash of the case-preserved password).</p></li><li class="listitem"><p>Samba SAM Account Flags.</p></li><li class="listitem"><p>The LCT data (password last change time).</p></li></ul></div><p> +<a class="indexterm" name="id360789"></a> +<a class="indexterm" name="id360796"></a> The Account Flags parameters are documented in the <code class="literal">pdbedit</code> man page, and are briefly documented in <a class="link" href="passdb.html#TOSHARG-acctflags" title="Account Flags Management">the Account Flags Management section</a>. </p><p> -<a class="indexterm" name="id2591389"></a> +<a class="indexterm" name="id360820"></a> The LCT data consists of 8 hexadecimal characters representing the time since January 1, 1970, of the time when the password was last changed. - </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591400"></a>Adding User Accounts</h5></div></div></div><p> -<a class="indexterm" name="id2591408"></a> -<a class="indexterm" name="id2591415"></a> -<a class="indexterm" name="id2591422"></a> -<a class="indexterm" name="id2591429"></a> -<a class="indexterm" name="id2591436"></a> + </p></div><div class="sect4" title="Adding User Accounts"><div class="titlepage"><div><div><h5 class="title"><a name="id360831"></a>Adding User Accounts</h5></div></div></div><p> +<a class="indexterm" name="id360838"></a> +<a class="indexterm" name="id360845"></a> +<a class="indexterm" name="id360852"></a> +<a class="indexterm" name="id360859"></a> +<a class="indexterm" name="id360866"></a> The <code class="literal">pdbedit</code> can be used to add a user account to a standalone server or to a domain. In the example shown here the account for the user <code class="literal">vlaan</code> has been created before attempting to add the SambaSAMAccount. @@ -802,11 +802,11 @@ Last bad password : 0 Bad password count : 0 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF </pre><p> - </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591488"></a>Deleting Accounts</h5></div></div></div><p> -<a class="indexterm" name="id2591496"></a> -<a class="indexterm" name="id2591503"></a> -<a class="indexterm" name="id2591510"></a> -<a class="indexterm" name="id2591516"></a> + </p></div><div class="sect4" title="Deleting Accounts"><div class="titlepage"><div><div><h5 class="title"><a name="id360908"></a>Deleting Accounts</h5></div></div></div><p> +<a class="indexterm" name="id360915"></a> +<a class="indexterm" name="id360922"></a> +<a class="indexterm" name="id360929"></a> +<a class="indexterm" name="id360936"></a> An account can be deleted from the SambaSAMAccount database </p><pre class="screen"> <code class="prompt">root# </code> pdbedit -x vlaan @@ -814,16 +814,16 @@ Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF The account is removed without further screen output. The account is removed only from the SambaSAMAccount (passdb backend) database, it is not removed from the UNIX account backend. </p><p> -<a class="indexterm" name="id2591543"></a> -<a class="indexterm" name="id2591550"></a> +<a class="indexterm" name="id360960"></a> +<a class="indexterm" name="id360966"></a> The use of the NT4 domain user manager to delete an account will trigger the <em class="parameter"><code>delete user script</code></em>, but not the <code class="literal">pdbedit</code> tool. - </p></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2591572"></a>Changing User Accounts</h5></div></div></div><p> -<a class="indexterm" name="id2591580"></a> + </p></div><div class="sect4" title="Changing User Accounts"><div class="titlepage"><div><div><h5 class="title"><a name="id360988"></a>Changing User Accounts</h5></div></div></div><p> +<a class="indexterm" name="id360996"></a> Refer to the <code class="literal">pdbedit</code> man page for a full synopsis of all operations that are available with this tool. </p><p> -<a class="indexterm" name="id2591598"></a> +<a class="indexterm" name="id361013"></a> An example of a simple change in the user account information is the change of the full name information shown here: </p><pre class="screen"> @@ -835,9 +835,9 @@ Home Directory: \\frodo\vlaan ... </pre><p> </p><p> -<a class="indexterm" name="id2591625"></a> -<a class="indexterm" name="id2591632"></a> -<a class="indexterm" name="id2591639"></a> +<a class="indexterm" name="id361037"></a> +<a class="indexterm" name="id361044"></a> +<a class="indexterm" name="id361050"></a> Let us assume for a moment that a user's password has expired and the user is unable to change the password at this time. It may be necessary to give the user additional grace time so that it is possible to continue to work with the account and the original password. This @@ -852,8 +852,8 @@ Last bad password : Thu, 03 Jan 2002 15:08:35 GMT Bad password count : 2 ... </pre><p> -<a class="indexterm" name="id2591668"></a> -<a class="indexterm" name="id2591674"></a> +<a class="indexterm" name="id361074"></a> +<a class="indexterm" name="id361081"></a> The user has recorded 2 bad logon attempts and the next will lock the account, but the password is also expired. Here is how this account can be reset: </p><pre class="screen"> @@ -885,49 +885,49 @@ Password can change: Thu, 03 Jan 2002 15:08:35 GMT Password must change: Fri, 01 Jan 2010 00:00:00 GMT ... </pre><p> -<a class="indexterm" name="id2591738"></a> -<a class="indexterm" name="id2591745"></a> +<a class="indexterm" name="id361136"></a> +<a class="indexterm" name="id361142"></a> Refer to the strptime man page for specific time format information. </p><p> -<a class="indexterm" name="id2591757"></a> -<a class="indexterm" name="id2591763"></a> +<a class="indexterm" name="id361153"></a> +<a class="indexterm" name="id361160"></a> Please refer to the pdbedit man page for further information relating to SambaSAMAccount management. - </p><div class="sect5" lang="en"><div class="titlepage"><div><div><h6 class="title"><a name="TOSHARG-acctflags"></a>Account Flags Management</h6></div></div></div><p> -<a class="indexterm" name="id2591785"></a> -<a class="indexterm" name="id2591792"></a> -<a class="indexterm" name="id2591801"></a> -<a class="indexterm" name="id2591808"></a> + </p><div class="sect5" title="Account Flags Management"><div class="titlepage"><div><div><h6 class="title"><a name="TOSHARG-acctflags"></a>Account Flags Management</h6></div></div></div><p> +<a class="indexterm" name="id361180"></a> +<a class="indexterm" name="id361187"></a> +<a class="indexterm" name="id361196"></a> +<a class="indexterm" name="id361203"></a> The Samba SAM account flags are properly called the ACB (account control block) within the Samba source code. In some parts of the Samba source code they are referred to as the account encode_bits, and also as the account control flags. </p><p> -<a class="indexterm" name="id2591823"></a> -<a class="indexterm" name="id2591830"></a> -<a class="indexterm" name="id2591837"></a> -<a class="indexterm" name="id2591844"></a> -<a class="indexterm" name="id2591850"></a> +<a class="indexterm" name="id361215"></a> +<a class="indexterm" name="id361222"></a> +<a class="indexterm" name="id361229"></a> +<a class="indexterm" name="id361235"></a> +<a class="indexterm" name="id361242"></a> The manual adjustment of user, machine (workstation or server) or an inter-domain trust account account flgas should not be necessary under normal conditions of use of Samba. On the other hand, where this information becomes corrupted for some reason, the ability to correct the damaged data is certainly useful. The tool of choice by which such correction can be affected is the <code class="literal">pdbedit</code> utility. </p><p> -<a class="indexterm" name="id2591873"></a> -<a class="indexterm" name="id2591880"></a> +<a class="indexterm" name="id361262"></a> +<a class="indexterm" name="id361268"></a> There have been a few requests for information regarding the account flags from developers who are creating their own Samba management tools. An example of a need for information regarding the proper management of the account flags is evident when developing scripts that will be used to manage an LDAP directory. </p><p> -<a class="indexterm" name="id2591896"></a> -<a class="indexterm" name="id2591903"></a> +<a class="indexterm" name="id361281"></a> +<a class="indexterm" name="id361288"></a> The account flag field can contain up to 16 characters. Presently, only 11 are in use. These are listed in <a class="link" href="passdb.html#accountflags" title="Table 11.2. Samba SAM Account Control Block Flags">Samba SAM Account Control Block Flags</a>. The order in which the flags are specified to the <code class="literal">pdbedit</code> command is not important. In fact, they can be set without problem in any order in the SambaAcctFlags record in the LDAP directory. </p><div class="table"><a name="accountflags"></a><p class="title"><b>Table 11.2. Samba SAM Account Control Block Flags</b></p><div class="table-contents"><table summary="Samba SAM Account Control Block Flags" border="1"><colgroup><col><col></colgroup><thead><tr><th align="center">Flag</th><th align="center">Description</th></tr></thead><tbody><tr><td align="center">D</td><td align="left">Account is disabled.</td></tr><tr><td align="center">H</td><td align="left">A home directory is required.</td></tr><tr><td align="center">I</td><td align="left">An inter-domain trust account.</td></tr><tr><td align="center">L</td><td align="left">Account has been auto-locked.</td></tr><tr><td align="center">M</td><td align="left">An MNS (Microsoft network service) logon account.</td></tr><tr><td align="center">N</td><td align="left">Password not required.</td></tr><tr><td align="center">S</td><td align="left">A server trust account.</td></tr><tr><td align="center">T</td><td align="left">Temporary duplicate account entry.</td></tr><tr><td align="center">U</td><td align="left">A normal user account.</td></tr><tr><td align="center">W</td><td align="left">A workstation trust account.</td></tr><tr><td align="center">X</td><td align="left">Password does not expire.</td></tr></tbody></table></div></div><br class="table-break"><p> -<a class="indexterm" name="id2592134"></a> -<a class="indexterm" name="id2592140"></a> +<a class="indexterm" name="id361511"></a> +<a class="indexterm" name="id361518"></a> An example of use of the <code class="literal">pdbedit</code> utility to set the account control flags is shown here: </p><pre class="screen"> @@ -955,7 +955,7 @@ Last bad password : 0 Bad password count : 0 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF </pre><p> -<a class="indexterm" name="id2592196"></a> +<a class="indexterm" name="id361557"></a> The flags can be reset to the default settings by executing: </p><pre class="screen"> <code class="prompt">root# </code> pdbedit -r -c "[]" jht @@ -982,9 +982,9 @@ Last bad password : 0 Bad password count : 0 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF </pre><p> - </p></div></div><div class="sect4" lang="en"><div class="titlepage"><div><div><h5 class="title"><a name="id2592233"></a>Domain Account Policy Managment</h5></div></div></div><p> -<a class="indexterm" name="id2592241"></a> -<a class="indexterm" name="id2592248"></a> + </p></div></div><div class="sect4" title="Domain Account Policy Managment"><div class="titlepage"><div><div><h5 class="title"><a name="id361587"></a>Domain Account Policy Managment</h5></div></div></div><p> +<a class="indexterm" name="id361594"></a> +<a class="indexterm" name="id361601"></a> To view the domain account access policies that may be configured execute: </p><pre class="screen"> <code class="prompt">root# </code> pdbedit -P ? @@ -1003,7 +1003,7 @@ refuse machine password change </pre><p> </p><p> Commands will be executed to establish controls for our domain as follows: - </p><div class="orderedlist"><ol type="1"><li><p>min password length = 8 characters.</p></li><li><p>password history = last 4 passwords.</p></li><li><p>maximum password age = 90 days.</p></li><li><p>minimum password age = 7 days.</p></li><li><p>bad lockout attempt = 8 bad logon attempts.</p></li><li><p>lockout duration = forever, account must be manually reenabled.</p></li></ol></div><p> + </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>min password length = 8 characters.</p></li><li class="listitem"><p>password history = last 4 passwords.</p></li><li class="listitem"><p>maximum password age = 90 days.</p></li><li class="listitem"><p>minimum password age = 7 days.</p></li><li class="listitem"><p>bad lockout attempt = 8 bad logon attempts.</p></li><li class="listitem"><p>lockout duration = forever, account must be manually reenabled.</p></li></ol></div><p> The following command execution will achieve these settings: </p><pre class="screen"> <code class="prompt">root# </code> pdbedit -P "min password length" -C 8 @@ -1025,141 +1025,141 @@ account policy value for bad lockout attempt is now 8 account policy value for lockout duration was 30 account policy value for lockout duration is now 4294967295 </pre><p> - </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> + </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> To set the maximum (infinite) lockout time use the value of -1. -</p></div><div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> +</p></div><div class="warning" title="Warning" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Warning</h3><p> Account policies must be set individually on each PDC and BDC. At this time (Samba 3.0.11 to Samba 3.0.14a) account policies are not replicated automatically. This may be fixed before Samba 3.0.20 ships or some time there after. Please check the WHATSNEW.txt file in the Samba-3 tarball for specific update notiations regarding this facility. -</p></div></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2592394"></a>Account Import/Export</h4></div></div></div><p> - <a class="indexterm" name="id2592402"></a> -<a class="indexterm" name="id2592409"></a> -<a class="indexterm" name="id2592416"></a> +</p></div></div></div><div class="sect3" title="Account Import/Export"><div class="titlepage"><div><div><h4 class="title"><a name="id361730"></a>Account Import/Export</h4></div></div></div><p> + <a class="indexterm" name="id361738"></a> +<a class="indexterm" name="id361745"></a> +<a class="indexterm" name="id361752"></a> The <code class="literal">pdbedit</code> tool allows import/export of authentication (account) databases from one backend to another. For example, to import/export accounts from an old <code class="filename">smbpasswd</code> database to a <em class="parameter"><code>tdbsam</code></em> backend: - </p><div class="procedure"><ol type="1"><li><p> -<a class="indexterm" name="id2592453"></a> + </p><div class="procedure"><ol class="procedure" type="1"><li class="step" title="Step 1"><p> +<a class="indexterm" name="id361786"></a> </p><pre class="screen"> <code class="prompt">root# </code><strong class="userinput"><code>pdbedit -i smbpasswd -e tdbsam</code></strong> </pre><p> - </p></li><li><p> -<a class="indexterm" name="id2592483"></a> + </p></li><li class="step" title="Step 2"><p> +<a class="indexterm" name="id361816"></a> Replace the <em class="parameter"><code>smbpasswd</code></em> with <em class="parameter"><code>tdbsam</code></em> in the <em class="parameter"><code>passdb backend</code></em> configuration in <code class="filename">smb.conf</code>. - </p></li></ol></div></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2592519"></a>Password Backends</h2></div></div></div><p> -<a class="indexterm" name="id2592527"></a> -<a class="indexterm" name="id2592534"></a> + </p></li></ol></div></div></div></div><div class="sect1" title="Password Backends"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id361852"></a>Password Backends</h2></div></div></div><p> +<a class="indexterm" name="id361860"></a> +<a class="indexterm" name="id361867"></a> Samba offers flexibility in backend account database design. The flexibility is immediately obvious as one begins to explore this capability. Recent changes to Samba (since 3.0.23) have removed the mulitple backend feature in order to simplify problems that broke some installations. This removal has made the internal operation of Samba-3 more consistent and predictable. </p><p> -<a class="indexterm" name="id2592551"></a> -<a class="indexterm" name="id2592558"></a> +<a class="indexterm" name="id361880"></a> +<a class="indexterm" name="id361887"></a> Beginning with Samba 3.0.23 it is no longer possible to specify use of mulitple passdb backends. Earlier versions of Samba-3 made it possible to specify multiple password backends, and even multiple backends of the same type. The multiple passdb backend capability caused many problems with name to SID and SID to name ID resolution. The Samba team wrestled with the challenges and decided that this feature needed to be removed. -</p><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2592573"></a>Plaintext</h3></div></div></div><p> -<a class="indexterm" name="id2592581"></a> -<a class="indexterm" name="id2592588"></a> -<a class="indexterm" name="id2592595"></a> -<a class="indexterm" name="id2592602"></a> -<a class="indexterm" name="id2592609"></a> -<a class="indexterm" name="id2592615"></a> +</p><div class="sect2" title="Plaintext"><div class="titlepage"><div><div><h3 class="title"><a name="id361898"></a>Plaintext</h3></div></div></div><p> +<a class="indexterm" name="id361906"></a> +<a class="indexterm" name="id361913"></a> +<a class="indexterm" name="id361920"></a> +<a class="indexterm" name="id361926"></a> +<a class="indexterm" name="id361933"></a> +<a class="indexterm" name="id361940"></a> Older versions of Samba retrieved user information from the UNIX user database and eventually some other fields from the file <code class="filename">/etc/samba/smbpasswd</code> or <code class="filename">/etc/smbpasswd</code>. When password encryption is disabled, no SMB-specific data is stored at all. Instead, all operations are conducted via the way that the Samba host OS will access its <code class="filename">/etc/passwd</code> database. On most Linux systems, for example, all user and group resolution is done via PAM. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2592649"></a>smbpasswd: Encrypted Password Database</h3></div></div></div><p> - <a class="indexterm" name="id2592657"></a> -<a class="indexterm" name="id2592666"></a> -<a class="indexterm" name="id2592673"></a> -<a class="indexterm" name="id2592680"></a> + </p></div><div class="sect2" title="smbpasswd: Encrypted Password Database"><div class="titlepage"><div><div><h3 class="title"><a name="id361970"></a>smbpasswd: Encrypted Password Database</h3></div></div></div><p> + <a class="indexterm" name="id361978"></a> +<a class="indexterm" name="id361987"></a> +<a class="indexterm" name="id361994"></a> +<a class="indexterm" name="id362001"></a> Traditionally, when configuring <a class="link" href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = yes</a> in Samba's <code class="filename">smb.conf</code> file, user account information such as username, LM/NT password hashes, password change times, and account flags have been stored in the <code class="filename">smbpasswd(5)</code> file. There are several disadvantages to this approach for sites with large numbers of users (counted in the thousands). - </p><div class="itemizedlist"><ul type="disc"><li><p> -<a class="indexterm" name="id2592723"></a> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> +<a class="indexterm" name="id362040"></a> The first problem is that all lookups must be performed sequentially. Given that there are approximately two lookups per domain logon (one during initial logon validation and one for a session connection setup, such as when mapping a network drive or printer), this is a performance bottleneck for large sites. What is needed is an indexed approach such as that used in databases. - </p></li><li><p> -<a class="indexterm" name="id2592741"></a> -<a class="indexterm" name="id2592748"></a> -<a class="indexterm" name="id2592755"></a> -<a class="indexterm" name="id2592761"></a> -<a class="indexterm" name="id2592768"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id362054"></a> +<a class="indexterm" name="id362061"></a> +<a class="indexterm" name="id362068"></a> +<a class="indexterm" name="id362074"></a> +<a class="indexterm" name="id362081"></a> The second problem is that administrators who desire to replicate an smbpasswd file to more than one Samba server are left to use external tools such as <code class="literal">rsync(1)</code> and <code class="literal">ssh(1)</code> and write custom, in-house scripts. - </p></li><li><p> -<a class="indexterm" name="id2592794"></a> -<a class="indexterm" name="id2592800"></a> -<a class="indexterm" name="id2592807"></a> -<a class="indexterm" name="id2592814"></a> -<a class="indexterm" name="id2592821"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id362106"></a> +<a class="indexterm" name="id362113"></a> +<a class="indexterm" name="id362119"></a> +<a class="indexterm" name="id362126"></a> +<a class="indexterm" name="id362133"></a> Finally, the amount of information that is stored in an smbpasswd entry leaves no room for additional attributes such as a home directory, password expiration time, or even a relative identifier (RID). </p></li></ul></div><p> -<a class="indexterm" name="id2592838"></a> -<a class="indexterm" name="id2592845"></a> -<a class="indexterm" name="id2592852"></a> -<a class="indexterm" name="id2592859"></a> +<a class="indexterm" name="id362148"></a> +<a class="indexterm" name="id362155"></a> +<a class="indexterm" name="id362162"></a> +<a class="indexterm" name="id362169"></a> As a result of these deficiencies, a more robust means of storing user attributes used by smbd was developed. The API that defines access to user accounts is commonly referred to as the samdb interface (previously, this was called the passdb API and is still so named in the Samba source code trees). </p><p> -<a class="indexterm" name="id2592874"></a> -<a class="indexterm" name="id2592881"></a> -<a class="indexterm" name="id2592888"></a> -<a class="indexterm" name="id2592895"></a> -<a class="indexterm" name="id2592902"></a> +<a class="indexterm" name="id362181"></a> +<a class="indexterm" name="id362188"></a> +<a class="indexterm" name="id362195"></a> +<a class="indexterm" name="id362202"></a> +<a class="indexterm" name="id362209"></a> Samba provides an enhanced set of passdb backends that overcome the deficiencies of the smbpasswd plaintext database. These are tdbsam and ldapsam. Of these, ldapsam will be of most interest to large corporate or enterprise sites. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2592915"></a>tdbsam</h3></div></div></div><p> - <a class="indexterm" name="id2592923"></a> -<a class="indexterm" name="id2592932"></a> -<a class="indexterm" name="id2592941"></a> - Samba can store user and machine account data in a “<span class="quote">TDB</span>” (trivial database). + </p></div><div class="sect2" title="tdbsam"><div class="titlepage"><div><div><h3 class="title"><a name="id362220"></a>tdbsam</h3></div></div></div><p> + <a class="indexterm" name="id362228"></a> +<a class="indexterm" name="id362237"></a> +<a class="indexterm" name="id362246"></a> + Samba can store user and machine account data in a <span class="quote">“<span class="quote">TDB</span>”</span> (trivial database). Using this backend does not require any additional configuration. This backend is recommended for new installations that do not require LDAP. </p><p> -<a class="indexterm" name="id2592958"></a> -<a class="indexterm" name="id2592965"></a> -<a class="indexterm" name="id2592972"></a> -<a class="indexterm" name="id2592978"></a> +<a class="indexterm" name="id362261"></a> +<a class="indexterm" name="id362268"></a> +<a class="indexterm" name="id362274"></a> +<a class="indexterm" name="id362281"></a> As a general guide, the Samba Team does not recommend using the tdbsam backend for sites that have 250 or more users. Additionally, tdbsam is not capable of scaling for use in sites that require PDB/BDC implementations that require replication of the account database. Clearly, for reason of scalability, the use of ldapsam should be encouraged. </p><p> -<a class="indexterm" name="id2592994"></a> -<a class="indexterm" name="id2593001"></a> -<a class="indexterm" name="id2593008"></a> +<a class="indexterm" name="id362294"></a> +<a class="indexterm" name="id362301"></a> +<a class="indexterm" name="id362308"></a> The recommendation of a 250-user limit is purely based on the notion that this would generally involve a site that has routed networks, possibly spread across more than one physical location. The Samba Team has not at this time established the performance-based scalability limits of the tdbsam architecture. </p><p> -<a class="indexterm" name="id2593024"></a> -<a class="indexterm" name="id2593031"></a> -<a class="indexterm" name="id2593038"></a> -<a class="indexterm" name="id2593044"></a> +<a class="indexterm" name="id362320"></a> +<a class="indexterm" name="id362327"></a> +<a class="indexterm" name="id362334"></a> +<a class="indexterm" name="id362341"></a> There are sites that have thousands of users and yet require only one server. One site recently reported having 4,500 user accounts on one UNIX system and reported excellent performance with the <code class="literal">tdbsam</code> passdb backend. @@ -1167,60 +1167,60 @@ to be removed. is not one pertaining to a limitation in the TDB storage system, it is based only on the need for a reliable distribution mechanism for the SambaSAMAccount backend. - </p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2593073"></a>ldapsam</h3></div></div></div><p> -<a class="indexterm" name="id2593081"></a> -<a class="indexterm" name="id2593087"></a> - <a class="indexterm" name="id2593094"></a> + </p></div><div class="sect2" title="ldapsam"><div class="titlepage"><div><div><h3 class="title"><a name="id362365"></a>ldapsam</h3></div></div></div><p> +<a class="indexterm" name="id362373"></a> +<a class="indexterm" name="id362380"></a> + <a class="indexterm" name="id362387"></a> There are a few points to stress that the ldapsam does not provide. The LDAP support referred to in this documentation does not include: - </p><div class="itemizedlist"><ul type="disc"><li><p>A means of retrieving user account information from - a Windows 200x Active Directory server.</p></li><li><p>A means of replacing /etc/passwd.</p></li></ul></div><p> -<a class="indexterm" name="id2593123"></a> -<a class="indexterm" name="id2593130"></a> -<a class="indexterm" name="id2593137"></a> -<a class="indexterm" name="id2593143"></a> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p>A means of retrieving user account information from + a Windows 200x Active Directory server.</p></li><li class="listitem"><p>A means of replacing /etc/passwd.</p></li></ul></div><p> +<a class="indexterm" name="id362414"></a> +<a class="indexterm" name="id362420"></a> +<a class="indexterm" name="id362427"></a> +<a class="indexterm" name="id362433"></a> The second item can be accomplished by using LDAP NSS and PAM modules. LGPL versions of these libraries can be obtained from <a class="ulink" href="http://www.padl.com/" target="_top">PADL Software</a>. More information about the configuration of these packages may be found in <a class="ulink" href="http://safari.oreilly.com/?XmlId=1-56592-491-6" target="_top"> <span class="emphasis"><em>LDAP, System Administration</em></span> by Gerald Carter, Chapter 6, Replacing NIS"</a>. </p><p> -<a class="indexterm" name="id2593174"></a> -<a class="indexterm" name="id2593181"></a> -<a class="indexterm" name="id2593188"></a> +<a class="indexterm" name="id362460"></a> +<a class="indexterm" name="id362467"></a> +<a class="indexterm" name="id362474"></a> This document describes how to use an LDAP directory for storing Samba user account information traditionally stored in the smbpasswd(5) file. It is assumed that the reader already has a basic understanding of LDAP concepts and has a working directory server already installed. For more information on LDAP architectures and directories, please refer to the following sites: - </p><div class="itemizedlist"><ul type="disc"><li><p><a class="ulink" href="http://www.openldap.org/" target="_top">OpenLDAP</a></p></li><li><p><a class="ulink" href="http://www.sun.com/software/products/directory_srvr_ee/index.xml" target="_top"> - Sun One Directory Server</a></p></li><li><p><a class="ulink" href="http://www.novell.com/products/edirectory/" target="_top">Novell eDirectory</a></p></li><li><p><a class="ulink" href="http://www-306.ibm.com/software/tivoli/products/directory-server/" target="_top">IBM - Tivoli Directory Server</a></p></li><li><p><a class="ulink" href="http://www.redhat.com/software/rha/directory/" target="_top">Red Hat Directory - Server</a></p></li><li><p><a class="ulink" href="http://www.linuxsecurity.com/content/view/119229" target="_top">Fedora Directory + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><a class="ulink" href="http://www.openldap.org/" target="_top">OpenLDAP</a></p></li><li class="listitem"><p><a class="ulink" href="http://www.sun.com/software/products/directory_srvr_ee/index.xml" target="_top"> + Sun One Directory Server</a></p></li><li class="listitem"><p><a class="ulink" href="http://www.novell.com/products/edirectory/" target="_top">Novell eDirectory</a></p></li><li class="listitem"><p><a class="ulink" href="http://www-306.ibm.com/software/tivoli/products/directory-server/" target="_top">IBM + Tivoli Directory Server</a></p></li><li class="listitem"><p><a class="ulink" href="http://www.redhat.com/software/rha/directory/" target="_top">Red Hat Directory + Server</a></p></li><li class="listitem"><p><a class="ulink" href="http://www.linuxsecurity.com/content/view/119229" target="_top">Fedora Directory Server</a></p></li></ul></div><p> Two additional Samba resources that may prove to be helpful are: - </p><div class="itemizedlist"><ul type="disc"><li><p> -<a class="indexterm" name="id2593268"></a> + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p> +<a class="indexterm" name="id362547"></a> The <a class="ulink" href="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html" target="_top">Samba-PDC-LDAP-HOWTO</a> maintained by Ignacio Coupeau. - </p></li><li><p> -<a class="indexterm" name="id2593288"></a> -<a class="indexterm" name="id2593294"></a> -<a class="indexterm" name="id2593301"></a> + </p></li><li class="listitem"><p> +<a class="indexterm" name="id362565"></a> +<a class="indexterm" name="id362572"></a> +<a class="indexterm" name="id362578"></a> The NT migration scripts from <a class="ulink" href="http://samba.idealx.org/" target="_top">IDEALX</a> that are geared to manage users and groups in such a Samba-LDAP domain controller configuration. Idealx also produced the smbldap-tools and the Interactive Console Management tool. - </p></li></ul></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593320"></a>Supported LDAP Servers</h4></div></div></div><p> -<a class="indexterm" name="id2593328"></a> -<a class="indexterm" name="id2593335"></a> -<a class="indexterm" name="id2593342"></a> -<a class="indexterm" name="id2593349"></a> + </p></li></ul></div><div class="sect3" title="Supported LDAP Servers"><div class="titlepage"><div><div><h4 class="title"><a name="id362595"></a>Supported LDAP Servers</h4></div></div></div><p> +<a class="indexterm" name="id362603"></a> +<a class="indexterm" name="id362610"></a> +<a class="indexterm" name="id362617"></a> +<a class="indexterm" name="id362624"></a> The LDAP ldapsam code was developed and tested using the OpenLDAP 2.x server and client libraries. The same code should work with Netscape's Directory Server and client SDK. However, there are bound to be compile errors and bugs. These should not be hard to fix. Please submit fixes via the process outlined in <a class="link" href="bugreport.html" title="Chapter 40. Reporting Bugs">Reporting Bugs</a>. </p><p> Samba is capable of working with any standards-compliant LDAP server. - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593375"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div></div><p> + </p></div><div class="sect3" title="Schema and Relationship to the RFC 2307 posixAccount"><div class="titlepage"><div><div><h4 class="title"><a name="id362646"></a>Schema and Relationship to the RFC 2307 posixAccount</h4></div></div></div><p> Samba-3.0 includes the necessary schema file for OpenLDAP 2.x in the <code class="filename">examples/LDAP/samba.schema</code> directory of the source code distribution tarball. The schema entry for the sambaSamAccount ObjectClass is shown here: @@ -1236,21 +1236,21 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY sambaPrimaryGroupSID $ sambaDomainName )) </pre><p> </p><p> -<a class="indexterm" name="id2593412"></a> -<a class="indexterm" name="id2593418"></a> -<a class="indexterm" name="id2593425"></a> +<a class="indexterm" name="id362676"></a> +<a class="indexterm" name="id362682"></a> +<a class="indexterm" name="id362689"></a> The <code class="filename">samba.schema</code> file has been formatted for OpenLDAP 2.0/2.1. The Samba Team owns the OID space used by the above schema and recommends its use. If you translate the schema to be used with Netscape DS, please submit the modified schema file as a patch to <a class="ulink" href="mailto:jerry@samba.org" target="_top">jerry@samba.org</a>. </p><p> -<a class="indexterm" name="id2593452"></a> -<a class="indexterm" name="id2593459"></a> -<a class="indexterm" name="id2593466"></a> -<a class="indexterm" name="id2593473"></a> -<a class="indexterm" name="id2593480"></a> -<a class="indexterm" name="id2593486"></a> -<a class="indexterm" name="id2593493"></a> +<a class="indexterm" name="id362714"></a> +<a class="indexterm" name="id362720"></a> +<a class="indexterm" name="id362727"></a> +<a class="indexterm" name="id362734"></a> +<a class="indexterm" name="id362741"></a> +<a class="indexterm" name="id362748"></a> +<a class="indexterm" name="id362754"></a> Just as the smbpasswd file is meant to store information that provides information additional to a user's <code class="filename">/etc/passwd</code> entry, so is the sambaSamAccount object meant to supplement the UNIX user account information. A sambaSamAccount is an @@ -1259,15 +1259,15 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY for Samba account handling. However, there are several fields (e.g., uid) that overlap with the posixAccount ObjectClass outlined in RFC 2307. This is by design. </p><p> -<a class="indexterm" name="id2593522"></a> -<a class="indexterm" name="id2593529"></a> -<a class="indexterm" name="id2593536"></a> -<a class="indexterm" name="id2593543"></a> -<a class="indexterm" name="id2593550"></a> -<a class="indexterm" name="id2593556"></a> -<a class="indexterm" name="id2593563"></a> -<a class="indexterm" name="id2593570"></a> -<a class="indexterm" name="id2593577"></a> +<a class="indexterm" name="id362778"></a> +<a class="indexterm" name="id362785"></a> +<a class="indexterm" name="id362792"></a> +<a class="indexterm" name="id362799"></a> +<a class="indexterm" name="id362806"></a> +<a class="indexterm" name="id362812"></a> +<a class="indexterm" name="id362819"></a> +<a class="indexterm" name="id362826"></a> +<a class="indexterm" name="id362833"></a> In order to store all user account information (UNIX and Samba) in the directory, it is necessary to use the sambaSamAccount and posixAccount ObjectClasses in combination. However, <code class="literal">smbd</code> will still obtain the user's UNIX account @@ -1276,11 +1276,11 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY and functioning correctly. This division of information makes it possible to store all Samba account information in LDAP, but still maintain UNIX account information in NIS while the network is transitioning to a full LDAP infrastructure. - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593602"></a>OpenLDAP Configuration</h4></div></div></div><p> -<a class="indexterm" name="id2593610"></a> -<a class="indexterm" name="id2593617"></a> -<a class="indexterm" name="id2593624"></a> -<a class="indexterm" name="id2593630"></a> + </p></div><div class="sect3" title="OpenLDAP Configuration"><div class="titlepage"><div><div><h4 class="title"><a name="id362853"></a>OpenLDAP Configuration</h4></div></div></div><p> +<a class="indexterm" name="id362860"></a> +<a class="indexterm" name="id362867"></a> +<a class="indexterm" name="id362874"></a> +<a class="indexterm" name="id362881"></a> To include support for the sambaSamAccount object in an OpenLDAP directory server, first copy the samba.schema file to slapd's configuration directory. The samba.schema file can be found in the directory <code class="filename">examples/LDAP</code> @@ -1289,14 +1289,14 @@ ObjectClass (1.3.6.1.4.1.7165.2.2.6 NAME 'sambaSamAccount' SUP top AUXILIARY <code class="prompt">root# </code><strong class="userinput"><code>cp samba.schema /etc/openldap/schema/</code></strong> </pre><p> </p><p> -<a class="indexterm" name="id2593667"></a> -<a class="indexterm" name="id2593674"></a> -<a class="indexterm" name="id2593681"></a> -<a class="indexterm" name="id2593688"></a> -<a class="indexterm" name="id2593695"></a> -<a class="indexterm" name="id2593702"></a> -<a class="indexterm" name="id2593709"></a> -<a class="indexterm" name="id2593715"></a> +<a class="indexterm" name="id362915"></a> +<a class="indexterm" name="id362922"></a> +<a class="indexterm" name="id362928"></a> +<a class="indexterm" name="id362935"></a> +<a class="indexterm" name="id362942"></a> +<a class="indexterm" name="id362948"></a> +<a class="indexterm" name="id362955"></a> +<a class="indexterm" name="id362962"></a> Next, include the <code class="filename">samba.schema</code> file in <code class="filename">slapd.conf</code>. The sambaSamAccount object contains two attributes that depend on other schema files. The <em class="parameter"><code>uid</code></em> attribute is defined in <code class="filename">cosine.schema</code> and @@ -1316,10 +1316,10 @@ include /etc/openldap/schema/samba.schema .... </pre><p> </p><p> -<a class="indexterm" name="id2593783"></a> -<a class="indexterm" name="id2593790"></a> -<a class="indexterm" name="id2593797"></a> -<a class="indexterm" name="id2593804"></a> +<a class="indexterm" name="id363024"></a> +<a class="indexterm" name="id363031"></a> +<a class="indexterm" name="id363038"></a> +<a class="indexterm" name="id363044"></a> It is recommended that you maintain some indices on some of the most useful attributes, as in the following example, to speed up searches made on sambaSamAccount ObjectClasses (and possibly posixAccount and posixGroup as well): @@ -1357,11 +1357,11 @@ index default sub </p><pre class="screen"> <code class="prompt">root# </code><strong class="userinput"><code>/etc/init.d/slapd restart</code></strong> </pre><p> - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2593874"></a>Initialize the LDAP Database</h4></div></div></div><p> -<a class="indexterm" name="id2593882"></a> -<a class="indexterm" name="id2593889"></a> -<a class="indexterm" name="id2593896"></a> -<a class="indexterm" name="id2593903"></a> + </p></div><div class="sect3" title="Initialize the LDAP Database"><div class="titlepage"><div><div><h4 class="title"><a name="id363105"></a>Initialize the LDAP Database</h4></div></div></div><p> +<a class="indexterm" name="id363113"></a> +<a class="indexterm" name="id363120"></a> +<a class="indexterm" name="id363126"></a> +<a class="indexterm" name="id363133"></a> Before you can add accounts to the LDAP database, you must create the account containers that they will be stored in. The following LDIF file should be modified to match your needs (DNS entries, and so on): @@ -1423,32 +1423,32 @@ objectclass: simpleSecurityObject userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz </pre><p> </p><p> -<a class="indexterm" name="id2593945"></a> -<a class="indexterm" name="id2593952"></a> +<a class="indexterm" name="id363162"></a> +<a class="indexterm" name="id363169"></a> The userPassword shown above should be generated using <code class="literal">slappasswd</code>. </p><p> -<a class="indexterm" name="id2593969"></a> -<a class="indexterm" name="id2593976"></a> +<a class="indexterm" name="id363186"></a> +<a class="indexterm" name="id363192"></a> The following command will then load the contents of the LDIF file into the LDAP database. -<a class="indexterm" name="id2593985"></a> +<a class="indexterm" name="id363200"></a> </p><pre class="screen"> <code class="prompt">$ </code><strong class="userinput"><code>slapadd -v -l initldap.dif</code></strong> </pre><p> </p><p> Do not forget to secure your LDAP server with an adequate access control list as well as an admin password. - </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> -<a class="indexterm" name="id2594017"></a> + </p><div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> +<a class="indexterm" name="id363231"></a> Before Samba can access the LDAP server, you need to store the LDAP admin password in the Samba-3 <code class="filename">secrets.tdb</code> database by: -<a class="indexterm" name="id2594032"></a> +<a class="indexterm" name="id363245"></a> </p><pre class="screen"> <code class="prompt">root# </code><strong class="userinput"><code>smbpasswd -w <em class="replaceable"><code>secret</code></em></code></strong> </pre><p> - </p></div></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594059"></a>Configuring Samba</h4></div></div></div><p> -<a class="indexterm" name="id2594067"></a> -<a class="indexterm" name="id2594074"></a> + </p></div></div><div class="sect3" title="Configuring Samba"><div class="titlepage"><div><div><h4 class="title"><a name="id363272"></a>Configuring Samba</h4></div></div></div><p> +<a class="indexterm" name="id363280"></a> +<a class="indexterm" name="id363287"></a> The following parameters are available in <code class="filename">smb.conf</code> only if your version of Samba was built with LDAP support. Samba automatically builds with LDAP support if the LDAP libraries are found. The best method to verify that Samba was built with LDAP support is: @@ -1467,57 +1467,57 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz that includes <code class="literal">HAVE_LDAP_H</code> it is necessary to discover why the LDAP headers and libraries were not found during compilation. </p><p>LDAP-related smb.conf options include these: - </p><table class="simplelist" border="0" summary="Simple list"><tr><td><a class="indexterm" name="id2594130"></a><em class="parameter"><code>passdb backend = ldapsam:url</code></em></td></tr><tr><td><a class="indexterm" name="id2594142"></a></td></tr><tr><td><a class="indexterm" name="id2594149"></a></td></tr><tr><td><a class="indexterm" name="id2594156"></a></td></tr><tr><td><a class="indexterm" name="id2594163"></a></td></tr><tr><td><a class="indexterm" name="id2594170"></a></td></tr><tr><td><a class="indexterm" name="id2594177"></a></td></tr><tr><td><a class="indexterm" name="id2594184"></a></td></tr><tr><td><a class="indexterm" name="id2594191"></a></td></tr><tr><td><a class="indexterm" name="id2594198"></a></td></tr><tr><td><a class="indexterm" name="id2594204"></a></td></tr><tr><td><a class="indexterm" name="id2594211"></a></td></tr><tr><td><a class="indexterm" name="id2594218"></a></td></tr><tr><td><a class="indexterm" name="id2594225"></a></td></tr></table><p> + </p><table border="0" summary="Simple list" class="simplelist"><tr><td><a class="indexterm" name="id363337"></a><em class="parameter"><code>passdb backend = ldapsam:url</code></em></td></tr><tr><td><a class="indexterm" name="id363349"></a></td></tr><tr><td><a class="indexterm" name="id363356"></a></td></tr><tr><td><a class="indexterm" name="id363363"></a></td></tr><tr><td><a class="indexterm" name="id363369"></a></td></tr><tr><td><a class="indexterm" name="id363376"></a></td></tr><tr><td><a class="indexterm" name="id363383"></a></td></tr><tr><td><a class="indexterm" name="id363390"></a></td></tr><tr><td><a class="indexterm" name="id363397"></a></td></tr><tr><td><a class="indexterm" name="id363403"></a></td></tr><tr><td><a class="indexterm" name="id363410"></a></td></tr><tr><td><a class="indexterm" name="id363417"></a></td></tr><tr><td><a class="indexterm" name="id363424"></a></td></tr><tr><td><a class="indexterm" name="id363431"></a></td></tr></table><p> </p><p> These are described in the <code class="filename">smb.conf</code> man page and so are not repeated here. However, an example for use with an LDAP directory is shown in <a class="link" href="passdb.html#confldapex" title="Example 11.2. Configuration with LDAP">the Configuration with LDAP.</a> - </p><div class="example"><a name="confldapex"></a><p class="title"><b>Example 11.2. Configuration with LDAP</b></p><div class="example-contents"><table class="simplelist" border="0" summary="Simple list"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id2594277"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id2594288"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr><tr><td><a class="indexterm" name="id2594300"></a><em class="parameter"><code>netbios name = MORIA</code></em></td></tr><tr><td><a class="indexterm" name="id2594312"></a><em class="parameter"><code>workgroup = NOLDOR</code></em></td></tr><tr><td># LDAP related parameters:</td></tr><tr><td># Define the DN used when binding to the LDAP servers.</td></tr><tr><td># The password for this DN is not stored in smb.conf</td></tr><tr><td># Set it using 'smbpasswd -w secret' to store the</td></tr><tr><td># passphrase in the secrets.tdb file.</td></tr><tr><td># If the "ldap admin dn" value changes, it must be reset.</td></tr><tr><td><a class="indexterm" name="id2594348"></a><em class="parameter"><code>ldap admin dn = "cn=Manager,dc=quenya,dc=org"</code></em></td></tr><tr><td># SSL directory connections can be configured by:</td></tr><tr><td># ('off', 'start tls', or 'on' (default))</td></tr><tr><td><a class="indexterm" name="id2594369"></a><em class="parameter"><code>ldap ssl = start tls</code></em></td></tr><tr><td># syntax: passdb backend = ldapsam:ldap://server-name[:port]</td></tr><tr><td><a class="indexterm" name="id2594385"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://frodo.quenya.org</code></em></td></tr><tr><td># smbpasswd -x delete the entire dn-entry</td></tr><tr><td><a class="indexterm" name="id2594401"></a><em class="parameter"><code>ldap delete dn = no</code></em></td></tr><tr><td># The machine and user suffix are added to the base suffix</td></tr><tr><td># wrote WITHOUT quotes. NULL suffixes by default</td></tr><tr><td><a class="indexterm" name="id2594421"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id2594433"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id2594445"></a><em class="parameter"><code>ldap machine suffix = ou=Computers</code></em></td></tr><tr><td># Trust UNIX account information in LDAP</td></tr><tr><td># (see the smb.conf man page for details)</td></tr><tr><td># Specify the base DN to use when searching the directory</td></tr><tr><td><a class="indexterm" name="id2594470"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594484"></a>Accounts and Groups Management</h4></div></div></div><p> - <a class="indexterm" name="id2594492"></a> - <a class="indexterm" name="id2594499"></a> + </p><div class="example"><a name="confldapex"></a><p class="title"><b>Example 11.2. Configuration with LDAP</b></p><div class="example-contents"><table border="0" summary="Simple list" class="simplelist"><tr><td> </td></tr><tr><td><em class="parameter"><code>[global]</code></em></td></tr><tr><td><a class="indexterm" name="id363480"></a><em class="parameter"><code>security = user</code></em></td></tr><tr><td><a class="indexterm" name="id363492"></a><em class="parameter"><code>encrypt passwords = yes</code></em></td></tr><tr><td><a class="indexterm" name="id363503"></a><em class="parameter"><code>netbios name = MORIA</code></em></td></tr><tr><td><a class="indexterm" name="id363515"></a><em class="parameter"><code>workgroup = NOLDOR</code></em></td></tr><tr><td># LDAP related parameters:</td></tr><tr><td># Define the DN used when binding to the LDAP servers.</td></tr><tr><td># The password for this DN is not stored in smb.conf</td></tr><tr><td># Set it using 'smbpasswd -w secret' to store the</td></tr><tr><td># passphrase in the secrets.tdb file.</td></tr><tr><td># If the "ldap admin dn" value changes, it must be reset.</td></tr><tr><td><a class="indexterm" name="id363548"></a><em class="parameter"><code>ldap admin dn = "cn=Manager,dc=quenya,dc=org"</code></em></td></tr><tr><td># SSL directory connections can be configured by:</td></tr><tr><td># ('off', 'start tls', or 'on' (default))</td></tr><tr><td><a class="indexterm" name="id363568"></a><em class="parameter"><code>ldap ssl = start tls</code></em></td></tr><tr><td># syntax: passdb backend = ldapsam:ldap://server-name[:port]</td></tr><tr><td><a class="indexterm" name="id363583"></a><em class="parameter"><code>passdb backend = ldapsam:ldap://frodo.quenya.org</code></em></td></tr><tr><td># smbpasswd -x delete the entire dn-entry</td></tr><tr><td><a class="indexterm" name="id363598"></a><em class="parameter"><code>ldap delete dn = no</code></em></td></tr><tr><td># The machine and user suffix are added to the base suffix</td></tr><tr><td># wrote WITHOUT quotes. NULL suffixes by default</td></tr><tr><td><a class="indexterm" name="id363618"></a><em class="parameter"><code>ldap user suffix = ou=People</code></em></td></tr><tr><td><a class="indexterm" name="id363629"></a><em class="parameter"><code>ldap group suffix = ou=Groups</code></em></td></tr><tr><td><a class="indexterm" name="id363641"></a><em class="parameter"><code>ldap machine suffix = ou=Computers</code></em></td></tr><tr><td># Trust UNIX account information in LDAP</td></tr><tr><td># (see the smb.conf man page for details)</td></tr><tr><td># Specify the base DN to use when searching the directory</td></tr><tr><td><a class="indexterm" name="id363664"></a><em class="parameter"><code>ldap suffix = dc=quenya,dc=org</code></em></td></tr></table></div></div><br class="example-break"></div><div class="sect3" title="Accounts and Groups Management"><div class="titlepage"><div><div><h4 class="title"><a name="id363677"></a>Accounts and Groups Management</h4></div></div></div><p> + <a class="indexterm" name="id363685"></a> + <a class="indexterm" name="id363692"></a> Because user accounts are managed through the sambaSamAccount ObjectClass, you should modify your existing administration tools to deal with sambaSamAccount attributes. </p><p> -<a class="indexterm" name="id2594514"></a> -<a class="indexterm" name="id2594521"></a> -<a class="indexterm" name="id2594528"></a> +<a class="indexterm" name="id363706"></a> +<a class="indexterm" name="id363713"></a> +<a class="indexterm" name="id363720"></a> Machine accounts are managed with the sambaSamAccount ObjectClass, just like user accounts. However, it is up to you to store those accounts in a different tree of your LDAP namespace. You should use - “<span class="quote">ou=Groups,dc=quenya,dc=org</span>” to store groups and - “<span class="quote">ou=People,dc=quenya,dc=org</span>” to store users. Just configure your + <span class="quote">“<span class="quote">ou=Groups,dc=quenya,dc=org</span>”</span> to store groups and + <span class="quote">“<span class="quote">ou=People,dc=quenya,dc=org</span>”</span> to store users. Just configure your NSS and PAM accordingly (usually, in the <code class="filename">/etc/openldap/sldap.conf</code> configuration file). </p><p> -<a class="indexterm" name="id2594558"></a> -<a class="indexterm" name="id2594565"></a> -<a class="indexterm" name="id2594572"></a> -<a class="indexterm" name="id2594579"></a> +<a class="indexterm" name="id363746"></a> +<a class="indexterm" name="id363753"></a> +<a class="indexterm" name="id363760"></a> +<a class="indexterm" name="id363766"></a> In Samba-3, the group management system is based on POSIX groups. This means that Samba makes use of the posixGroup ObjectClass. For now, there is no NT-like group system management (global and local groups). Samba-3 knows only about <code class="constant">Domain Groups</code> and, unlike MS Windows 2000 and Active Directory, Samba-3 does not support nested groups. - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594597"></a>Security and sambaSamAccount</h4></div></div></div><p> -<a class="indexterm" name="id2594605"></a> + </p></div><div class="sect3" title="Security and sambaSamAccount"><div class="titlepage"><div><div><h4 class="title"><a name="id363782"></a>Security and sambaSamAccount</h4></div></div></div><p> +<a class="indexterm" name="id363790"></a> There are two important points to remember when discussing the security of sambaSAMAccount entries in the directory. - </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Never</em></span> retrieve the SambaLMPassword or -<a class="indexterm" name="id2594624"></a> - SambaNTPassword attribute values over an unencrypted LDAP session.</p></li><li><p><span class="emphasis"><em>Never</em></span> allow non-admin users to + </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><span class="emphasis"><em>Never</em></span> retrieve the SambaLMPassword or +<a class="indexterm" name="id363807"></a> + SambaNTPassword attribute values over an unencrypted LDAP session.</p></li><li class="listitem"><p><span class="emphasis"><em>Never</em></span> allow non-admin users to view the SambaLMPassword or SambaNTPassword attribute values.</p></li></ul></div><p> -<a class="indexterm" name="id2594645"></a> -<a class="indexterm" name="id2594651"></a> -<a class="indexterm" name="id2594658"></a> +<a class="indexterm" name="id363826"></a> +<a class="indexterm" name="id363833"></a> +<a class="indexterm" name="id363840"></a> These password hashes are clear-text equivalents and can be used to impersonate the user without deriving the original clear-text strings. For more information on the details of LM/NT password hashes, refer to <a class="link" href="passdb.html" title="Chapter 11. Account Information Databases">the Account Information Database section</a>. </p><p> -<a class="indexterm" name="id2594680"></a> -<a class="indexterm" name="id2594687"></a> -<a class="indexterm" name="id2594694"></a> -<a class="indexterm" name="id2594700"></a> +<a class="indexterm" name="id363859"></a> +<a class="indexterm" name="id363866"></a> +<a class="indexterm" name="id363872"></a> +<a class="indexterm" name="id363879"></a> To remedy the first security issue, the <a class="link" href="smb.conf.5.html#LDAPSSL" target="_top">ldap ssl</a> <code class="filename">smb.conf</code> parameter defaults to require an encrypted session (<a class="link" href="smb.conf.5.html#LDAPSSL" target="_top">ldap ssl = on</a>) using the default port of <code class="constant">636</code> when contacting the directory server. When using an OpenLDAP server, it @@ -1525,16 +1525,16 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz In either case, you are strongly encouraged to use secure communications protocols (so do not set <a class="link" href="smb.conf.5.html#LDAPSSL" target="_top">ldap ssl = off</a>). </p><p> -<a class="indexterm" name="id2594762"></a> -<a class="indexterm" name="id2594768"></a> -<a class="indexterm" name="id2594775"></a> +<a class="indexterm" name="id363935"></a> +<a class="indexterm" name="id363942"></a> +<a class="indexterm" name="id363948"></a> Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS extended operation. However, the OpenLDAP library still provides support for the older method of securing communication between clients and servers. </p><p> -<a class="indexterm" name="id2594789"></a> -<a class="indexterm" name="id2594796"></a> -<a class="indexterm" name="id2594803"></a> +<a class="indexterm" name="id363961"></a> +<a class="indexterm" name="id363968"></a> +<a class="indexterm" name="id363974"></a> The second security precaution is to prevent non-administrative users from harvesting password hashes from the directory. This can be done using the following ACL in <code class="filename">slapd.conf</code>: @@ -1545,7 +1545,7 @@ access to attrs=SambaLMPassword,SambaNTPassword by dn="cn=Samba Admin,ou=People,dc=quenya,dc=org" write by * none </pre><p> -</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2594833"></a>LDAP Special Attributes for sambaSamAccounts</h4></div></div></div><p> The sambaSamAccount ObjectClass is composed of the attributes shown in next tables: <a class="link" href="passdb.html#attribobjclPartA" title="Table 11.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A">Part A</a>, and <a class="link" href="passdb.html#attribobjclPartB" title="Table 11.4. Attributes in the sambaSamAccount ObjectClass (LDAP), Part B">Part B</a>. +</p></div><div class="sect3" title="LDAP Special Attributes for sambaSamAccounts"><div class="titlepage"><div><div><h4 class="title"><a name="id364001"></a>LDAP Special Attributes for sambaSamAccounts</h4></div></div></div><p> The sambaSamAccount ObjectClass is composed of the attributes shown in next tables: <a class="link" href="passdb.html#attribobjclPartA" title="Table 11.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A">Part A</a>, and <a class="link" href="passdb.html#attribobjclPartB" title="Table 11.4. Attributes in the sambaSamAccount ObjectClass (LDAP), Part B">Part B</a>. </p><div class="table"><a name="attribobjclPartA"></a><p class="title"><b>Table 11.3. Attributes in the sambaSamAccount ObjectClass (LDAP), Part A</b></p><div class="table-contents"><table summary="Attributes in the sambaSamAccount ObjectClass (LDAP), Part A" border="1"><colgroup><col align="left"><col align="justify"></colgroup><tbody><tr><td align="left"><code class="constant">sambaLMPassword</code></td><td align="justify">The LanMan password 16-byte hash stored as a character representation of a hexadecimal string.</td></tr><tr><td align="left"><code class="constant">sambaNTPassword</code></td><td align="justify">The NT password 16-byte hash stored as a character representation of a hexadecimal string.</td></tr><tr><td align="left"><code class="constant">sambaPwdLastSet</code></td><td align="justify">The integer time in seconds since 1970 when the @@ -1561,8 +1561,8 @@ access to attrs=SambaLMPassword,SambaNTPassword to change his password whenever he wants.</td></tr><tr><td align="left"><code class="constant">sambaPwdMustChange</code></td><td align="justify">Specifies the time (UNIX time format) when the user is forced to change his password. If this value is set to 0, the user will have to change his password at first login. If this attribute is not set, then the password will never expire.</td></tr><tr><td align="left"><code class="constant">sambaHomeDrive</code></td><td align="justify">Specifies the drive letter to which to map the - UNC path specified by sambaHomePath. The drive letter must be specified in the form “<span class="quote">X:</span>” - where X is the letter of the drive to map. Refer to the “<span class="quote">logon drive</span>” parameter in the + UNC path specified by sambaHomePath. The drive letter must be specified in the form <span class="quote">“<span class="quote">X:</span>”</span> + where X is the letter of the drive to map. Refer to the <span class="quote">“<span class="quote">logon drive</span>”</span> parameter in the smb.conf(5) man page for more information.</td></tr><tr><td align="left"><code class="constant">sambaLogonScript</code></td><td align="justify">The sambaLogonScript property specifies the path of the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path is relative to the netlogon share. Refer to the <a class="link" href="smb.conf.5.html#LOGONSCRIPT" target="_top">logon script</a> parameter in the @@ -1580,27 +1580,27 @@ access to attrs=SambaLMPassword,SambaNTPassword </td></tr><tr><td align="left"><code class="constant">sambaSID</code></td><td align="justify">The security identifier(SID) of the user. The Windows equivalent of UNIX UIDs.</td></tr><tr><td align="left"><code class="constant">sambaPrimaryGroupSID</code></td><td align="justify">The security identifier (SID) of the primary group of the user.</td></tr><tr><td align="left"><code class="constant">sambaDomainName</code></td><td align="justify">Domain the user is part of.</td></tr></tbody></table></div></div><br class="table-break"><p> -<a class="indexterm" name="id2595181"></a> -<a class="indexterm" name="id2595188"></a> +<a class="indexterm" name="id364317"></a> +<a class="indexterm" name="id364324"></a> The majority of these parameters are only used when Samba is acting as a PDC of a domain (refer to <a class="link" href="samba-pdc.html" title="Chapter 4. Domain Control">Domain Control</a>, for details on how to configure Samba as a PDC). The following four attributes are only stored with the sambaSamAccount entry if the values are non-default values: - </p><div class="itemizedlist"><a class="indexterm" name="id2595210"></a><a class="indexterm" name="id2595216"></a><a class="indexterm" name="id2595223"></a><a class="indexterm" name="id2595230"></a><ul type="disc"><li><p>sambaHomePath</p></li><li><p>sambaLogonScript</p></li><li><p>sambaProfilePath</p></li><li><p>sambaHomeDrive</p></li></ul></div><p> -<a class="indexterm" name="id2595259"></a> -<a class="indexterm" name="id2595266"></a> -<a class="indexterm" name="id2595273"></a> + </p><div class="itemizedlist"><a class="indexterm" name="id364343"></a><a class="indexterm" name="id364350"></a><a class="indexterm" name="id364357"></a><a class="indexterm" name="id364364"></a><ul class="itemizedlist" type="disc"><li class="listitem"><p>sambaHomePath</p></li><li class="listitem"><p>sambaLogonScript</p></li><li class="listitem"><p>sambaProfilePath</p></li><li class="listitem"><p>sambaHomeDrive</p></li></ul></div><p> +<a class="indexterm" name="id364392"></a> +<a class="indexterm" name="id364399"></a> +<a class="indexterm" name="id364405"></a> These attributes are only stored with the sambaSamAccount entry if the values are non-default values. For example, assume MORIA has now been configured as a PDC and that <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home = \\%L\%u</a> was defined in - its <code class="filename">smb.conf</code> file. When a user named “<span class="quote">becky</span>” logs on to the domain, + its <code class="filename">smb.conf</code> file. When a user named <span class="quote">“<span class="quote">becky</span>”</span> logs on to the domain, the <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> string is expanded to \\MORIA\becky. - If the smbHome attribute exists in the entry “<span class="quote">uid=becky,ou=People,dc=samba,dc=org</span>”, + If the smbHome attribute exists in the entry <span class="quote">“<span class="quote">uid=becky,ou=People,dc=samba,dc=org</span>”</span>, this value is used. However, if this attribute does not exist, then the value of the <a class="link" href="smb.conf.5.html#LOGONHOME" target="_top">logon home</a> parameter is used in its place. Samba will only write the attribute value to the directory entry if the value is something other than the default (e.g., <code class="filename">\\MOBY\becky</code>). - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2595346"></a>Example LDIF Entries for a sambaSamAccount</h4></div></div></div><p> + </p></div><div class="sect3" title="Example LDIF Entries for a sambaSamAccount"><div class="titlepage"><div><div><h4 class="title"><a name="id364472"></a>Example LDIF Entries for a sambaSamAccount</h4></div></div></div><p> The following is a working LDIF that demonstrates the use of the SambaSamAccount ObjectClass: </p><pre class="programlisting"> dn: uid=guest2, ou=People,dc=quenya,dc=org @@ -1645,7 +1645,7 @@ sambaPwdCanChange: 0 sambaPwdMustChange: 2147483647 sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7 </pre><p> - </p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2595394"></a>Password Synchronization</h4></div></div></div><p> + </p></div><div class="sect3" title="Password Synchronization"><div class="titlepage"><div><div><h4 class="title"><a name="id364508"></a>Password Synchronization</h4></div></div></div><p> Samba-3 and later can update the non-Samba (LDAP) password stored with an account. When using pam_ldap, this allows changing both UNIX and Windows passwords at once. </p><p>The <a class="link" href="smb.conf.5.html#LDAPPASSWDSYNC" target="_top">ldap passwd sync</a> options can have the values shown in @@ -1654,7 +1654,7 @@ sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7 and the <code class="constant">password</code> fields.</p></td></tr><tr><td align="left">no</td><td align="justify"><p>Only update <code class="constant">SambaNTPassword</code> and <code class="constant">SambaLMPassword</code>.</p></td></tr><tr><td align="left">only</td><td align="justify"><p>Only update the LDAP password and let the LDAP server worry about the other fields. This option is only available on some LDAP servers and - only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.</p></td></tr></tbody></table></div></div><br class="table-break"><p>More information can be found in the <code class="filename">smb.conf</code> man page.</p></div><div class="sect3" lang="en"><div class="titlepage"><div><div><h4 class="title"><a name="id2595546"></a>Using OpenLDAP Overlay for Password Synchronization</h4></div></div></div><p> + only when the LDAP server supports LDAP_EXOP_X_MODIFY_PASSWD.</p></td></tr></tbody></table></div></div><br class="table-break"><p>More information can be found in the <code class="filename">smb.conf</code> man page.</p></div><div class="sect3" title="Using OpenLDAP Overlay for Password Synchronization"><div class="titlepage"><div><div><h4 class="title"><a name="id364654"></a>Using OpenLDAP Overlay for Password Synchronization</h4></div></div></div><p> Howard Chu has written a special overlay called <code class="literal">smbk5pwd</code>. This tool modifies the <code class="literal">SambaNTPassword</code>, <code class="literal">SambaLMPassword</code> and <code class="literal">Heimdal</code> hashes in an OpenLDAP entry when an LDAP_EXOP_X_MODIFY_PASSWD operation is performed. @@ -1662,8 +1662,8 @@ sambaNTPassword: 878D8014606CDA29677A44EFA1353FC7 The overlay is shipped with OpenLDAP-2.3 and can be found in the <code class="filename">contrib/slapd-modules/smbk5pwd</code> subdirectory. This module can also be used with OpenLDAP-2.2. - </p></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id2595597"></a>Common Errors</h2></div></div></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2595603"></a>Users Cannot Logon</h3></div></div></div><p>“<span class="quote">I've installed Samba, but now I can't log on with my UNIX account! </span>”</p><p>Make sure your user has been added to the current Samba <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a>. - Read the <a class="link" href="passdb.html#acctmgmttools" title="Account Management Tools">Account Management Tools</a> for details.</p></div><div class="sect2" lang="en"><div class="titlepage"><div><div><h3 class="title"><a name="id2595641"></a>Configuration of <em class="parameter"><code>auth methods</code></em></h3></div></div></div><p> + </p></div></div></div><div class="sect1" title="Common Errors"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="id364701"></a>Common Errors</h2></div></div></div><div class="sect2" title="Users Cannot Logon"><div class="titlepage"><div><div><h3 class="title"><a name="id364707"></a>Users Cannot Logon</h3></div></div></div><p><span class="quote">“<span class="quote">I've installed Samba, but now I can't log on with my UNIX account! </span>”</span></p><p>Make sure your user has been added to the current Samba <a class="link" href="smb.conf.5.html#PASSDBBACKEND" target="_top">passdb backend</a>. + Read the <a class="link" href="passdb.html#acctmgmttools" title="Account Management Tools">Account Management Tools</a> for details.</p></div><div class="sect2" title="Configuration of auth methods"><div class="titlepage"><div><div><h3 class="title"><a name="id364741"></a>Configuration of <em class="parameter"><code>auth methods</code></em></h3></div></div></div><p> When explicitly setting an <a class="link" href="smb.conf.5.html#AUTHMETHODS" target="_top">auth methods</a> parameter, <em class="parameter"><code>guest</code></em> must be specified as the first entry on the line for example, <a class="link" href="smb.conf.5.html#AUTHMETHODS" target="_top">auth methods = guest sam</a>. |