diff options
Diffstat (limited to 'docs/htmldocs/Samba-HOWTO-Collection.html')
| -rw-r--r-- | docs/htmldocs/Samba-HOWTO-Collection.html | 3394 |
1 files changed, 1574 insertions, 1820 deletions
diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index c7393bc71bc..d93a4543d47 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -62,7 +62,7 @@ CLASS="TOC" ></DT ><DT >1. <A -HREF="#AEN15" +HREF="#INSTALL" >How to Install and Test SAMBA</A ></DT ><DD @@ -180,7 +180,7 @@ HREF="#AEN209" ></DD ><DT >2. <A -HREF="#AEN212" +HREF="#INTEGRATE-MS-NETWORKS" >Integrating MS Windows networks with Samba</A ></DT ><DD @@ -199,7 +199,7 @@ HREF="#AEN245" ><DL ><DT >2.2.1. <A -HREF="#AEN248" +HREF="#AEN261" ><TT CLASS="FILENAME" >/etc/hosts</TT @@ -207,7 +207,7 @@ CLASS="FILENAME" ></DT ><DT >2.2.2. <A -HREF="#AEN264" +HREF="#AEN277" ><TT CLASS="FILENAME" >/etc/resolv.conf</TT @@ -215,7 +215,7 @@ CLASS="FILENAME" ></DT ><DT >2.2.3. <A -HREF="#AEN275" +HREF="#AEN288" ><TT CLASS="FILENAME" >/etc/host.conf</TT @@ -223,7 +223,7 @@ CLASS="FILENAME" ></DT ><DT >2.2.4. <A -HREF="#AEN283" +HREF="#AEN296" ><TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -233,47 +233,47 @@ CLASS="FILENAME" ></DD ><DT >2.3. <A -HREF="#AEN295" +HREF="#AEN308" >Name resolution as used within MS Windows networking</A ></DT ><DD ><DL ><DT >2.3.1. <A -HREF="#AEN307" +HREF="#AEN320" >The NetBIOS Name Cache</A ></DT ><DT >2.3.2. <A -HREF="#AEN312" +HREF="#AEN325" >The LMHOSTS file</A ></DT ><DT >2.3.3. <A -HREF="#AEN320" +HREF="#AEN333" >HOSTS file</A ></DT ><DT >2.3.4. <A -HREF="#AEN325" +HREF="#AEN338" >DNS Lookup</A ></DT ><DT >2.3.5. <A -HREF="#AEN328" +HREF="#AEN341" >WINS Lookup</A ></DT ></DL ></DD ><DT >2.4. <A -HREF="#AEN342" +HREF="#AEN353" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT >2.5. <A -HREF="#AEN352" +HREF="#AEN363" >MS Windows security options and how to configure Samba for seemless integration</A ></DT @@ -281,29 +281,29 @@ Samba for seemless integration</A ><DL ><DT >2.5.1. <A -HREF="#AEN369" +HREF="#AEN391" >Use MS Windows NT as an authentication server</A ></DT ><DT >2.5.2. <A -HREF="#AEN377" +HREF="#AEN399" >Make Samba a member of an MS Windows NT security domain</A ></DT ><DT >2.5.3. <A -HREF="#AEN391" +HREF="#AEN416" >Configure Samba as an authentication server</A ></DT ><DD ><DL ><DT >2.5.3.1. <A -HREF="#AEN398" +HREF="#AEN423" >Users</A ></DT ><DT >2.5.3.2. <A -HREF="#AEN405" +HREF="#AEN428" >MS Windows NT Machine Accounts</A ></DT ></DL @@ -312,168 +312,198 @@ HREF="#AEN405" ></DD ><DT >2.6. <A -HREF="#AEN410" ->Configuration of Samba as ...</A +HREF="#AEN433" +>Conclusions</A ></DT ></DL ></DD ><DT >3. <A -HREF="#AEN421" ->LanMan and NT Password Encryption in Samba 2.x</A +HREF="#PAM" +>Configuring PAM for distributed but centrally +managed authentication</A ></DT ><DD ><DL ><DT >3.1. <A -HREF="#AEN432" ->Introduction</A +HREF="#AEN454" +>Samba and PAM</A ></DT ><DT >3.2. <A -HREF="#AEN436" ->How does it work?</A +HREF="#AEN496" +>Distributed Authentication</A ></DT ><DT >3.3. <A -HREF="#AEN447" ->Important Notes About Security</A +HREF="#AEN503" +>PAM Configuration in smb.conf</A +></DT +></DL +></DD +><DT +>4. <A +HREF="#MSDFS" +>Hosting a Microsoft Distributed File System tree on Samba</A ></DT ><DD ><DL ><DT ->3.3.1. <A -HREF="#AEN466" ->Advantages of SMB Encryption</A +>4.1. <A +HREF="#AEN523" +>Instructions</A ></DT +><DD +><DL ><DT ->3.3.2. <A -HREF="#AEN473" ->Advantages of non-encrypted passwords</A +>4.1.1. <A +HREF="#AEN558" +>Notes</A ></DT ></DL ></DD +></DL +></DD ><DT ->3.4. <A -HREF="#AEN482" -><A -NAME="SMBPASSWDFILEFORMAT" -></A ->The smbpasswd file</A +>5. <A +HREF="#UNIX-PERMISSIONS" +>UNIX Permission Bits and Windows NT Access Control Lists</A ></DT +><DD +><DL ><DT ->3.5. <A -HREF="#AEN534" ->The smbpasswd Command</A +>5.1. <A +HREF="#AEN578" +>Viewing and changing UNIX permissions using the NT + security dialogs</A ></DT ><DT ->3.6. <A -HREF="#AEN573" ->Setting up Samba to support LanManager Encryption</A +>5.2. <A +HREF="#AEN587" +>How to view file security on a Samba share</A ></DT -></DL -></DD ><DT ->4. <A -HREF="#AEN588" ->Hosting a Microsoft Distributed File System tree on Samba</A +>5.3. <A +HREF="#AEN598" +>Viewing file ownership</A ></DT -><DD -><DL ><DT ->4.1. <A -HREF="#AEN599" ->Instructions</A +>5.4. <A +HREF="#AEN618" +>Viewing file or directory permissions</A ></DT ><DD ><DL ><DT ->4.1.1. <A -HREF="#AEN634" ->Notes</A +>5.4.1. <A +HREF="#AEN633" +>File Permissions</A +></DT +><DT +>5.4.2. <A +HREF="#AEN647" +>Directory Permissions</A ></DT ></DL ></DD +><DT +>5.5. <A +HREF="#AEN654" +>Modifying file or directory permissions</A +></DT +><DT +>5.6. <A +HREF="#AEN676" +>Interaction with the standard Samba create mask + parameters</A +></DT +><DT +>5.7. <A +HREF="#AEN740" +>Interaction with the standard Samba file attribute + mapping</A +></DT ></DL ></DD ><DT ->5. <A -HREF="#AEN643" +>6. <A +HREF="#PRINTING" >Printing Support in Samba 2.2.x</A ></DT ><DD ><DL ><DT ->5.1. <A -HREF="#AEN654" +>6.1. <A +HREF="#AEN761" >Introduction</A ></DT ><DT ->5.2. <A -HREF="#AEN676" +>6.2. <A +HREF="#AEN783" >Configuration</A ></DT ><DD ><DL ><DT ->5.2.1. <A -HREF="#AEN687" +>6.2.1. <A +HREF="#AEN794" >Creating [print$]</A ></DT ><DT ->5.2.2. <A -HREF="#AEN722" +>6.2.2. <A +HREF="#AEN829" >Setting Drivers for Existing Printers</A ></DT ><DT ->5.2.3. <A -HREF="#AEN739" +>6.2.3. <A +HREF="#AEN846" >Support a large number of printers</A ></DT ><DT ->5.2.4. <A -HREF="#AEN750" +>6.2.4. <A +HREF="#AEN857" >Adding New Printers via the Windows NT APW</A ></DT ><DT ->5.2.5. <A -HREF="#AEN775" +>6.2.5. <A +HREF="#AEN882" >Samba and Printer Ports</A ></DT ></DL ></DD ><DT ->5.3. <A -HREF="#AEN783" +>6.3. <A +HREF="#AEN890" >The Imprints Toolset</A ></DT ><DD ><DL ><DT ->5.3.1. <A -HREF="#AEN787" +>6.3.1. <A +HREF="#AEN894" >What is Imprints?</A ></DT ><DT ->5.3.2. <A -HREF="#AEN797" +>6.3.2. <A +HREF="#AEN904" >Creating Printer Driver Packages</A ></DT ><DT ->5.3.3. <A -HREF="#AEN800" +>6.3.3. <A +HREF="#AEN907" >The Imprints server</A ></DT ><DT ->5.3.4. <A -HREF="#AEN804" +>6.3.4. <A +HREF="#AEN911" >The Installation Client</A ></DT ></DL ></DD ><DT ->5.4. <A -HREF="#AEN826" +>6.4. <A +HREF="#AEN933" ><A NAME="MIGRATION" ></A @@ -482,138 +512,138 @@ NAME="MIGRATION" ></DL ></DD ><DT ->6. <A -HREF="#AEN870" +>7. <A +HREF="#DOMAIN-SECURITY" >security = domain in Samba 2.x</A ></DT ><DD ><DL ><DT ->6.1. <A -HREF="#AEN888" +>7.1. <A +HREF="#AEN995" >Joining an NT Domain with Samba 2.2</A ></DT ><DT ->6.2. <A -HREF="#AEN952" +>7.2. <A +HREF="#AEN1059" >Samba and Windows 2000 Domains</A ></DT ><DT ->6.3. <A -HREF="#AEN957" +>7.3. <A +HREF="#AEN1064" >Why is this better than security = server?</A ></DT ></DL ></DD ><DT ->7. <A -HREF="#AEN973" +>8. <A +HREF="#SAMBA-PDC" >How to Configure Samba 2.2 as a Primary Domain Controller</A ></DT ><DD ><DL ><DT ->7.1. <A -HREF="#AEN990" +>8.1. <A +HREF="#AEN1097" >Prerequisite Reading</A ></DT ><DT ->7.2. <A -HREF="#AEN996" +>8.2. <A +HREF="#AEN1103" >Background</A ></DT ><DT ->7.3. <A -HREF="#AEN1036" +>8.3. <A +HREF="#AEN1145" >Configuring the Samba Domain Controller</A ></DT ><DT ->7.4. <A -HREF="#AEN1079" +>8.4. <A +HREF="#AEN1188" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></DT ><DD ><DL ><DT ->7.4.1. <A -HREF="#AEN1093" +>8.4.1. <A +HREF="#AEN1202" >Manually creating machine trust accounts</A ></DT ><DT ->7.4.2. <A -HREF="#AEN1121" +>8.4.2. <A +HREF="#AEN1230" >Creating machine trust accounts "on the fly"</A ></DT ></DL ></DD ><DT ->7.5. <A -HREF="#AEN1132" +>8.5. <A +HREF="#AEN1241" >Common Problems and Errors</A ></DT ><DT ->7.6. <A -HREF="#AEN1180" +>8.6. <A +HREF="#AEN1289" >System Policies and Profiles</A ></DT ><DT ->7.7. <A -HREF="#AEN1224" +>8.7. <A +HREF="#AEN1333" >What other help can I get ?</A ></DT ><DT ->7.8. <A -HREF="#AEN1338" +>8.8. <A +HREF="#AEN1447" >Domain Control for Windows 9x/ME</A ></DT ><DD ><DL ><DT ->7.8.1. <A -HREF="#AEN1368" +>8.8.1. <A +HREF="#AEN1477" >Configuration Instructions: Network Logons</A ></DT ><DT ->7.8.2. <A -HREF="#AEN1402" +>8.8.2. <A +HREF="#AEN1511" >Configuration Instructions: Setting up Roaming User Profiles</A ></DT ><DD ><DL ><DT ->7.8.2.1. <A -HREF="#AEN1410" +>8.8.2.1. <A +HREF="#AEN1519" >Windows NT Configuration</A ></DT ><DT ->7.8.2.2. <A -HREF="#AEN1418" +>8.8.2.2. <A +HREF="#AEN1527" >Windows 9X Configuration</A ></DT ><DT ->7.8.2.3. <A -HREF="#AEN1426" +>8.8.2.3. <A +HREF="#AEN1535" >Win9X and WinNT Configuration</A ></DT ><DT ->7.8.2.4. <A -HREF="#AEN1433" +>8.8.2.4. <A +HREF="#AEN1542" >Windows 9X Profile Setup</A ></DT ><DT ->7.8.2.5. <A -HREF="#AEN1469" +>8.8.2.5. <A +HREF="#AEN1578" >Windows NT Workstation 4.0</A ></DT ><DT ->7.8.2.6. <A -HREF="#AEN1482" +>8.8.2.6. <A +HREF="#AEN1591" >Windows NT Server</A ></DT ><DT ->7.8.2.7. <A -HREF="#AEN1485" +>8.8.2.7. <A +HREF="#AEN1594" >Sharing Profiles between W95 and NT Workstation 4.0</A ></DT ></DL @@ -621,190 +651,129 @@ HREF="#AEN1485" ></DL ></DD ><DT ->7.9. <A -HREF="#AEN1495" +>8.9. <A +HREF="#AEN1604" >DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></DT ></DL ></DD ><DT ->8. <A -HREF="#AEN1520" ->Unifed Logons between Windows NT and UNIX using Winbind</A +>9. <A +HREF="#WINBIND" +>Unified Logons between Windows NT and UNIX using Winbind</A ></DT ><DD ><DL ><DT ->8.1. <A -HREF="#AEN1538" +>9.1. <A +HREF="#AEN1647" >Abstract</A ></DT ><DT ->8.2. <A -HREF="#AEN1542" +>9.2. <A +HREF="#AEN1651" >Introduction</A ></DT ><DT ->8.3. <A -HREF="#AEN1555" +>9.3. <A +HREF="#AEN1664" >What Winbind Provides</A ></DT ><DD ><DL ><DT ->8.3.1. <A -HREF="#AEN1562" +>9.3.1. <A +HREF="#AEN1671" >Target Uses</A ></DT ></DL ></DD ><DT ->8.4. <A -HREF="#AEN1566" +>9.4. <A +HREF="#AEN1675" >How Winbind Works</A ></DT ><DD ><DL ><DT ->8.4.1. <A -HREF="#AEN1571" +>9.4.1. <A +HREF="#AEN1680" >Microsoft Remote Procedure Calls</A ></DT ><DT ->8.4.2. <A -HREF="#AEN1575" +>9.4.2. <A +HREF="#AEN1684" >Name Service Switch</A ></DT ><DT ->8.4.3. <A -HREF="#AEN1591" +>9.4.3. <A +HREF="#AEN1700" >Pluggable Authentication Modules</A ></DT ><DT ->8.4.4. <A -HREF="#AEN1599" +>9.4.4. <A +HREF="#AEN1708" >User and Group ID Allocation</A ></DT ><DT ->8.4.5. <A -HREF="#AEN1603" +>9.4.5. <A +HREF="#AEN1712" >Result Caching</A ></DT ></DL ></DD ><DT ->8.5. <A -HREF="#AEN1606" ->Installation and Configuration</A -></DT -><DT ->8.6. <A -HREF="#AEN1612" ->Limitations</A -></DT -><DT ->8.7. <A -HREF="#AEN1624" ->Conclusion</A -></DT -></DL -></DD -><DT ->9. <A -HREF="#AEN1627" ->UNIX Permission Bits and WIndows NT Access Control Lists</A -></DT -><DD -><DL -><DT ->9.1. <A -HREF="#AEN1638" ->Viewing and changing UNIX permissions using the NT - security dialogs</A -></DT -><DT ->9.2. <A -HREF="#AEN1647" ->How to view file security on a Samba share</A -></DT -><DT ->9.3. <A -HREF="#AEN1658" ->Viewing file ownership</A -></DT -><DT ->9.4. <A -HREF="#AEN1678" ->Viewing file or directory permissions</A -></DT -><DD -><DL -><DT ->9.4.1. <A -HREF="#AEN1693" ->File Permissions</A -></DT -><DT ->9.4.2. <A -HREF="#AEN1707" ->Directory Permissions</A -></DT -></DL -></DD -><DT >9.5. <A -HREF="#AEN1714" ->Modifying file or directory permissions</A +HREF="#AEN1715" +>Installation and Configuration</A ></DT ><DT >9.6. <A -HREF="#AEN1736" ->Interaction with the standard Samba create mask - parameters</A +HREF="#AEN1721" +>Limitations</A ></DT ><DT >9.7. <A -HREF="#AEN1800" ->Interaction with the standard Samba file attribute - mapping</A +HREF="#AEN1733" +>Conclusion</A ></DT ></DL ></DD ><DT >10. <A -HREF="#AEN1810" +HREF="#OS2" >OS2 Client HOWTO</A ></DT ><DD ><DL ><DT >10.1. <A -HREF="#AEN1821" +HREF="#AEN1747" >FAQs</A ></DT ><DD ><DL ><DT >10.1.1. <A -HREF="#AEN1823" +HREF="#AEN1749" >How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</A ></DT ><DT >10.1.2. <A -HREF="#AEN1838" +HREF="#AEN1764" >How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</A ></DT ><DT >10.1.3. <A -HREF="#AEN1847" +HREF="#AEN1773" >Are there any other issues when OS/2 (any version) is used as a client?</A ></DT ><DT >10.1.4. <A -HREF="#AEN1851" +HREF="#AEN1777" >How do I get printer driver download working for OS/2 clients?</A ></DT @@ -814,44 +783,49 @@ HREF="#AEN1851" ></DD ><DT >11. <A -HREF="#AEN1860" +HREF="#CVS-ACCESS" >HOWTO Access Samba source code via CVS</A ></DT ><DD ><DL ><DT >11.1. <A -HREF="#AEN1867" +HREF="#AEN1793" >Introduction</A ></DT ><DT >11.2. <A -HREF="#AEN1872" +HREF="#AEN1798" >CVS Access to samba.org</A ></DT ><DD ><DL ><DT >11.2.1. <A -HREF="#AEN1875" +HREF="#AEN1801" >Access via CVSweb</A ></DT ><DT >11.2.2. <A -HREF="#AEN1880" +HREF="#AEN1806" >Access via cvs</A ></DT ></DL ></DD ></DL ></DD +><DT +><A +HREF="#AEN1834" +>Index</A +></DT ></DL ></DIV ><DIV CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN15" +NAME="INSTALL" >Chapter 1. How to Install and Test SAMBA</A ></H1 ><DIV @@ -915,7 +889,7 @@ CLASS="USERINPUT" ></P ><P >first to see what special options you can enable. - Then exectuting</P + Then executing</P ><P ><TT CLASS="PROMPT" @@ -1042,7 +1016,7 @@ CLASS="PROGRAMLISTING" >which would allow connections by anyone with an account on the server, using either their login name or "homes" as the service name. (Note that I also set the - workgroup that Samba is part of. See BROWSING.txt for defails)</P + workgroup that Samba is part of. See BROWSING.txt for details)</P ><P >Note that <B CLASS="COMMAND" @@ -1089,7 +1063,7 @@ CLASS="FILENAME" not it will give an error message.</P ><P >Make sure it runs OK and that the services look - resonable before proceeding. </P + reasonable before proceeding. </P ></DIV ><DIV CLASS="SECT1" @@ -1207,7 +1181,7 @@ CLASS="FILENAME" <TT CLASS="FILENAME" >/etc/inetd.conf</TT -> to make them consistant.</P +> to make them consistent.</P ><P >NOTE: On many systems you may need to use the "interfaces" option in smb.conf to specify the IP address @@ -1220,7 +1194,7 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > tries to determine it at run - time, but fails on somunixes. See the section on "testing nmbd" + time, but fails on some unixes. See the section on "testing nmbd" for a method of finding if you need to do this.</P ><P >!!!WARNING!!! Many unixes only accept around 5 @@ -1495,7 +1469,7 @@ NAME="AEN176" >1.10.1. Diagnosing Problems</A ></H2 ><P ->If you have instalation problems then go to +>If you have installation problems then go to <TT CLASS="FILENAME" >DIAGNOSIS.txt</TT @@ -1629,7 +1603,7 @@ NAME="AEN196" are set by an application when it opens a file to determine what types of access should be allowed simultaneously with its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE - or DENY_ALL. There are also special compatability modes called + or DENY_ALL. There are also special compatibility modes called DENY_FCB and DENY_DOS.</P ><P >You can disable share modes using "share modes = no". @@ -1662,7 +1636,7 @@ NAME="AEN209" ><P >If you have problems using filenames with accented characters in them (like the German, French or Scandinavian - character sets) then I recommmend you look at the "valid chars" + character sets) then I recommend you look at the "valid chars" option in smb.conf and also take a look at the validchars package in the examples directory.</P ></DIV @@ -1672,7 +1646,7 @@ NAME="AEN209" CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN212" +NAME="INTEGRATE-MS-NETWORKS" >Chapter 2. Integrating MS Windows networks with Samba</A ></H1 ><DIV @@ -1751,13 +1725,45 @@ NAME="AEN245" >2.2. Name Resolution in a pure Unix/Linux world</A ></H1 ><P ->The key configuration files : </P +>The key configuration files covered in this section are:</P +><P +></P +><UL +><LI +><P +><TT +CLASS="FILENAME" +>/etc/hosts</TT +></P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>/etc/resolv.conf</TT +></P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>/etc/host.conf</TT +></P +></LI +><LI +><P +><TT +CLASS="FILENAME" +>/etc/nsswitch.conf</TT +></P +></LI +></UL ><DIV CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN248" +NAME="AEN261" >2.2.1. <TT CLASS="FILENAME" >/etc/hosts</TT @@ -1847,7 +1853,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN264" +NAME="AEN277" >2.2.2. <TT CLASS="FILENAME" >/etc/resolv.conf</TT @@ -1885,7 +1891,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN275" +NAME="AEN288" >2.2.3. <TT CLASS="FILENAME" >/etc/host.conf</TT @@ -1923,7 +1929,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN283" +NAME="AEN296" >2.2.4. <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -2001,7 +2007,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN295" +NAME="AEN308" >2.3. Name resolution as used within MS Windows networking</A ></H1 ><P @@ -2095,7 +2101,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN307" +NAME="AEN320" >2.3.1. The NetBIOS Name Cache</A ></H2 ><P @@ -2122,7 +2128,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN312" +NAME="AEN325" >2.3.2. The LMHOSTS file</A ></H2 ><P @@ -2234,7 +2240,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN320" +NAME="AEN333" >2.3.3. HOSTS file</A ></H2 ><P @@ -2256,7 +2262,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN325" +NAME="AEN338" >2.3.4. DNS Lookup</A ></H2 ><P @@ -2276,14 +2282,11 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN328" +NAME="AEN341" >2.3.5. WINS Lookup</A ></H2 ><P ->Refer to above details for section <EM ->DNS Lookups</EM ->. A -WINS (Windows Internet Name Server) service is the equivaent of the +>A WINS (Windows Internet Name Server) service is the equivaent of the rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores the names and IP addresses that are registered by a Windows client if the TCP/IP setup has been given at least one WINS Server IP Address.</P @@ -2320,12 +2323,7 @@ WIDTH="100%" ><PRE CLASS="PROGRAMLISTING" > wins support = No - wins server = <TT -CLASS="REPLACEABLE" -><I ->xxx.xxx.xxx.xxx</I -></TT -></PRE + wins server = xxx.xxx.xxx.xxx</PRE ></TD ></TR ></TABLE @@ -2345,7 +2343,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN342" +NAME="AEN353" >2.4. How browsing functions and how to deploy stable and dependable browsing using Samba</A ></H1 @@ -2412,35 +2410,47 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN352" +NAME="AEN363" >2.5. MS Windows security options and how to configure Samba for seemless integration</A ></H1 ><P ->MS Windows clients may use encrypted passwords alone, or encrypted -as well as plain text passwords in the authentication process. It -should be realized that with the SMB protocol the password is passed -over the network either in plain text or encrypted. When encrypted -passwords are used a password that has been entered by the user is -encrypted in two ways:</P +>MS Windows clients may use encrypted passwords as part of a +challenege/response authentication model (a.k.a. NTLMv1) or +alone, or clear text strings for simple password based +authentication. It should be realized that with the SMB +protocol the password is passed over the network either +in plain text or encrypted, but not both in the same +authentication requets.</P +><P +>When encrypted passwords are used a password that has been +entered by the user is encrypted in two ways:</P ><P ></P ><UL ><LI ><P ->The case preserved password is encrypted - using an MD5/DES one way hash +>An MD4 hash of the UNICODE of the password + string. This is known as the NT hash. </P ></LI ><LI ><P ->The case is converted to upper case and then - encrypted using an MD5/DES one way hash</P +>The password is converted to upper case, + and then padded or trucated to 14 bytes. This string is + then appended with 5 bytes of NULL characters and split to + form two 56 bit DES keys to encrypt a "magic" 8 byte value. + The resulting 16 bytes for the LanMan hash. + </P ></LI ></UL ><P ->Both of these enrypted passwords are sent over the network -in the one authentication datagram.</P +>You should refer to the <A +HREF="ENCRYPTION.html" +TARGET="_top" +>Password Encryption</A +> chapter in this HOWTO collection +for more details on the inner workings</P ><P >MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0 pre-service pack 3 will use either mode of @@ -2461,8 +2471,10 @@ the remote authentication server does not support encrypted passwords. This means that it is definitely not a good idea to re-enable plain text password support in such clients.</P ><P ->It is recommended that the following parameters be added to the -smb.conf file:</P +>The following parameters can be used to work around the +issue of Windows 9x client upper casing usernames and +password before transmitting them to the SMB server +when using clear text authentication.</P ><P ><TABLE BORDER="0" @@ -2472,19 +2484,65 @@ WIDTH="100%" ><TD ><PRE CLASS="PROGRAMLISTING" -> passsword level = 8 - username level = 8</PRE +> <A +HREF="smb.conf.5.html#PASSWORDLEVEL" +TARGET="_top" +>passsword level</A +> = <TT +CLASS="REPLACEABLE" +><I +>integer</I +></TT +> + <A +HREF="smb.conf.5.html#USERNAMELEVEL" +TARGET="_top" +>username level</A +> = <TT +CLASS="REPLACEABLE" +><I +>integer</I +></TT +></PRE ></TD ></TR ></TABLE ></P ><P ->these configuration parameters will compensate for the fact that -in some circumstances MS Windows and MS DOS clients may twiddle the -password that has been supplied by the user by converting characters to -upper case. The above entries will try every combination of upper and -lower case for the first 8 characters. Please refer to the man page -for smb.conf for more information on use of these parameters.</P +>By default Samba will lower case the username before attempting +to lookup the user in the database of local system accounts. +Because UNIX usernames conventionally only contain lower case +character, the <TT +CLASS="PARAMETER" +><I +>username level</I +></TT +> parameter +is rarely even needed.</P +><P +>However, password on UNIX systems often make use of mixed case +characters. This means that in order for a user on a Windows 9x +client to connect to a Samba server using clear text authentication, +the <TT +CLASS="PARAMETER" +><I +>password level</I +></TT +> must be set to the maximum +number of upper case letter which <EM +>could</EM +> appear +is a password. Note that is the server OS uses the traditional +DES version of crypt(), then a <TT +CLASS="PARAMETER" +><I +>password level</I +></TT +> +of 8 will result in case insensitive passwords as seen from Windows +users. This will also result in longer login times as Samba +hash to compute the permutations of the password string and +try them one by one until a match is located (or all combinations fail).</P ><P >The best option to adopt is to enable support for encrypted passwords where ever Samba is used. There are three configuration possibilities @@ -2494,7 +2552,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN369" +NAME="AEN391" >2.5.1. Use MS Windows NT as an authentication server</A ></H2 ><P @@ -2539,7 +2597,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN377" +NAME="AEN399" >2.5.2. Make Samba a member of an MS Windows NT security domain</A ></H2 ><P @@ -2589,15 +2647,29 @@ CLASS="COMMAND" ></UL ><P >Use of this mode of authentication does require there to be -a standard Unix account for the user, this account can be -blocked to prevent logons by other than MS Windows clients.</P +a standard Unix account for the user in order to assign +a uid once the account has been authenticated by the remote +Windows DC. This account can be blocked to prevent logons by +other than MS Windows clients by things such as setting an invalid +shell in the <TT +CLASS="FILENAME" +>/etc/passwd</TT +> entry.</P +><P +>An alternative to assigning UIDs to Windows users on a +Samba member server is presented in the <A +HREF="winbind.html" +TARGET="_top" +>Winbind Overview</A +> chapter in +this HOWTO collection.</P ></DIV ><DIV CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN391" +NAME="AEN416" >2.5.3. Configure Samba as an authentication server</A ></H2 ><P @@ -2618,8 +2690,18 @@ WIDTH="100%" ><TD ><PRE CLASS="PROGRAMLISTING" -> encrypt passwords = Yes - security = user</PRE +>## please refer to the Samba PDC HOWTO chapter later in +## this collection for more details +[global] + encrypt passwords = Yes + security = user + domain logons = Yes + ; an OS level of 33 or more is recommended + os level = 33 + +[NETLOGON] + path = /somewhare/in/file/system + read only = yes</PRE ></TD ></TR ></TABLE @@ -2633,7 +2715,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN398" +NAME="AEN423" >2.5.3.1. Users</A ></H3 ><P @@ -2651,20 +2733,10 @@ WIDTH="100%" CLASS="PROGRAMLISTING" > # useradd -s /bin/bash -d /home/"userid" -m # passwd "userid" - Enter Password: <TT -CLASS="USERINPUT" -><B ->pass</B -></TT -> + Enter Password: <pw> # smbpasswd -a "userid" - Enter Password: <TT -CLASS="USERINPUT" -><B ->pass</B -></TT -></PRE + Enter Password: <pw></PRE ></TD ></TR ></TABLE @@ -2675,7 +2747,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN405" +NAME="AEN428" >2.5.3.2. MS Windows NT Machine Accounts</A ></H3 ><P @@ -2705,10 +2777,12 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN410" ->2.6. Configuration of Samba as ...</A +NAME="AEN433" +>2.6. Conclusions</A ></H1 ><P +>Samba provides a flexible means to operate as...</P +><P ></P ><UL ><LI @@ -2723,384 +2797,185 @@ NAME="AEN410" ></LI ><LI ><P ->An MS Windows NT 3.x/4.0 security domain member - - Refer to the previous section(s) above. +>An MS Windows NT 3.x/4.0 security domain member. </P ></LI ><LI ><P >An alternative to an MS Windows NT 3.x/4.0 - Domain Controller - In the smb.conf file the following parameters - should be added:</P + Domain Controller. + </P ></LI ></UL -><P -><TABLE -BORDER="0" -BGCOLOR="#E0E0E0" -WIDTH="100%" -><TR -><TD -><PRE -CLASS="PROGRAMLISTING" ->## please refer to the Samba PDC HOWTO chapter later in -## this collection for more details -[global] - domain logons = Yes - ; an OS level of 33 or more is recommended - os level = 33 - - [NETLOGON] - path = /somewhare/in/file/system - read only = yes - available = yes</PRE -></TD -></TR -></TABLE -></P ></DIV ></DIV ><DIV CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN421" ->Chapter 3. LanMan and NT Password Encryption in Samba 2.x</A +NAME="PAM" +>Chapter 3. Configuring PAM for distributed but centrally +managed authentication</A ></H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN432" ->3.1. Introduction</A -></H1 -><P ->With the development of LanManager and Windows NT - compatible password encryption for Samba, it is now able - to validate user connections in exactly the same way as - a LanManager or Windows NT server.</P -><P ->This document describes how the SMB password encryption - algorithm works and what issues there are in choosing whether - you want to use it. You should read it carefully, especially - the part about security and the "PROS and CONS" section.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" -><A -NAME="AEN436" ->3.2. How does it work?</A +NAME="AEN454" +>3.1. Samba and PAM</A ></H1 ><P ->LanManager encryption is somewhat similar to UNIX - password encryption. The server uses a file containing a - hashed value of a user's password. This is created by taking - the user's plaintext password, capitalising it, and either - truncating to 14 bytes or padding to 14 bytes with null bytes. - This 14 byte value is used as two 56 bit DES keys to encrypt - a 'magic' eight byte value, forming a 16 byte value which is - stored by the server and client. Let this value be known as - the "hashed password".</P -><P ->Windows NT encryption is a higher quality mechanism, - consisting of doing an MD4 hash on a Unicode version of the user's - password. This also produces a 16 byte hash value that is - non-reversible.</P -><P ->When a client (LanManager, Windows for WorkGroups, Windows - 95 or Windows NT) wishes to mount a Samba drive (or use a Samba - resource), it first requests a connection and negotiates the - protocol that the client and server will use. In the reply to this - request the Samba server generates and appends an 8 byte, random - value - this is stored in the Samba server after the reply is sent - and is known as the "challenge". The challenge is different for - every client connection.</P -><P ->The client then uses the hashed password (16 byte values - described above), appended with 5 null bytes, as three 56 bit - DES keys, each of which is used to encrypt the challenge 8 byte - value, forming a 24 byte value known as the "response".</P -><P ->In the SMB call SMBsessionsetupX (when user level security - is selected) or the call SMBtconX (when share level security is - selected), the 24 byte response is returned by the client to the - Samba server. For Windows NT protocol levels the above calculation - is done on both hashes of the user's password and both responses are - returned in the SMB call, giving two 24 byte values.</P -><P ->The Samba server then reproduces the above calculation, using - its own stored value of the 16 byte hashed password (read from the - <TT +>A number of Unix systems (eg: Sun Solaris), as well as the +xxxxBSD family and Linux, now utilize the Pluggable Authentication +Modules (PAM) facility to provide all authentication, +authorization and resource control services. Prior to the +introduction of PAM, a decision to use an alternative to +the system password database (<TT CLASS="FILENAME" ->smbpasswd</TT -> file - described later) and the challenge - value that it kept from the negotiate protocol reply. It then checks - to see if the 24 byte value it calculates matches the 24 byte value - returned to it from the client.</P -><P ->If these values match exactly, then the client knew the - correct password (or the 16 byte hashed value - see security note - below) and is thus allowed access. If not, then the client did not - know the correct password and is denied access.</P +>/etc/passwd</TT +>) +would require the provision of alternatives for all programs that provide +security services. Such a choice would involve provision of +alternatives to such programs as: <B +CLASS="COMMAND" +>login</B +>, +<B +CLASS="COMMAND" +>passwd</B +>, <B +CLASS="COMMAND" +>chown</B +>, etc.</P ><P ->Note that the Samba server never knows or stores the cleartext - of the user's password - just the 16 byte hashed values derived from - it. Also note that the cleartext password or 16 byte hashed values - are never transmitted over the network - thus increasing security.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" -><A -NAME="AEN447" ->3.3. Important Notes About Security</A -></H1 +>PAM provides a mechanism that disconnects these security programs +from the underlying authentication/authorization infrastructure. +PAM is configured either through one file <TT +CLASS="FILENAME" +>/etc/pam.conf</TT +> (Solaris), +or by editing individual files that are located in <TT +CLASS="FILENAME" +>/etc/pam.d</TT +>.</P ><P ->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 nextwork when - logging in. This is bad. The SMB encryption scheme never sends the - cleartext 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 "password equivalent". 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 thus treat the smbpasswd file as though it contained the - cleartext passwords of all your users. Its contents must be kept - secret, and the file should be protected accordingly.</P -><P ->Ideally we would like a password scheme which neither requires - plain text passwords on the net or on disk. Unfortunately this - is not available as Samba is stuck with being compatible with - other SMB systems (WinNT, WfWg, Win95 etc). </P -><DIV -CLASS="WARNING" +>The following is an example <TT +CLASS="FILENAME" +>/etc/pam.d/login</TT +> configuration file. +This example had all options been uncommented is probably not usable +as it stacks many conditions before allowing successful completion +of the login process. Essentially all conditions can be disabled +by commenting them out except the calls to <TT +CLASS="FILENAME" +>pam_pwdb.so</TT +>.</P ><P -></P ><TABLE -CLASS="WARNING" -BORDER="1" +BORDER="0" +BGCOLOR="#E0E0E0" WIDTH="100%" ><TR ><TD -ALIGN="CENTER" -><B ->Warning</B +><PRE +CLASS="PROGRAMLISTING" +>#%PAM-1.0 +# The PAM configuration file for the `login' service +# +auth required pam_securetty.so +auth required pam_nologin.so +# auth required pam_dialup.so +# auth optional pam_mail.so +auth required pam_pwdb.so shadow md5 +# account requisite pam_time.so +account required pam_pwdb.so +session required pam_pwdb.so +# session optional pam_lastlog.so +# password required pam_cracklib.so retry=3 +password required pam_pwdb.so shadow md5</PRE ></TD ></TR -><TR -><TD -ALIGN="LEFT" -><P ->Note that Windows NT 4.0 Service pack 3 changed the - default for permissible authentication so that plaintext - passwords are <EM ->never</EM -> sent over the wire. - The solution to this is either to switch to encrypted passwords - with Samba or edit the Windows NT registry to re-enable plaintext - passwords. See the document WinNT.txt for details on how to do - this.</P -><P ->Other Microsoft operating systems which also exhibit - this behavior includes</P -><P +></TABLE ></P -><UL -><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 [se]</P -></LI -><LI -><P ->Windows 2000</P -></LI -></UL +>PAM allows use of replacable modules. Those available on a +sample system include:</P ><P -><EM ->Note :</EM ->All current release 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 particpate in encrypted authentication.</P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>$ /bin/ls /lib/security +pam_access.so pam_ftp.so pam_limits.so +pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so +pam_cracklib.so pam_group.so pam_listfile.so +pam_nologin.so pam_rootok.so pam_tally.so +pam_deny.so pam_issue.so pam_mail.so +pam_permit.so pam_securetty.so pam_time.so +pam_dialup.so pam_lastlog.so pam_mkhomedir.so +pam_pwdb.so pam_shells.so pam_unix.so +pam_env.so pam_ldap.so pam_motd.so +pam_radius.so pam_smbpass.so pam_unix_acct.so +pam_wheel.so pam_unix_auth.so pam_unix_passwd.so +pam_userdb.so pam_warn.so pam_unix_session.so</PRE ></TD ></TR ></TABLE -></DIV -><DIV -CLASS="SECT2" -><HR><H2 -CLASS="SECT2" -><A -NAME="AEN466" ->3.3.1. Advantages of SMB Encryption</A -></H2 -><P ></P -><UL -><LI ><P ->plain text 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 ->WinNT doesn't like talking to a server - that isn't using SMB 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 things you can do to stop this is to use SMB encryption. - </P -></LI -></UL -></DIV -><DIV -CLASS="SECT2" -><HR><H2 -CLASS="SECT2" -><A -NAME="AEN473" ->3.3.2. Advantages of non-encrypted passwords</A -></H2 -><P -></P -><UL -><LI -><P ->plain text passwords are not kept - on disk. </P -></LI -><LI -><P ->uses same password file as other unix - services such as login and ftp</P -></LI -><LI -><P ->you are probably already using other - services (such as telnet and ftp) which send plain text - passwords over the net, so sending them for SMB isn't - such a big deal.</P -></LI -></UL -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" -><A -NAME="AEN482" ->3.4. <A -NAME="SMBPASSWDFILEFORMAT" -></A ->The smbpasswd file</A -></H1 -><P ->In order for Samba to participate in the above protocol - it must be able to look up the 16 byte hashed values given a user name. - Unfortunately, as the UNIX password value is also a one way hash - function (ie. it is impossible to retrieve the cleartext of the user's - password given the UNIX hash of it), a separate password file - containing this 16 byte value must be kept. To minimise problems with - these two password files, getting out of sync, the UNIX <TT -CLASS="FILENAME" -> /etc/passwd</TT -> and the <TT +>The following example for the login program replaces the use of +the <TT CLASS="FILENAME" ->smbpasswd</TT -> file, - a utility, <B -CLASS="COMMAND" ->mksmbpasswd.sh</B ->, is provided to generate - a smbpasswd file from a UNIX <TT +>pam_pwdb.so</TT +> module which uses the system +password database (<TT CLASS="FILENAME" >/etc/passwd</TT -> file. - </P -><P ->To generate the smbpasswd file from your <TT +>, +<TT CLASS="FILENAME" ->/etc/passwd - </TT -> file use the following command :</P -><P -><TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->cat /etc/passwd | mksmbpasswd.sh - > /usr/local/samba/private/smbpasswd</B -></TT -></P -><P ->If you are running on a system that uses NIS, use</P -><P -><TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->ypcat passwd | mksmbpasswd.sh - > /usr/local/samba/private/smbpasswd</B -></TT -></P -><P ->The <B -CLASS="COMMAND" ->mksmbpasswd.sh</B -> program is found in - the Samba source directory. By default, the smbpasswd file is - stored in :</P -><P -><TT +>/etc/shadow</TT +>, <TT +CLASS="FILENAME" +>/etc/group</TT +>) with +the module <TT +CLASS="FILENAME" +>pam_smbpass.so</TT +> which uses the Samba +database which contains the Microsoft MD4 encrypted password +hashes. This database is stored in either +<TT CLASS="FILENAME" >/usr/local/samba/private/smbpasswd</TT -></P -><P ->The owner of the <TT +>, +<TT CLASS="FILENAME" ->/usr/local/samba/private/</TT -> - directory should be set to root, and the permissions on it should - be set to 0500 (<B -CLASS="COMMAND" ->chmod 500 /usr/local/samba/private</B ->). - </P -><P ->Likewise, the smbpasswd file inside the private directory should - be owned by root and the permissions on is should be set to 0600 - (<B +>/etc/samba/smbpasswd</TT +>, or in +<TT +CLASS="FILENAME" +>/etc/samba.d/smbpasswd</TT +>, depending on the +Samba implementation for your Unix/Linux system. The +<TT +CLASS="FILENAME" +>pam_smbpass.so</TT +> module is provided by +Samba version 2.2.1 or later. It can be compiled only if the +<TT +CLASS="CONSTANT" +>--with-pam --with-pam_smbpass</TT +> options are both +provided to the Samba <B CLASS="COMMAND" ->chmod 600 smbpasswd</B ->).</P -><P ->The format of the smbpasswd file is (The line has been - wrapped here. It should appear as one entry per line in - your smbpasswd file.)</P +>configure</B +> program.</P ><P ><TABLE BORDER="0" @@ -3110,68 +2985,23 @@ WIDTH="100%" ><TD ><PRE CLASS="PROGRAMLISTING" ->username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX: - [Account type]:LCT-<last-change-time>:Long name - </PRE +>#%PAM-1.0 +# The PAM configuration file for the `login' service +# +auth required pam_smbpass.so nodelay +account required pam_smbpass.so nodelay +session required pam_smbpass.so nodelay +password required pam_smbpass.so nodelay</PRE ></TD ></TR ></TABLE ></P ><P ->Although only the <TT -CLASS="REPLACEABLE" -><I ->username</I -></TT ->, - <TT -CLASS="REPLACEABLE" -><I ->uid</I -></TT ->, <TT -CLASS="REPLACEABLE" -><I -> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</I -></TT ->, - [<TT -CLASS="REPLACEABLE" -><I ->Account type</I -></TT ->] and <TT -CLASS="REPLACEABLE" -><I -> last-change-time</I -></TT -> sections are significant - and are looked at in the Samba code.</P -><P ->It is <EM ->VITALLY</EM -> important that there by 32 - 'X' characters between the two ':' characters in the XXX sections - - the smbpasswd and Samba code will fail to validate any entries that - do not have 32 characters between ':' characters. The first XXX - section is for the Lanman password hash, the second is for the - Windows NT version.</P -><P ->When the password file is created all users have password entries - consisting of 32 'X' characters. By default this disallows any access - as this user. When a user has a password set, the 'X' characters change - to 32 ascii hexadecimal digits (0-9, A-F). These are an ascii - representation of the 16 byte hashed value of a user's password.</P -><P ->To set a user to have no password (not recommended), edit the file - using vi, and replace the first 11 characters with the ascii text - <TT -CLASS="CONSTANT" ->"NO PASSWORD"</TT -> (minus the quotes).</P -><P ->For example, to clear the password for user bob, his smbpasswd file - entry would look like :</P +>The following is the PAM configuration file for a particular +Linux system. The default condition uses <TT +CLASS="FILENAME" +>pam_pwdb.so</TT +>.</P ><P ><TABLE BORDER="0" @@ -3181,238 +3011,141 @@ WIDTH="100%" ><TD ><PRE CLASS="PROGRAMLISTING" -> bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U ]:LCT-00000000:Bob's full name:/bobhome:/bobshell - </PRE +>#%PAM-1.0 +# The PAM configuration file for the `samba' service +# +auth required /lib/security/pam_pwdb.so nullok nodelay shadow audit +account required /lib/security/pam_pwdb.so audit nodelay +session required /lib/security/pam_pwdb.so nodelay +password required /lib/security/pam_pwdb.so shadow md5</PRE ></TD ></TR ></TABLE ></P ><P ->If you are allowing users to use the smbpasswd command to set - their own passwords, you may want to give users NO PASSWORD initially - so they do not have to enter a previous password when changing to their - new password (not recommended). In order for you to allow this the - <B -CLASS="COMMAND" ->smbpasswd</B -> program must be able to connect to the - <B -CLASS="COMMAND" ->smbd</B -> daemon as that user with no password. Enable this - by adding the line :</P +>In the following example the decision has been made to use the +smbpasswd database even for basic samba authentication. Such a +decision could also be made for the passwd program and would +thus allow the smbpasswd passwords to be changed using the passwd +program.</P ><P -><B -CLASS="COMMAND" ->null passwords = yes</B +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>#%PAM-1.0 +# The PAM configuration file for the `samba' service +# +auth required /lib/security/pam_smbpass.so nodelay +account required /lib/security/pam_pwdb.so audit nodelay +session required /lib/security/pam_pwdb.so nodelay +password required /lib/security/pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf</PRE +></TD +></TR +></TABLE ></P ><P ->to the [global] section of the smb.conf file (this is why - the above scenario is not recommended). Preferably, allocate your - users a default password to begin with, so you do not have - to enable this on your server.</P -><P -><EM ->Note : </EM ->This file should be protected very - carefully. Anyone with access to this file can (with enough knowledge of - the protocols) gain access to your SMB server. The file is thus more - sensitive than a normal unix <TT +>Note: PAM allows stacking of authentication mechanisms. It is +also possible to pass information obtained within on PAM module through +to the next module in the PAM stack. Please refer to the documentation for +your particular system implementation for details regarding the specific +capabilities of PAM in this environment. Some Linux implmentations also +provide the <TT CLASS="FILENAME" ->/etc/passwd</TT -> file.</P +>pam_stack.so</TT +> module that allows all +authentication to be configured in a single central file. The +<TT +CLASS="FILENAME" +>pam_stack.so</TT +> method has some very devoted followers +on the basis that it allows for easier administration. As with all issues in +life though, every decision makes trade-offs, so you may want examine the +PAM documentation for further helpful information.</P ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN534" ->3.5. The smbpasswd Command</A +NAME="AEN496" +>3.2. Distributed Authentication</A ></H1 ><P ->The smbpasswd command maintains the two 32 byte password fields - in the smbpasswd file. If you wish to make it similar to the unix - <B -CLASS="COMMAND" ->passwd</B -> or <B -CLASS="COMMAND" ->yppasswd</B -> programs, - install it in <TT +>The astute administrator will realize from this that the +combination of <TT CLASS="FILENAME" ->/usr/local/samba/bin/</TT -> (or your - main Samba binary directory).</P -><P ->Note that as of Samba 1.9.18p4 this program <EM ->MUST NOT - BE INSTALLED</EM -> setuid root (the new <B -CLASS="COMMAND" ->smbpasswd</B -> - code enforces this restriction so it cannot be run this way by - accident).</P -><P -><B -CLASS="COMMAND" ->smbpasswd</B -> now 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 - as follows.</P -><P -></P -><UL -><LI -><P ->smbpasswd no longer has to be setuid root - - an enormous range of potential security problems is - eliminated.</P -></LI -><LI -><P -><B -CLASS="COMMAND" ->smbpasswd</B -> now has the capability - to change passwords on Windows NT servers (this only works when - the request is sent to the NT Primary Domain Controller if you - are changing an NT Domain user's password).</P -></LI -></UL -><P ->To run smbpasswd as a normal user just type :</P -><P -><TT -CLASS="PROMPT" ->$ </TT -><TT -CLASS="USERINPUT" -><B ->smbpasswd</B -></TT -></P -><P -><TT -CLASS="PROMPT" ->Old SMB password: </TT -><TT -CLASS="USERINPUT" -><B -><type old value here - - or hit return if there was no old password></B -></TT -></P -><P -><TT -CLASS="PROMPT" ->New SMB Password: </TT -><TT -CLASS="USERINPUT" -><B -><type new value> - </B -></TT -></P -><P -><TT -CLASS="PROMPT" ->Repeat New SMB Password: </TT -><TT -CLASS="USERINPUT" -><B -><re-type new value - </B -></TT -></P -><P ->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 ->If invoked by an ordinary user it will only allow the user - to change his or her own Samba password.</P -><P ->If run by the root user smbpasswd may take an optional - argument, specifying the user name whose SMB password you wish to - change. Note that when run as root smbpasswd 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 -><B -CLASS="COMMAND" ->smbpasswd</B -> is designed to work in the same way - and be familiar to UNIX users who use the <B -CLASS="COMMAND" ->passwd</B -> or - <B +>pam_smbpass.so</TT +>, +<B CLASS="COMMAND" ->yppasswd</B -> commands.</P -><P ->For more details on using <B +>winbindd</B +>, and <B CLASS="COMMAND" ->smbpasswd</B -> refer - to the man page which will always be the definitive reference.</P +>rsync</B +> (see +<A +HREF="http://rsync.samba.org/" +TARGET="_top" +>http://rsync.samba.org/</A +>) +will allow the establishment of a centrally managed, distributed +user/password database that can also be used by all +PAM (eg: Linux) aware programs and applications. This arrangement +can have particularly potent advantages compared with the +use of Microsoft Active Directory Service (ADS) in so far as +reduction of wide area network authentication traffic.</P ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN573" ->3.6. Setting up Samba to support LanManager Encryption</A +NAME="AEN503" +>3.3. PAM Configuration in smb.conf</A ></H1 ><P ->This is a very brief description on how to setup samba to - support password encryption. </P -><P -></P -><OL -TYPE="1" -><LI +>There is an option in smb.conf called <A +HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS" +TARGET="_top" +>obey pam restrictions</A +>. +The following is from the on-line help for this option in SWAT;</P ><P ->compile and install samba as usual</P -></LI -><LI +>When Samba 2.2 is configure to enable PAM support (i.e. +<TT +CLASS="CONSTANT" +>--with-pam</TT +>), this parameter will +control whether or not Samba should obey PAM's account +and session management directives. The default behavior +is to use PAM for clear text authentication only and to +ignore any account or session management. Note that Samba always +ignores PAM for authentication in the case of +<A +HREF="smb.conf.5.html#ENCRYPTPASSWORDS" +TARGET="_top" +>encrypt passwords = yes</A +>. +The reason is that PAM modules cannot support the challenge/response +authentication mechanism needed in the presence of SMB +password encryption. </P ><P ->enable encrypted passwords in <TT -CLASS="FILENAME" -> smb.conf</TT -> by adding the line <B +>Default: <B CLASS="COMMAND" ->encrypt - passwords = yes</B -> in the [global] section</P -></LI -><LI -><P ->create the initial <TT -CLASS="FILENAME" ->smbpasswd</TT -> - password file in the place you specified in the Makefile - (--prefix=<dir>). See the notes under the <A -HREF="#SMBPASSWDFILEFORMAT" ->The smbpasswd File</A -> - section earlier in the document for details.</P -></LI -></OL -><P ->Note that you can test things using smbclient.</P +>obey pam restrictions = no</B +></P ></DIV ></DIV ><DIV CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN588" +NAME="MSDFS" >Chapter 4. Hosting a Microsoft Distributed File System tree on Samba</A ></H1 ><DIV @@ -3420,7 +3153,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN599" +NAME="AEN523" >4.1. Instructions</A ></H1 ><P @@ -3577,7 +3310,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN634" +NAME="AEN558" >4.1.1. Notes</A ></H2 ><P @@ -3610,16 +3343,769 @@ NAME="AEN634" CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN643" ->Chapter 5. Printing Support in Samba 2.2.x</A +NAME="UNIX-PERMISSIONS" +>Chapter 5. UNIX Permission Bits and Windows NT Access Control Lists</A ></H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A +NAME="AEN578" +>5.1. Viewing and changing UNIX permissions using the NT + security dialogs</A +></H1 +><P +>New in the Samba 2.0.4 release is the ability for Windows + NT clients to use their native security settings dialog box to + view and modify the underlying UNIX permissions.</P +><P +>Note that this ability is careful not to compromise + the security of the UNIX host Samba is running on, and + still obeys all the file permission rules that a Samba + administrator can set.</P +><P +>In Samba 2.0.4 and above the default value of the + parameter <A +HREF="smb.conf.5.html#NTACLSUPPORT" +TARGET="_top" +><TT +CLASS="PARAMETER" +><I +> nt acl support</I +></TT +></A +> has been changed from + <TT +CLASS="CONSTANT" +>false</TT +> to <TT +CLASS="CONSTANT" +>true</TT +>, so + manipulation of permissions is turned on by default.</P +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN587" +>5.2. How to view file security on a Samba share</A +></H1 +><P +>From an NT 4.0 client, single-click with the right + mouse button on any file or directory in a Samba mounted + drive letter or UNC path. When the menu pops-up, click + on the <EM +>Properties</EM +> entry at the bottom of + the menu. This brings up the normal file properties dialog + box, but with Samba 2.0.4 this will have a new tab along the top + marked <EM +>Security</EM +>. Click on this tab and you + will see three buttons, <EM +>Permissions</EM +>, + <EM +>Auditing</EM +>, and <EM +>Ownership</EM +>. + The <EM +>Auditing</EM +> button will cause either + an error message <SPAN +CLASS="ERRORNAME" +>A requested privilege is not held + by the client</SPAN +> to appear if the user is not the + NT Administrator, or a dialog which is intended to allow an + Administrator to add auditing requirements to a file if the + user is logged on as the NT Administrator. This dialog is + non-functional with a Samba share at this time, as the only + useful button, the <B +CLASS="COMMAND" +>Add</B +> button will not currently + allow a list of users to be seen.</P +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN598" +>5.3. Viewing file ownership</A +></H1 +><P +>Clicking on the <B +CLASS="COMMAND" +>"Ownership"</B +> button + brings up a dialog box telling you who owns the given file. The + owner name will be of the form :</P +><P +><B +CLASS="COMMAND" +>"SERVER\user (Long name)"</B +></P +><P +>Where <TT +CLASS="REPLACEABLE" +><I +>SERVER</I +></TT +> is the NetBIOS name of + the Samba server, <TT +CLASS="REPLACEABLE" +><I +>user</I +></TT +> is the user name of + the UNIX user who owns the file, and <TT +CLASS="REPLACEABLE" +><I +>(Long name)</I +></TT +> + is the descriptive string identifying the user (normally found in the + GECOS field of the UNIX password database). Click on the <B +CLASS="COMMAND" +>Close + </B +> button to remove this dialog.</P +><P +>If the parameter <TT +CLASS="PARAMETER" +><I +>nt acl support</I +></TT +> + is set to <TT +CLASS="CONSTANT" +>false</TT +> then the file owner will + be shown as the NT user <B +CLASS="COMMAND" +>"Everyone"</B +>.</P +><P +>The <B +CLASS="COMMAND" +>Take Ownership</B +> button will not allow + you to change the ownership of this file to yourself (clicking on + it will display a dialog box complaining that the user you are + currently logged onto the NT client cannot be found). The reason + for this is that changing the ownership of a file is a privileged + operation in UNIX, available only to the <EM +>root</EM +> + user. As clicking on this button causes NT to attempt to change + the ownership of a file to the current user logged into the NT + client this will not work with Samba at this time.</P +><P +>There is an NT chown command that will work with Samba + and allow a user with Administrator privilege connected + to a Samba 2.0.4 server as root to change the ownership of + files on both a local NTFS filesystem or remote mounted NTFS + or Samba drive. This is available as part of the <EM +>Seclib + </EM +> NT security library written by Jeremy Allison of + the Samba Team, available from the main Samba ftp site.</P +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN618" +>5.4. Viewing file or directory permissions</A +></H1 +><P +>The third button is the <B +CLASS="COMMAND" +>"Permissions"</B +> + button. Clicking on this brings up a dialog box that shows both + the permissions and the UNIX owner of the file or directory. + The owner is displayed in the form :</P +><P +><B +CLASS="COMMAND" +>"SERVER\user (Long name)"</B +></P +><P +>Where <TT +CLASS="REPLACEABLE" +><I +>SERVER</I +></TT +> is the NetBIOS name of + the Samba server, <TT +CLASS="REPLACEABLE" +><I +>user</I +></TT +> is the user name of + the UNIX user who owns the file, and <TT +CLASS="REPLACEABLE" +><I +>(Long name)</I +></TT +> + is the descriptive string identifying the user (normally found in the + GECOS field of the UNIX password database).</P +><P +>If the parameter <TT +CLASS="PARAMETER" +><I +>nt acl support</I +></TT +> + is set to <TT +CLASS="CONSTANT" +>false</TT +> then the file owner will + be shown as the NT user <B +CLASS="COMMAND" +>"Everyone"</B +> and the + permissions will be shown as NT "Full Control".</P +><P +>The permissions field is displayed differently for files + and directories, so I'll describe the way file permissions + are displayed first.</P +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN633" +>5.4.1. File Permissions</A +></H2 +><P +>The standard UNIX user/group/world triple and + the corresponding "read", "write", "execute" permissions + triples are mapped by Samba into a three element NT ACL + with the 'r', 'w', and 'x' bits mapped into the corresponding + NT permissions. The UNIX world permissions are mapped into + the global NT group <B +CLASS="COMMAND" +>Everyone</B +>, followed + by the list of permissions allowed for UNIX world. The UNIX + owner and group permissions are displayed as an NT + <B +CLASS="COMMAND" +>user</B +> icon and an NT <B +CLASS="COMMAND" +>local + group</B +> icon respectively followed by the list + of permissions allowed for the UNIX user and group.</P +><P +>As many UNIX permission sets don't map into common + NT names such as <B +CLASS="COMMAND" +>"read"</B +>, <B +CLASS="COMMAND" +> "change"</B +> or <B +CLASS="COMMAND" +>"full control"</B +> then + usually the permissions will be prefixed by the words <B +CLASS="COMMAND" +> "Special Access"</B +> in the NT display list.</P +><P +>But what happens if the file has no permissions allowed + for a particular UNIX user group or world component ? In order + to allow "no permissions" to be seen and modified then Samba + overloads the NT <B +CLASS="COMMAND" +>"Take Ownership"</B +> ACL attribute + (which has no meaning in UNIX) and reports a component with + no permissions as having the NT <B +CLASS="COMMAND" +>"O"</B +> bit set. + This was chosen of course to make it look like a zero, meaning + zero permissions. More details on the decision behind this will + be given below.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN647" +>5.4.2. Directory Permissions</A +></H2 +><P +>Directories on an NT NTFS file system have two + different sets of permissions. The first set of permissions + is the ACL set on the directory itself, this is usually displayed + in the first set of parentheses in the normal <B +CLASS="COMMAND" +>"RW"</B +> + NT style. This first set of permissions is created by Samba in + exactly the same way as normal file permissions are, described + above, and is displayed in the same way.</P +><P +>The second set of directory permissions has no real meaning + in the UNIX permissions world and represents the <B +CLASS="COMMAND" +> "inherited"</B +> permissions that any file created within + this directory would inherit.</P +><P +>Samba synthesises these inherited permissions for NT by + returning as an NT ACL the UNIX permission mode that a new file + created by Samba on this share would receive.</P +></DIV +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A NAME="AEN654" ->5.1. Introduction</A +>5.5. Modifying file or directory permissions</A +></H1 +><P +>Modifying file and directory permissions is as simple + as changing the displayed permissions in the dialog box, and + clicking the <B +CLASS="COMMAND" +>OK</B +> button. However, there are + limitations that a user needs to be aware of, and also interactions + with the standard Samba permission masks and mapping of DOS + attributes that need to also be taken into account.</P +><P +>If the parameter <TT +CLASS="PARAMETER" +><I +>nt acl support</I +></TT +> + is set to <TT +CLASS="CONSTANT" +>false</TT +> then any attempt to set + security permissions will fail with an <B +CLASS="COMMAND" +>"Access Denied" + </B +> message.</P +><P +>The first thing to note is that the <B +CLASS="COMMAND" +>"Add"</B +> + button will not return a list of users in Samba 2.0.4 (it will give + an error message of <B +CLASS="COMMAND" +>"The remote procedure call failed + and did not execute"</B +>). This means that you can only + manipulate the current user/group/world permissions listed in + the dialog box. This actually works quite well as these are the + only permissions that UNIX actually has.</P +><P +>If a permission triple (either user, group, or world) + is removed from the list of permissions in the NT dialog box, + then when the <B +CLASS="COMMAND" +>"OK"</B +> button is pressed it will + be applied as "no permissions" on the UNIX side. If you then + view the permissions again the "no permissions" entry will appear + as the NT <B +CLASS="COMMAND" +>"O"</B +> flag, as described above. This + allows you to add permissions back to a file or directory once + you have removed them from a triple component.</P +><P +>As UNIX supports only the "r", "w" and "x" bits of + an NT ACL then if other NT security attributes such as "Delete + access" are selected then they will be ignored when applied on + the Samba server.</P +><P +>When setting permissions on a directory the second + set of permissions (in the second set of parentheses) is + by default applied to all files within that directory. If this + is not what you want you must uncheck the <B +CLASS="COMMAND" +>"Replace + permissions on existing files"</B +> checkbox in the NT + dialog before clicking <B +CLASS="COMMAND" +>"OK"</B +>.</P +><P +>If you wish to remove all permissions from a + user/group/world component then you may either highlight the + component and click the <B +CLASS="COMMAND" +>"Remove"</B +> button, + or set the component to only have the special <B +CLASS="COMMAND" +>"Take + Ownership"</B +> permission (displayed as <B +CLASS="COMMAND" +>"O" + </B +>) highlighted.</P +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN676" +>5.6. Interaction with the standard Samba create mask + parameters</A +></H1 +><P +>Note that with Samba 2.0.5 there are four new parameters + to control this interaction. These are :</P +><P +><TT +CLASS="PARAMETER" +><I +>security mask</I +></TT +></P +><P +><TT +CLASS="PARAMETER" +><I +>force security mode</I +></TT +></P +><P +><TT +CLASS="PARAMETER" +><I +>directory security mask</I +></TT +></P +><P +><TT +CLASS="PARAMETER" +><I +>force directory security mode</I +></TT +></P +><P +>Once a user clicks <B +CLASS="COMMAND" +>"OK"</B +> to apply the + permissions Samba maps the given permissions into a user/group/world + r/w/x triple set, and then will check the changed permissions for a + file against the bits set in the <A +HREF="smb.conf.5.html#SECURITYMASK" +TARGET="_top" +> + <TT +CLASS="PARAMETER" +><I +>security mask</I +></TT +></A +> parameter. Any bits that + were changed that are not set to '1' in this parameter are left alone + in the file permissions.</P +><P +>Essentially, zero bits in the <TT +CLASS="PARAMETER" +><I +>security mask</I +></TT +> + mask may be treated as a set of bits the user is <EM +>not</EM +> + allowed to change, and one bits are those the user is allowed to change. + </P +><P +>If not set explicitly this parameter is set to the same value as + the <A +HREF="smb.conf.5.html#CREATEMASK" +TARGET="_top" +><TT +CLASS="PARAMETER" +><I +>create mask + </I +></TT +></A +> parameter to provide compatibility with Samba 2.0.4 + where this permission change facility was introduced. To allow a user to + modify all the user/group/world permissions on a file, set this parameter + to 0777.</P +><P +>Next Samba checks the changed permissions for a file against + the bits set in the <A +HREF="smb.conf.5.html#FORCESECURITYMODE" +TARGET="_top" +> <TT +CLASS="PARAMETER" +><I +>force security mode</I +></TT +></A +> parameter. Any bits + that were changed that correspond to bits set to '1' in this parameter + are forced to be set.</P +><P +>Essentially, bits set in the <TT +CLASS="PARAMETER" +><I +>force security mode + </I +></TT +> parameter may be treated as a set of bits that, when + modifying security on a file, the user has always set to be 'on'.</P +><P +>If not set explicitly this parameter is set to the same value + as the <A +HREF="smb.conf.5.html#FORCECREATEMODE" +TARGET="_top" +><TT +CLASS="PARAMETER" +><I +>force + create mode</I +></TT +></A +> parameter to provide compatibility + with Samba 2.0.4 where the permission change facility was introduced. + To allow a user to modify all the user/group/world permissions on a file + with no restrictions set this parameter to 000.</P +><P +>The <TT +CLASS="PARAMETER" +><I +>security mask</I +></TT +> and <TT +CLASS="PARAMETER" +><I +>force + security mode</I +></TT +> parameters are applied to the change + request in that order.</P +><P +>For a directory Samba will perform the same operations as + described above for a file except using the parameter <TT +CLASS="PARAMETER" +><I +> directory security mask</I +></TT +> instead of <TT +CLASS="PARAMETER" +><I +>security + mask</I +></TT +>, and <TT +CLASS="PARAMETER" +><I +>force directory security mode + </I +></TT +> parameter instead of <TT +CLASS="PARAMETER" +><I +>force security mode + </I +></TT +>.</P +><P +>The <TT +CLASS="PARAMETER" +><I +>directory security mask</I +></TT +> parameter + by default is set to the same value as the <TT +CLASS="PARAMETER" +><I +>directory mask + </I +></TT +> parameter and the <TT +CLASS="PARAMETER" +><I +>force directory security + mode</I +></TT +> parameter by default is set to the same value as + the <TT +CLASS="PARAMETER" +><I +>force directory mode</I +></TT +> parameter to provide + compatibility with Samba 2.0.4 where the permission change facility + was introduced.</P +><P +>In this way Samba enforces the permission restrictions that + an administrator can set on a Samba share, whilst still allowing users + to modify the permission bits within that restriction.</P +><P +>If you want to set up a share that allows users full control + in modifying the permission bits on their files and directories and + doesn't force any particular bits to be set 'on', then set the following + parameters in the <A +HREF="smb.conf.5.html" +TARGET="_top" +><TT +CLASS="FILENAME" +>smb.conf(5) + </TT +></A +> file in that share specific section :</P +><P +><TT +CLASS="PARAMETER" +><I +>security mask = 0777</I +></TT +></P +><P +><TT +CLASS="PARAMETER" +><I +>force security mode = 0</I +></TT +></P +><P +><TT +CLASS="PARAMETER" +><I +>directory security mask = 0777</I +></TT +></P +><P +><TT +CLASS="PARAMETER" +><I +>force directory security mode = 0</I +></TT +></P +><P +>As described, in Samba 2.0.4 the parameters :</P +><P +><TT +CLASS="PARAMETER" +><I +>create mask</I +></TT +></P +><P +><TT +CLASS="PARAMETER" +><I +>force create mode</I +></TT +></P +><P +><TT +CLASS="PARAMETER" +><I +>directory mask</I +></TT +></P +><P +><TT +CLASS="PARAMETER" +><I +>force directory mode</I +></TT +></P +><P +>were used instead of the parameters discussed here.</P +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN740" +>5.7. Interaction with the standard Samba file attribute + mapping</A +></H1 +><P +>Samba maps some of the DOS attribute bits (such as "read + only") into the UNIX permissions of a file. This means there can + be a conflict between the permission bits set via the security + dialog and the permission bits set by the file attribute mapping. + </P +><P +>One way this can show up is if a file has no UNIX read access + for the owner it will show up as "read only" in the standard + file attributes tabbed dialog. Unfortunately this dialog is + the same one that contains the security info in another tab.</P +><P +>What this can mean is that if the owner changes the permissions + to allow themselves read access using the security dialog, clicks + <B +CLASS="COMMAND" +>"OK"</B +> to get back to the standard attributes tab + dialog, and then clicks <B +CLASS="COMMAND" +>"OK"</B +> on that dialog, then + NT will set the file permissions back to read-only (as that is what + the attributes still say in the dialog). This means that after setting + permissions and clicking <B +CLASS="COMMAND" +>"OK"</B +> to get back to the + attributes dialog you should always hit <B +CLASS="COMMAND" +>"Cancel"</B +> + rather than <B +CLASS="COMMAND" +>"OK"</B +> to ensure that your changes + are not overridden.</P +></DIV +></DIV +><DIV +CLASS="CHAPTER" +><HR><H1 +><A +NAME="PRINTING" +>Chapter 6. Printing Support in Samba 2.2.x</A +></H1 +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN761" +>6.1. Introduction</A ></H1 ><P >Beginning with the 2.2.0 release, Samba supports @@ -3702,8 +4188,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN676" ->5.2. Configuration</A +NAME="AEN783" +>6.2. Configuration</A ></H1 ><DIV CLASS="WARNING" @@ -3770,8 +4256,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN687" ->5.2.1. Creating [print$]</A +NAME="AEN794" +>6.2.1. Creating [print$]</A ></H2 ><P >In order to support the uploading of printer driver @@ -3781,7 +4267,8 @@ the name is very important (print$ is the service used by Windows NT print servers to provide support for printer driver download).</P ><P ->You should modify the server's smb.conf file to create the +>You should modify the server's smb.conf file to add the global +parameters and to create the following file share (of course, some of the parameter values, such as 'path' are arbitrary and should be replaced with appropriate values for your site):</P @@ -3794,7 +4281,13 @@ WIDTH="100%" ><TD ><PRE CLASS="PROGRAMLISTING" ->[print$] +>[global] + ; members of the ntadmin group should be able + ; to add drivers and set printer properties + ; root is implicitly a 'printer admin' + printer admin = @ntadmin + +[print$] path = /usr/local/samba/printers guest ok = yes browseable = yes @@ -3804,7 +4297,7 @@ CLASS="PROGRAMLISTING" ; sure this account can copy files to the share. If this ; is setup to a non-root account, then it should also exist ; as a 'printer admin' - write list = ntadmin</PRE + write list = @ntadmin,root</PRE ></TD ></TR ></TABLE @@ -3964,8 +4457,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN722" ->5.2.2. Setting Drivers for Existing Printers</A +NAME="AEN829" +>6.2.2. Setting Drivers for Existing Printers</A ></H2 ><P >The initial listing of printers in the Samba host's @@ -4036,8 +4529,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN739" ->5.2.3. Support a large number of printers</A +NAME="AEN846" +>6.2.3. Support a large number of printers</A ></H2 ><P >One issue that has arisen during the development @@ -4111,8 +4604,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN750" ->5.2.4. Adding New Printers via the Windows NT APW</A +NAME="AEN857" +>6.2.4. Adding New Printers via the Windows NT APW</A ></H2 ><P >By default, Samba offers all printer shares defined in <TT @@ -4128,7 +4621,7 @@ Add Printer Wizard icon. The APW will be show only if</P ><P >The connected user is able to successfully execute an OpenPrinterEx(\\server) with administrative - priviledges (i.e. root or <TT + privileges (i.e. root or <TT CLASS="PARAMETER" ><I >printer admin</I @@ -4217,8 +4710,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN775" ->5.2.5. Samba and Printer Ports</A +NAME="AEN882" +>6.2.5. Samba and Printer Ports</A ></H2 ><P >Windows NT/2000 print servers associate a port with each printer. These normally @@ -4254,8 +4747,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN783" ->5.3. The Imprints Toolset</A +NAME="AEN890" +>6.3. The Imprints Toolset</A ></H1 ><P >The Imprints tool set provides a UNIX equivalent of the @@ -4272,8 +4765,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN787" ->5.3.1. What is Imprints?</A +NAME="AEN894" +>6.3.1. What is Imprints?</A ></H2 ><P >Imprints is a collection of tools for supporting the goals @@ -4304,8 +4797,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN797" ->5.3.2. Creating Printer Driver Packages</A +NAME="AEN904" +>6.3.2. Creating Printer Driver Packages</A ></H2 ><P >The process of creating printer driver packages is beyond @@ -4320,8 +4813,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN800" ->5.3.3. The Imprints server</A +NAME="AEN907" +>6.3.3. The Imprints server</A ></H2 ><P >The Imprints server is really a database server that @@ -4340,8 +4833,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN804" ->5.3.4. The Installation Client</A +NAME="AEN911" +>6.3.4. The Installation Client</A ></H2 ><P >More information regarding the Imprints installation client @@ -4410,7 +4903,7 @@ foreach (supported architecture for a given driver) the Imprints tool set was the name space issues between various supported client architectures. For example, Windows NT includes a driver named "Apple LaserWriter II NTX v51.8" - and Windows 95 callsits version of this driver "Apple + and Windows 95 calls its version of this driver "Apple LaserWriter II NTX"</P ><P >The problem is how to know what client drivers have @@ -4443,8 +4936,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN826" ->5.4. <A +NAME="AEN933" +>6.4. <A NAME="MIGRATION" ></A >Migration to from Samba 2.0.x to 2.2.x</A @@ -4460,7 +4953,7 @@ it will remember the server as a LanMan printer server. Upgrading the Samba host to 2.2 makes support for MSRPC printing possible, but the NT client will still remember the previous setting.</P ><P ->In order to give an NT client printing "amesia" (only necessary if you +>In order to give an NT client printing "amnesia" (only necessary if you want to use the newer MSRPC printing functionality in Samba), delete the registry keys associated with the print server contained in <TT @@ -4620,16 +5113,16 @@ TARGET="_top" CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN870" ->Chapter 6. security = domain in Samba 2.x</A +NAME="DOMAIN-SECURITY" +>Chapter 7. security = domain in Samba 2.x</A ></H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN888" ->6.1. Joining an NT Domain with Samba 2.2</A +NAME="AEN995" +>7.1. Joining an NT Domain with Samba 2.2</A ></H1 ><P >In order for a Samba-2 server to join an NT domain, @@ -4855,8 +5348,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN952" ->6.2. Samba and Windows 2000 Domains</A +NAME="AEN1059" +>7.2. Samba and Windows 2000 Domains</A ></H1 ><P >Many people have asked regarding the state of Samba's ability to participate in @@ -4880,8 +5373,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN957" ->6.3. Why is this better than security = server?</A +NAME="AEN1064" +>7.3. Why is this better than security = server?</A ></H1 ><P >Currently, domain security in Samba doesn't free you from @@ -4966,21 +5459,21 @@ TARGET="_top" CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN973" ->Chapter 7. How to Configure Samba 2.2 as a Primary Domain Controller</A +NAME="SAMBA-PDC" +>Chapter 8. How to Configure Samba 2.2 as a Primary Domain Controller</A ></H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN990" ->7.1. Prerequisite Reading</A +NAME="AEN1097" +>8.1. Prerequisite Reading</A ></H1 ><P ->Before you continue readingin this chapter, please make sure +>Before you continue reading in this chapter, please make sure that you are comfortable with configuring basic files services -in smb.conf and how to enable and administrate password +in smb.conf and how to enable and administer password encryption in Samba. Theses two topics are covered in the <A HREF="smb.conf.5.html" @@ -4991,7 +5484,7 @@ CLASS="FILENAME" ></A > manpage and the <A -HREF="EMCRYPTION.html" +HREF="ENCRYPTION.html" TARGET="_top" >Encryption chapter</A > @@ -5002,8 +5495,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN996" ->7.2. Background</A +NAME="AEN1103" +>8.2. Background</A ></H1 ><DIV CLASS="NOTE" @@ -5016,12 +5509,12 @@ CLASS="NOTE" >Author's Note :</EM > This document is a combination of David Bannon's Samba 2.2 PDC HOWTO and the Samba NT Domain FAQ. -Both documents are superceeded by this one.</P +Both documents are superseded by this one.</P ></BLOCKQUOTE ></DIV ><P >Version of Samba prior to release 2.2 had marginal capabilities to -act as a Windows NT 4.0 Primary Domain Controller (PDC). Beginning with +act as a Windows NT 4.0 Primary DOmain Controller (PDC). Beginning with Samba 2.2.0, we are proud to announce official support for Windows NT 4.0 style domain logons from Windows NT 4.0 (through SP6) and Windows 2000 (through SP1) clients. This article outlines the steps necessary for configuring Samba @@ -5159,8 +5652,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1036" ->7.3. Configuring the Samba Domain Controller</A +NAME="AEN1145" +>8.3. Configuring the Samba Domain Controller</A ></H1 ><P >The first step in creating a working Samba PDC is to @@ -5381,15 +5874,15 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1079" ->7.4. Creating Machine Trust Accounts and Joining Clients +NAME="AEN1188" +>8.4. Creating Machine Trust Accounts and Joining Clients to the Domain</A ></H1 ><P >A machine trust account is a samba user account owned by a computer. The account password acts as the shared secret for secure communication with the Domain Controller. This is a security feature -to prevent an unauthorized machine with the same netbios name from +to prevent an unauthorized machine with the same NetBIOS name from joining the domain and gaining access to domain user/group accounts. Hence a Windows 9x host is never a true member of a domain because it does not posses a machine trust account, and thus has no shared secret with the DC.</P @@ -5422,7 +5915,7 @@ CLASS="FILENAME" ><P > Manual creation before joining the client to the domain. In this case, the password is set to a known value -- the lower case of the - machine's netbios name. + machine's NetBIOS name. </P ></LI ><LI @@ -5439,8 +5932,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1093" ->7.4.1. Manually creating machine trust accounts</A +NAME="AEN1202" +>8.4.1. Manually creating machine trust accounts</A ></H2 ><P >The first step in creating a machine trust account by hand is to @@ -5509,7 +6002,7 @@ CLASS="REPLACEABLE" >machine_name</I ></TT > absolutely must be -the netbios name of the pc to be added to the domain. The "$" must append the netbios +the NetBIOS name of the pc to be added to the domain. The "$" must append the NetBIOS name of the pc or samba will not recognize this as a machine account</P ><P >Now that the UNIX account has been created, the next step is to create @@ -5539,7 +6032,7 @@ CLASS="REPLACEABLE" ><I >machine_name</I ></TT -> is the machine's netbios +> is the machine's NetBIOS name. </P ><DIV CLASS="WARNING" @@ -5565,7 +6058,7 @@ ALIGN="LEFT" the "Server Manager". From the time at which the account is created to the time which th client joins the domain and changes the password, your domain is vulnerable to an intruder joining your domain using a - a machine with the same netbios name. A PDC inherently trusts + a machine with the same NetBIOS name. A PDC inherently trusts members of the domain and will serve out a large degree of user information to such clients. You have been warned! </P @@ -5579,8 +6072,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1121" ->7.4.2. Creating machine trust accounts "on the fly"</A +NAME="AEN1230" +>8.4.2. Creating machine trust accounts "on the fly"</A ></H2 ><P >The second, and most recommended way of creating machine trust accounts @@ -5627,8 +6120,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1132" ->7.5. Common Problems and Errors</A +NAME="AEN1241" +>8.5. Common Problems and Errors</A ></H1 ><P ></P @@ -5746,8 +6239,8 @@ CLASS="PARAMETER" have not been created correctly. Make sure that you have the entry correct for the machine account in smbpasswd file on the Samba PDC. If you added the account using an editor rather than using the smbpasswd - utility, make sure that the account name is the machine netbios name - with a '$' appended to it ( ie. computer_name$ ). There must be an entry + utility, make sure that the account name is the machine NetBIOS name + with a '$' appended to it ( i.e. computer_name$ ). There must be an entry in both /etc/passwd and the smbpasswd file. Some people have reported that inconsistent subnet masks between the Samba server and the NT client have caused this problem. Make sure that these are consistent @@ -5772,7 +6265,7 @@ CLASS="PARAMETER" CLASS="COMMAND" >smbpasswd -e %user%</B ->, this is normaly done, when you create an account. +>, this is normally done, when you create an account. </P ><P > In order to work around this problem in 2.2.0, configure the @@ -5826,8 +6319,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1180" ->7.6. System Policies and Profiles</A +NAME="AEN1289" +>8.6. System Policies and Profiles</A ></H1 ><P >Much of the information necessary to implement System Policies and @@ -5890,7 +6383,7 @@ CLASS="FILENAME" CLASS="COMMAND" >servicepackname /x</B >, - ie thats <B + i.e. that's <B CLASS="COMMAND" >Nt4sp6ai.exe /x</B > for service pack 6a. The policy editor, @@ -5983,8 +6476,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1224" ->7.7. What other help can I get ?</A +NAME="AEN1333" +>8.7. What other help can I get ?</A ></H1 ><P >There are many sources of information available in the form @@ -6003,7 +6496,7 @@ general SMB topics such as browsing.</P </P ><P > One of the best diagnostic tools for debugging problems is Samba itself. - You can use the -d option for both smbd and nmbd to specifiy what + You can use the -d option for both smbd and nmbd to specify what 'debug level' at which to run. See the man pages on smbd, nmbd and smb.conf for more information on debugging options. The debug level can range from 1 (the default) to 10 (100 for debugging passwords). @@ -6059,7 +6552,7 @@ TARGET="_top" (aka. netmon) is available on the Microsoft Developer Network CD's, the Windows NT Server install CD and the SMS CD's. The version of netmon that ships with SMS allows for dumping packets between any two - computers (ie. placing the network interface in promiscuous mode). + computers (i.e. placing the network interface in promiscuous mode). The version on the NT Server install CD will only allow monitoring of network traffic directed to the local NT box and broadcasts on the local subnet. Be aware that Ethereal can read and write netmon @@ -6311,7 +6804,7 @@ TARGET="_top" ><LI ><P > Don't cross post. Work out which is the best list to post to - and see what happens, ie don't post to both samba-ntdom and samba-technical. + and see what happens, i.e. don't post to both samba-ntdom and samba-technical. Many people active on the lists subscribe to more than one list and get annoyed to see the same message two or more times. Often someone will see a message and thinking it would be better dealt @@ -6379,8 +6872,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1338" ->7.8. Domain Control for Windows 9x/ME</A +NAME="AEN1447" +>8.8. Domain Control for Windows 9x/ME</A ></H1 ><DIV CLASS="NOTE" @@ -6417,7 +6910,7 @@ profiles for MS Windows for workgroups and MS Windows 9X clients.</P logon server. The first one to reply gets the job, and validates its password using whatever mechanism the Samba administrator has installed. It is possible (but very stupid) to create a domain where the user -database is not shared between servers, ie they are effectively workgroup +database is not shared between servers, i.e. they are effectively workgroup servers advertising themselves as participating in a domain. This demonstrates how authentication is quite different from but closely involved with domains.</P @@ -6497,7 +6990,7 @@ TYPE="1" ><LI ><P > The client then connects to the user's home share and searches for the - user's profile. As it turns out, you can specify the users home share as + user's profile. As it turns out, you can specify the user's home share as a sharename and path. For example, \\server\fred\.profile. If the profiles are found, they are implemented. </P @@ -6515,8 +7008,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1368" ->7.8.1. Configuration Instructions: Network Logons</A +NAME="AEN1477" +>8.8.1. Configuration Instructions: Network Logons</A ></H2 ><P >To use domain logons and profiles you need to do the following:</P @@ -6625,7 +7118,7 @@ CLASS="PROGRAMLISTING" ></LI ><LI ><P -> you will probabaly find that your clients automatically mount the +> you will probably find that your clients automatically mount the \\SERVER\NETLOGON share as drive z: while logging in. You can put some useful programs there to execute from the batch files. </P @@ -6675,7 +7168,7 @@ or not Samba must be the domain master browser for its workgroup when operating as a DC. While it may technically be possible to configure a server as such (after all, browsing and domain logons are two distinctly different functions), it is not a good idea to -so. You should remember that the DC must register the DOMAIN#1b netbios +so. You should remember that the DC must register the DOMAIN#1b NetBIOS name. This is the name used by Windows clients to locate the DC. Windows clients do not distinguish between the DC and the DMB. For this reason, it is very wise to configure the Samba DC as the DMB.</P @@ -6704,8 +7197,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1402" ->7.8.2. Configuration Instructions: Setting up Roaming User Profiles</A +NAME="AEN1511" +>8.8.2. Configuration Instructions: Setting up Roaming User Profiles</A ></H2 ><DIV CLASS="WARNING" @@ -6740,7 +7233,7 @@ Win9X and WinNT clients implement these features.</P ><P >Win9X clients send a NetUserGetInfo request to the server to get the user's profiles location. However, the response does not have room for a separate -profiles location field, only the users home share. This means that Win9X +profiles location field, only the user's home share. This means that Win9X profiles are restricted to being in the user's home directory.</P ><P >WinNT clients send a NetSAMLogon RPC request, which contains many fields, @@ -6751,8 +7244,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1410" ->7.8.2.1. Windows NT Configuration</A +NAME="AEN1519" +>8.8.2.1. Windows NT Configuration</A ></H3 ><P >To support WinNT clients, inn the [global] section of smb.conf set the @@ -6795,8 +7288,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1418" ->7.8.2.2. Windows 9X Configuration</A +NAME="AEN1527" +>8.8.2.2. Windows 9X Configuration</A ></H3 ><P >To support Win9X clients, you must use the "logon home" parameter. Samba has @@ -6835,8 +7328,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1426" ->7.8.2.3. Win9X and WinNT Configuration</A +NAME="AEN1535" +>8.8.2.3. Win9X and WinNT Configuration</A ></H3 ><P >You can support profiles for both Win9X and WinNT clients by setting both the @@ -6873,8 +7366,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1433" ->7.8.2.4. Windows 9X Profile Setup</A +NAME="AEN1542" +>8.8.2.4. Windows 9X Profile Setup</A ></H3 ><P >When a user first logs in on Windows 9X, the file user.DAT is created, @@ -6997,7 +7490,7 @@ TYPE="1" ></LI ><LI ><P -> search for the user's .PWL password-cacheing file in the c:\windows +> search for the user's .PWL password-caching file in the c:\windows directory, and delete it. </P ></LI @@ -7029,8 +7522,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1469" ->7.8.2.5. Windows NT Workstation 4.0</A +NAME="AEN1578" +>8.8.2.5. Windows NT Workstation 4.0</A ></H3 ><P >When a user first logs in to a Windows NT Workstation, the profile @@ -7091,11 +7584,11 @@ case, or whether there is some configuration issue, as yet unknown, that makes NT Workstation _think_ that the link is a slow one is a matter to be resolved].</P ><P ->[lkcl 20aug97 - after samba digest correspondance, one user found, and +>[lkcl 20aug97 - after samba digest correspondence, one user found, and another confirmed, that profiles cannot be loaded from a samba server unless "security = user" and "encrypt passwords = yes" (see the file ENCRYPTION.txt) or "security = server" and "password server = ip.address. -of.yourNTserver" are used. either of these options will allow the NT +of.yourNTserver" are used. Either of these options will allow the NT workstation to access the samba server using LAN manager encrypted passwords, without the user intervention normally required by NT workstation for clear-text passwords].</P @@ -7111,8 +7604,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1482" ->7.8.2.6. Windows NT Server</A +NAME="AEN1591" +>8.8.2.6. Windows NT Server</A ></H3 ><P >There is nothing to stop you specifying any path that you like for the @@ -7125,8 +7618,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1485" ->7.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</A +NAME="AEN1594" +>8.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</A ></H3 ><DIV CLASS="WARNING" @@ -7190,8 +7683,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1495" ->7.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +NAME="AEN1604" +>8.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></H1 ><DIV CLASS="WARNING" @@ -7287,7 +7780,7 @@ plain Servers.</P ><P >The User database is called the SAM (Security Access Manager) database and is used for all user authentication as well as for authentication of inter- -process authentication (ie: to ensure that the service action a user has +process authentication (i.e. to ensure that the service action a user has requested is permitted within the limits of that user's privileges).</P ><P >The Samba team have produced a utility that can dump the Windows NT SAM into @@ -7298,7 +7791,7 @@ to Samba systems.</P ><P >Windows for Workgroups, Windows 95, and Windows NT Workstations and Servers can participate in a Domain security system that is controlled by Windows NT -servers that have been correctly configured. At most every domain will have +servers that have been correctly configured. Almost every domain will have ONE Primary Domain Controller (PDC). It is desirable that each domain will have at least one Backup Domain Controller (BDC).</P ><P @@ -7311,16 +7804,16 @@ within its registry.</P CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN1520" ->Chapter 8. Unifed Logons between Windows NT and UNIX using Winbind</A +NAME="WINBIND" +>Chapter 9. Unified Logons between Windows NT and UNIX using Winbind</A ></H1 ><DIV CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1538" ->8.1. Abstract</A +NAME="AEN1647" +>9.1. Abstract</A ></H1 ><P >Integration of UNIX and Microsoft Windows NT through @@ -7329,7 +7822,7 @@ NAME="AEN1538" >winbind </EM >, a component of the Samba suite of programs as a - solution to the unied logon problem. Winbind uses a UNIX implementation + solution to the unified logon problem. Winbind uses a UNIX implementation of Microsoft RPC calls, Pluggable Authentication Modules, and the Name Service Switch to allow Windows NT domain users to appear and operate as UNIX users on a UNIX machine. This paper describes the winbind @@ -7341,8 +7834,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1542" ->8.2. Introduction</A +NAME="AEN1651" +>9.2. Introduction</A ></H1 ><P >It is well known that UNIX and Microsoft Windows NT have @@ -7360,7 +7853,7 @@ NAME="AEN1542" can lead to synchronization problems between the UNIX and Windows systems and confusion for users.</P ><P ->We divide the unifed logon problem for UNIX machines into +>We divide the unified logon problem for UNIX machines into three smaller problems:</P ><P ></P @@ -7387,7 +7880,7 @@ NAME="AEN1542" information on the UNIX machines and without creating additional tasks for the system administrator when maintaining users and groups on either system. The winbind system provides a simple - and elegant solution to all three components of the unifed logon + and elegant solution to all three components of the unified logon problem.</P ></DIV ><DIV @@ -7395,8 +7888,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1555" ->8.3. What Winbind Provides</A +NAME="AEN1664" +>9.3. What Winbind Provides</A ></H1 ><P >Winbind unifies UNIX and Windows NT account management by @@ -7437,8 +7930,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1562" ->8.3.1. Target Uses</A +NAME="AEN1671" +>9.3.1. Target Uses</A ></H2 ><P >Winbind is targeted at organizations that have an @@ -7461,8 +7954,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1566" ->8.4. How Winbind Works</A +NAME="AEN1675" +>9.4. How Winbind Works</A ></H1 ><P >The winbind system is designed around a client/server @@ -7481,8 +7974,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1571" ->8.4.1. Microsoft Remote Procedure Calls</A +NAME="AEN1680" +>9.4.1. Microsoft Remote Procedure Calls</A ></H2 ><P >Over the last two years, efforts have been underway @@ -7507,14 +8000,14 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1575" ->8.4.2. Name Service Switch</A +NAME="AEN1684" +>9.4.2. Name Service Switch</A ></H2 ><P >The Name Service Switch, or NSS, is a feature that is present in many UNIX operating systems. It allows system information such as hostnames, mail aliases and user information - to be resolved from dierent sources. For example, a standalone + to be resolved from different sources. For example, a standalone UNIX workstation may resolve system information from a series of flat files stored on the local lesystem. A networked workstation may first attempt to resolve system information from local files, @@ -7543,7 +8036,7 @@ CLASS="FILENAME" for a line which matches the service type being requested, for example the "passwd" service type is used when user or group names are looked up. This config line species which implementations - of that service should be tried andin what order. If the passwd + of that service should be tried and in what order. If the passwd config line is:</P ><P ><B @@ -7586,14 +8079,14 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1591" ->8.4.3. Pluggable Authentication Modules</A +NAME="AEN1700" +>9.4.3. Pluggable Authentication Modules</A ></H2 ><P >Pluggable Authentication Modules, also known as PAM, is a system for abstracting authentication and authorization technologies. With a PAM module it is possible to specify different - authentication methods for dierent system applications without + authentication methods for different system applications without having to recompile these applications. PAM is also useful for implementing a particular policy for authorization. For example, a system administrator may only allow console logins from users @@ -7608,7 +8101,7 @@ NAME="AEN1591" this change take eect directly on the Primary Domain Controller. </P ><P ->PAM is congured by providing control files in the directory +>PAM is configured by providing control files in the directory <TT CLASS="FILENAME" >/etc/pam.d/</TT @@ -7635,16 +8128,16 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1599" ->8.4.4. User and Group ID Allocation</A +NAME="AEN1708" +>9.4.4. User and Group ID Allocation</A ></H2 ><P >When a user or group is created under Windows NT - is it allocated a numerical relative identier (RID). This is - slightly dierent to UNIX which has a range of numbers which are + is it allocated a numerical relative identifier (RID). This is + slightly different to UNIX which has a range of numbers which are used to identify users, and the same range in which to identify groups. It is winbind's job to convert RIDs to UNIX id numbers and - vice versa. When winbind is congured it is given part of the UNIX + vice versa. When winbind is configured it is given part of the UNIX user id space and a part of the UNIX group id space in which to store Windows NT users and groups. If a Windows NT user is resolved for the first time, it is allocated the next UNIX id from @@ -7661,8 +8154,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1603" ->8.4.5. Result Caching</A +NAME="AEN1712" +>9.4.5. Result Caching</A ></H2 ><P >An active system can generate a lot of user and group @@ -7671,7 +8164,7 @@ NAME="AEN1603" by NT domain controllers. User or group information returned by a PDC is cached by winbind along with a sequence number also returned by the PDC. This sequence number is incremented by - Windows NT whenever any user or group information is modied. If + Windows NT whenever any user or group information is modified. If a cached entry has expired, the sequence number is requested from the PDC and compared against the sequence number of the cached entry. If the sequence numbers do not match, then the cached information @@ -7684,8 +8177,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1606" ->8.5. Installation and Configuration</A +NAME="AEN1715" +>9.5. Installation and Configuration</A ></H1 ><P >The easiest way to install winbind is by using the packages @@ -7705,7 +8198,7 @@ CLASS="FILENAME" CLASS="COMMAND" >winbindd(8)</B > man page which will provide you - with conguration information and give you sample conguration files. + with configuration information and give you sample configuration files. You may also wish to update the main Samba daemons smbd and nmbd) with a more recent development release, such as the recently announced Samba 2.2 alpha release.</P @@ -7715,8 +8208,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1612" ->8.6. Limitations</A +NAME="AEN1721" +>9.6. Limitations</A ></H1 ><P >Winbind has a number of limitations in its current @@ -7763,8 +8256,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1624" ->8.7. Conclusion</A +NAME="AEN1733" +>9.7. Conclusion</A ></H1 ><P >The winbind system, through the use of the Name Service @@ -7779,760 +8272,7 @@ NAME="AEN1624" CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN1627" ->Chapter 9. UNIX Permission Bits and WIndows NT Access Control Lists</A -></H1 -><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" -><A -NAME="AEN1638" ->9.1. Viewing and changing UNIX permissions using the NT - security dialogs</A -></H1 -><P ->New in the Samba 2.0.4 release is the ability for Windows - NT clients to use their native security settings dialog box to - view and modify the underlying UNIX permissions.</P -><P ->Note that this ability is careful not to compromise - the security of the UNIX host Samba is running on, and - still obeys all the file permission rules that a Samba - administrator can set.</P -><P ->In Samba 2.0.4 and above the default value of the - parameter <A -HREF="smb.conf.5.html#NTACLSUPPORT" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I -> nt acl support</I -></TT -></A -> has been changed from - <TT -CLASS="CONSTANT" ->false</TT -> to <TT -CLASS="CONSTANT" ->true</TT ->, so - manipulation of permissions is turned on by default.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" -><A -NAME="AEN1647" ->9.2. How to view file security on a Samba share</A -></H1 -><P ->From an NT 4.0 client, single-click with the right - mouse button on any file or directory in a Samba mounted - drive letter or UNC path. When the menu pops-up, click - on the <EM ->Properties</EM -> entry at the bottom of - the menu. This brings up the normal file properties dialog - box, but with Samba 2.0.4 this will have a new tab along the top - marked <EM ->Security</EM ->. Click on this tab and you - will see three buttons, <EM ->Permissions</EM ->, - <EM ->Auditing</EM ->, and <EM ->Ownership</EM ->. - The <EM ->Auditing</EM -> button will cause either - an error message <SPAN -CLASS="ERRORNAME" ->A requested privilege is not held - by the client</SPAN -> to appear if the user is not the - NT Administrator, or a dialog which is intended to allow an - Administrator to add auditing requirements to a file if the - user is logged on as the NT Administrator. This dialog is - non-functional with a Samba share at this time, as the only - useful button, the <B -CLASS="COMMAND" ->Add</B -> button will not currently - allow a list of users to be seen.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" -><A -NAME="AEN1658" ->9.3. Viewing file ownership</A -></H1 -><P ->Clicking on the <B -CLASS="COMMAND" ->"Ownership"</B -> button - brings up a dialog box telling you who owns the given file. The - owner name will be of the form :</P -><P -><B -CLASS="COMMAND" ->"SERVER\user (Long name)"</B -></P -><P ->Where <TT -CLASS="REPLACEABLE" -><I ->SERVER</I -></TT -> is the NetBIOS name of - the Samba server, <TT -CLASS="REPLACEABLE" -><I ->user</I -></TT -> is the user name of - the UNIX user who owns the file, and <TT -CLASS="REPLACEABLE" -><I ->(Long name)</I -></TT -> - is the discriptive string identifying the user (normally found in the - GECOS field of the UNIX password database). Click on the <B -CLASS="COMMAND" ->Close - </B -> button to remove this dialog.</P -><P ->If the parameter <TT -CLASS="PARAMETER" -><I ->nt acl support</I -></TT -> - is set to <TT -CLASS="CONSTANT" ->false</TT -> then the file owner will - be shown as the NT user <B -CLASS="COMMAND" ->"Everyone"</B ->.</P -><P ->The <B -CLASS="COMMAND" ->Take Ownership</B -> button will not allow - you to change the ownership of this file to yourself (clicking on - it will display a dialog box complaining that the user you are - currently logged onto the NT client cannot be found). The reason - for this is that changing the ownership of a file is a privilaged - operation in UNIX, available only to the <EM ->root</EM -> - user. As clicking on this button causes NT to attempt to change - the ownership of a file to the current user logged into the NT - client this will not work with Samba at this time.</P -><P ->There is an NT chown command that will work with Samba - and allow a user with Administrator privillage connected - to a Samba 2.0.4 server as root to change the ownership of - files on both a local NTFS filesystem or remote mounted NTFS - or Samba drive. This is available as part of the <EM ->Seclib - </EM -> NT security library written by Jeremy Allison of - the Samba Team, available from the main Samba ftp site.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" -><A -NAME="AEN1678" ->9.4. Viewing file or directory permissions</A -></H1 -><P ->The third button is the <B -CLASS="COMMAND" ->"Permissions"</B -> - button. Clicking on this brings up a dialog box that shows both - the permissions and the UNIX owner of the file or directory. - The owner is displayed in the form :</P -><P -><B -CLASS="COMMAND" ->"SERVER\user (Long name)"</B -></P -><P ->Where <TT -CLASS="REPLACEABLE" -><I ->SERVER</I -></TT -> is the NetBIOS name of - the Samba server, <TT -CLASS="REPLACEABLE" -><I ->user</I -></TT -> is the user name of - the UNIX user who owns the file, and <TT -CLASS="REPLACEABLE" -><I ->(Long name)</I -></TT -> - is the discriptive string identifying the user (normally found in the - GECOS field of the UNIX password database).</P -><P ->If the parameter <TT -CLASS="PARAMETER" -><I ->nt acl support</I -></TT -> - is set to <TT -CLASS="CONSTANT" ->false</TT -> then the file owner will - be shown as the NT user <B -CLASS="COMMAND" ->"Everyone"</B -> and the - permissions will be shown as NT "Full Control".</P -><P ->The permissions field is displayed differently for files - and directories, so I'll describe the way file permissions - are displayed first.</P -><DIV -CLASS="SECT2" -><HR><H2 -CLASS="SECT2" -><A -NAME="AEN1693" ->9.4.1. File Permissions</A -></H2 -><P ->The standard UNIX user/group/world triple and - the correspinding "read", "write", "execute" permissions - triples are mapped by Samba into a three element NT ACL - with the 'r', 'w', and 'x' bits mapped into the corresponding - NT permissions. The UNIX world permissions are mapped into - the global NT group <B -CLASS="COMMAND" ->Everyone</B ->, followed - by the list of permissions allowed for UNIX world. The UNIX - owner and group permissions are displayed as an NT - <B -CLASS="COMMAND" ->user</B -> icon and an NT <B -CLASS="COMMAND" ->local - group</B -> icon respectively followed by the list - of permissions allowed for the UNIX user and group.</P -><P ->As many UNIX permission sets don't map into common - NT names such as <B -CLASS="COMMAND" ->"read"</B ->, <B -CLASS="COMMAND" -> "change"</B -> or <B -CLASS="COMMAND" ->"full control"</B -> then - usually the permissions will be prefixed by the words <B -CLASS="COMMAND" -> "Special Access"</B -> in the NT display list.</P -><P ->But what happens if the file has no permissions allowed - for a particular UNIX user group or world component ? In order - to allow "no permissions" to be seen and modified then Samba - overloads the NT <B -CLASS="COMMAND" ->"Take Ownership"</B -> ACL attribute - (which has no meaning in UNIX) and reports a component with - no permissions as having the NT <B -CLASS="COMMAND" ->"O"</B -> bit set. - This was chosen of course to make it look like a zero, meaning - zero permissions. More details on the decision behind this will - be given below.</P -></DIV -><DIV -CLASS="SECT2" -><HR><H2 -CLASS="SECT2" -><A -NAME="AEN1707" ->9.4.2. Directory Permissions</A -></H2 -><P ->Directories on an NT NTFS file system have two - different sets of permissions. The first set of permissions - is the ACL set on the directory itself, this is usually displayed - in the first set of parentheses in the normal <B -CLASS="COMMAND" ->"RW"</B -> - NT style. This first set of permissions is created by Samba in - exactly the same way as normal file permissions are, described - above, and is displayed in the same way.</P -><P ->The second set of directory permissions has no real meaning - in the UNIX permissions world and represents the <B -CLASS="COMMAND" -> "inherited"</B -> permissions that any file created within - this directory would inherit.</P -><P ->Samba synthesises these inherited permissions for NT by - returning as an NT ACL the UNIX permission mode that a new file - created by Samba on this share would receive.</P -></DIV -></DIV -><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" -><A -NAME="AEN1714" ->9.5. Modifying file or directory permissions</A -></H1 -><P ->Modifying file and directory permissions is as simple - as changing the displayed permissions in the dialog box, and - clicking the <B -CLASS="COMMAND" ->OK</B -> button. However, there are - limitations that a user needs to be aware of, and also interactions - with the standard Samba permission masks and mapping of DOS - attributes that need to also be taken into account.</P -><P ->If the parameter <TT -CLASS="PARAMETER" -><I ->nt acl support</I -></TT -> - is set to <TT -CLASS="CONSTANT" ->false</TT -> then any attempt to set - security permissions will fail with an <B -CLASS="COMMAND" ->"Access Denied" - </B -> message.</P -><P ->The first thing to note is that the <B -CLASS="COMMAND" ->"Add"</B -> - button will not return a list of users in Samba 2.0.4 (it will give - an error message of <B -CLASS="COMMAND" ->"The remote proceedure call failed - and did not execute"</B ->). This means that you can only - manipulate the current user/group/world permissions listed in - the dialog box. This actually works quite well as these are the - only permissions that UNIX actually has.</P -><P ->If a permission triple (either user, group, or world) - is removed from the list of permissions in the NT dialog box, - then when the <B -CLASS="COMMAND" ->"OK"</B -> button is pressed it will - be applied as "no permissions" on the UNIX side. If you then - view the permissions again the "no permissions" entry will appear - as the NT <B -CLASS="COMMAND" ->"O"</B -> flag, as described above. This - allows you to add permissions back to a file or directory once - you have removed them from a triple component.</P -><P ->As UNIX supports only the "r", "w" and "x" bits of - an NT ACL then if other NT security attributes such as "Delete - access" are selected then they will be ignored when applied on - the Samba server.</P -><P ->When setting permissions on a directory the second - set of permissions (in the second set of parentheses) is - by default applied to all files within that directory. If this - is not what you want you must uncheck the <B -CLASS="COMMAND" ->"Replace - permissions on existing files"</B -> checkbox in the NT - dialog before clicking <B -CLASS="COMMAND" ->"OK"</B ->.</P -><P ->If you wish to remove all permissions from a - user/group/world component then you may either highlight the - component and click the <B -CLASS="COMMAND" ->"Remove"</B -> button, - or set the component to only have the special <B -CLASS="COMMAND" ->"Take - Ownership"</B -> permission (dsplayed as <B -CLASS="COMMAND" ->"O" - </B ->) highlighted.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" -><A -NAME="AEN1736" ->9.6. Interaction with the standard Samba create mask - parameters</A -></H1 -><P ->Note that with Samba 2.0.5 there are four new parameters - to control this interaction. These are :</P -><P -><TT -CLASS="PARAMETER" -><I ->security mask</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force security mode</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->directory security mask</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force directory security mode</I -></TT -></P -><P ->Once a user clicks <B -CLASS="COMMAND" ->"OK"</B -> to apply the - permissions Samba maps the given permissions into a user/group/world - r/w/x triple set, and then will check the changed permissions for a - file against the bits set in the <A -HREF="smb.conf.5.html#SECURITYMASK" -TARGET="_top" -> - <TT -CLASS="PARAMETER" -><I ->security mask</I -></TT -></A -> parameter. Any bits that - were changed that are not set to '1' in this parameter are left alone - in the file permissions.</P -><P ->Essentially, zero bits in the <TT -CLASS="PARAMETER" -><I ->security mask</I -></TT -> - mask may be treated as a set of bits the user is <EM ->not</EM -> - allowed to change, and one bits are those the user is allowed to change. - </P -><P ->If not set explicitly this parameter is set to the same value as - the <A -HREF="smb.conf.5.html#CREATEMASK" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->create mask - </I -></TT -></A -> parameter to provide compatibility with Samba 2.0.4 - where this permission change facility was introduced. To allow a user to - modify all the user/group/world permissions on a file, set this parameter - to 0777.</P -><P ->Next Samba checks the changed permissions for a file against - the bits set in the <A -HREF="smb.conf.5.html#FORCESECURITYMODE" -TARGET="_top" -> <TT -CLASS="PARAMETER" -><I ->force security mode</I -></TT -></A -> parameter. Any bits - that were changed that correspond to bits set to '1' in this parameter - are forced to be set.</P -><P ->Essentially, bits set in the <TT -CLASS="PARAMETER" -><I ->force security mode - </I -></TT -> parameter may be treated as a set of bits that, when - modifying security on a file, the user has always set to be 'on'.</P -><P ->If not set explicitly this parameter is set to the same value - as the <A -HREF="smb.conf.5.html#FORCECREATEMODE" -TARGET="_top" -><TT -CLASS="PARAMETER" -><I ->force - create mode</I -></TT -></A -> parameter to provide compatibility - with Samba 2.0.4 where the permission change facility was introduced. - To allow a user to modify all the user/group/world permissions on a file, - with no restrictions set this parameter to 000.</P -><P ->The <TT -CLASS="PARAMETER" -><I ->security mask</I -></TT -> and <TT -CLASS="PARAMETER" -><I ->force - security mode</I -></TT -> parameters are applied to the change - request in that order.</P -><P ->For a directory Samba will perform the same operations as - described above for a file except using the parameter <TT -CLASS="PARAMETER" -><I -> directory security mask</I -></TT -> instead of <TT -CLASS="PARAMETER" -><I ->security - mask</I -></TT ->, and <TT -CLASS="PARAMETER" -><I ->force directory security mode - </I -></TT -> parameter instead of <TT -CLASS="PARAMETER" -><I ->force security mode - </I -></TT ->.</P -><P ->The <TT -CLASS="PARAMETER" -><I ->directory security mask</I -></TT -> parameter - by default is set to the same value as the <TT -CLASS="PARAMETER" -><I ->directory mask - </I -></TT -> parameter and the <TT -CLASS="PARAMETER" -><I ->force directory security - mode</I -></TT -> parameter by default is set to the same value as - the <TT -CLASS="PARAMETER" -><I ->force directory mode</I -></TT -> parameter to provide - compatibility with Samba 2.0.4 where the permission change facility - was introduced.</P -><P ->In this way Samba enforces the permission restrictions that - an administrator can set on a Samba share, whilst still allowing users - to modify the permission bits within that restriction.</P -><P ->If you want to set up a share that allows users full control - in modifying the permission bits on their files and directories and - doesn't force any particular bits to be set 'on', then set the following - parameters in the <A -HREF="smb.conf.5.html" -TARGET="_top" -><TT -CLASS="FILENAME" ->smb.conf(5) - </TT -></A -> file in that share specific section :</P -><P -><TT -CLASS="PARAMETER" -><I ->security mask = 0777</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force security mode = 0</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->directory security mask = 0777</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force directory security mode = 0</I -></TT -></P -><P ->As described, in Samba 2.0.4 the parameters :</P -><P -><TT -CLASS="PARAMETER" -><I ->create mask</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force create mode</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->directory mask</I -></TT -></P -><P -><TT -CLASS="PARAMETER" -><I ->force directory mode</I -></TT -></P -><P ->were used instead of the parameters discussed here.</P -></DIV -><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" -><A -NAME="AEN1800" ->9.7. Interaction with the standard Samba file attribute - mapping</A -></H1 -><P ->Samba maps some of the DOS attribute bits (such as "read - only") into the UNIX permissions of a file. This means there can - be a conflict between the permission bits set via the security - dialog and the permission bits set by the file attribute mapping. - </P -><P ->One way this can show up is if a file has no UNIX read access - for the owner it will show up as "read only" in the standard - file attributes tabbed dialog. Unfortunately this dialog is - the same one that contains the security info in another tab.</P -><P ->What this can mean is that if the owner changes the permissions - to allow themselves read access using the security dialog, clicks - <B -CLASS="COMMAND" ->"OK"</B -> to get back to the standard attributes tab - dialog, and then clicks <B -CLASS="COMMAND" ->"OK"</B -> on that dialog, then - NT will set the file permissions back to read-only (as that is what - the attributes still say in the dialog). This means that after setting - permissions and clicking <B -CLASS="COMMAND" ->"OK"</B -> to get back to the - attributes dialog you should always hit <B -CLASS="COMMAND" ->"Cancel"</B -> - rather than <B -CLASS="COMMAND" ->"OK"</B -> to ensure that your changes - are not overridden.</P -></DIV -></DIV -><DIV -CLASS="CHAPTER" -><HR><H1 -><A -NAME="AEN1810" +NAME="OS2" >Chapter 10. OS2 Client HOWTO</A ></H1 ><DIV @@ -8540,7 +8280,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1821" +NAME="AEN1747" >10.1. FAQs</A ></H1 ><DIV @@ -8548,7 +8288,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1823" +NAME="AEN1749" >10.1.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?</A ></H2 @@ -8607,7 +8347,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1838" +NAME="AEN1764" >10.1.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?</A ></H2 @@ -8660,7 +8400,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1847" +NAME="AEN1773" >10.1.3. Are there any other issues when OS/2 (any version) is used as a client?</A ></H2 @@ -8682,7 +8422,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1851" +NAME="AEN1777" >10.1.4. How do I get printer driver download working for OS/2 clients?</A ></H2 @@ -8694,7 +8434,7 @@ NAME="AEN1851" driver from an OS/2 system.</P ><P >Install the NT driver first for that printer. Then, - add to your smb.conf a paramater, "os2 driver map = + add to your smb.conf a parameter, "os2 driver map = <TT CLASS="REPLACEABLE" ><I @@ -8730,7 +8470,7 @@ CLASS="REPLACEABLE" CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN1860" +NAME="CVS-ACCESS" >Chapter 11. HOWTO Access Samba source code via CVS</A ></H1 ><DIV @@ -8738,14 +8478,14 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1867" +NAME="AEN1793" >11.1. Introduction</A ></H1 ><P ->Samba is developed in an open environnment. Developers use CVS +>Samba is developed in an open environment. Developers use CVS (Concurrent Versioning System) to "checkin" (also known as "commit") new source code. Samba's various CVS branches can -be accessed via anonymouns CVS using the instructions +be accessed via anonymous CVS using the instructions detailed in this chapter.</P ><P >This document is a modified version of the instructions found at @@ -8760,7 +8500,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1872" +NAME="AEN1798" >11.2. CVS Access to samba.org</A ></H1 ><P @@ -8773,7 +8513,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1875" +NAME="AEN1801" >11.2.1. Access via CVSweb</A ></H2 ><P @@ -8794,14 +8534,14 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1880" +NAME="AEN1806" >11.2.2. Access via cvs</A ></H2 ><P >You can also access the source code via a normal cvs client. This gives you much more control over you can do with the repository and allows you to checkout whole source trees -and keep them uptodate via normal cvs commands. This is the +and keep them up to date via normal cvs commands. This is the preferred method of access if you are a developer and not just a casual browser.</P ><P @@ -8898,6 +8638,20 @@ CLASS="COMMAND" ></DIV ></DIV ></DIV +><HR><H1 +><A +NAME="AEN1834" +>Index</A +></H1 +><DL +><DT +>Primary Domain Controller, + <A +HREF="x1103.htm" +>Background</A +> + </DT +></DL ></DIV ></BODY ></HTML |