diff options
| author | Gerald Carter <jerry@samba.org> | 2001-10-10 17:19:10 +0000 |
|---|---|---|
| committer | Gerald Carter <jerry@samba.org> | 2001-10-10 17:19:10 +0000 |
| commit | 55abd936a838a4410899db76cb5530b0c4694dc9 (patch) | |
| tree | 7096b43be65a4ec4cab7217ecd4e5ab603d9ac71 /docs/htmldocs | |
| parent | 1347bd6057f664fcd827e91b639cc55280d8fa77 (diff) | |
| download | samba-55abd936a838a4410899db76cb5530b0c4694dc9.tar.gz samba-55abd936a838a4410899db76cb5530b0c4694dc9.tar.bz2 samba-55abd936a838a4410899db76cb5530b0c4694dc9.zip | |
mega-merge from 2.2
(This used to be commit c76bf8ed3275e217d1b691879153fe9137bcbe38)
Diffstat (limited to 'docs/htmldocs')
34 files changed, 6359 insertions, 2873 deletions
diff --git a/docs/htmldocs/CVS-Access.html b/docs/htmldocs/CVS-Access.html index ea47cede04..1329433f1a 100644 --- a/docs/htmldocs/CVS-Access.html +++ b/docs/htmldocs/CVS-Access.html @@ -19,7 +19,7 @@ CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="AEN1" +NAME="CVS-ACCESS" >HOWTO Access Samba source code via CVS</A ></H1 ><HR></DIV @@ -32,10 +32,10 @@ NAME="AEN3" >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 @@ -91,7 +91,7 @@ NAME="AEN16" >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 diff --git a/docs/htmldocs/DOMAIN_MEMBER.html b/docs/htmldocs/DOMAIN_MEMBER.html index 051b72f8d0..bb29c416eb 100644 --- a/docs/htmldocs/DOMAIN_MEMBER.html +++ b/docs/htmldocs/DOMAIN_MEMBER.html @@ -19,7 +19,7 @@ CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="AEN1" +NAME="DOMAIN-SECURITY" >security = domain in Samba 2.x</A ></H1 ><HR></DIV diff --git a/docs/htmldocs/ENCRYPTION.html b/docs/htmldocs/ENCRYPTION.html index f7424be11a..e4d3ef5fed 100644 --- a/docs/htmldocs/ENCRYPTION.html +++ b/docs/htmldocs/ENCRYPTION.html @@ -19,7 +19,7 @@ CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="AEN1" +NAME="PWENCRYPT" >LanMan and NT Password Encryption in Samba 2.x</A ></H1 ><HR></DIV @@ -118,7 +118,7 @@ NAME="AEN18" ><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 + scheme typically sends clear text passwords over the network 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 @@ -196,7 +196,7 @@ CLASS="EMPHASIS" 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 + of the client to participate in encrypted authentication.</P ></TD ></TR ></TABLE diff --git a/docs/htmldocs/Integrating-with-Windows.html b/docs/htmldocs/Integrating-with-Windows.html new file mode 100644 index 0000000000..7c5fe31627 --- /dev/null +++ b/docs/htmldocs/Integrating-with-Windows.html @@ -0,0 +1,1072 @@ +<HTML +><HEAD +><TITLE +>Integrating MS Windows networks with Samba</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD +><BODY +CLASS="ARTICLE" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="ARTICLE" +><DIV +CLASS="TITLEPAGE" +><H1 +CLASS="TITLE" +><A +NAME="INTEGRATE-MS-NETWORKS" +>Integrating MS Windows networks with Samba</A +></H1 +><HR></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN3" +>Agenda</A +></H1 +><P +>To identify the key functional mechanisms of MS Windows networking +to enable the deployment of Samba as a means of extending and/or +replacing MS Windows NT/2000 technology.</P +><P +>We will examine:</P +><P +></P +><OL +TYPE="1" +><LI +><P +>Name resolution in a pure Unix/Linux TCP/IP + environment + </P +></LI +><LI +><P +>Name resolution as used within MS Windows + networking + </P +></LI +><LI +><P +>How browsing functions and how to deploy stable + and dependable browsing using Samba + </P +></LI +><LI +><P +>MS Windows security options and how to + configure Samba for seemless integration + </P +></LI +><LI +><P +>Configuration of Samba as:</P +><P +></P +><OL +TYPE="a" +><LI +><P +>A stand-alone server</P +></LI +><LI +><P +>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 + </P +></LI +></OL +></LI +></OL +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN25" +>Name Resolution in a pure Unix/Linux world</A +></H1 +><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="AEN41" +><TT +CLASS="FILENAME" +>/etc/hosts</TT +></A +></H2 +><P +>Contains a static list of IP Addresses and names. +eg:</P +><P +><PRE +CLASS="PROGRAMLISTING" +> 127.0.0.1 localhost localhost.localdomain + 192.168.1.1 bigbox.caldera.com bigbox alias4box</PRE +></P +><P +>The purpose of <TT +CLASS="FILENAME" +>/etc/hosts</TT +> is to provide a +name resolution mechanism so that uses do not need to remember +IP addresses.</P +><P +>Network packets that are sent over the physical network transport +layer communicate not via IP addresses but rather using the Media +Access Control address, or MAC address. IP Addresses are currently +32 bits in length and are typically presented as four (4) decimal +numbers that are separated by a dot (or period). eg: 168.192.1.1</P +><P +>MAC Addresses use 48 bits (or 6 bytes) and are typically represented +as two digit hexadecimal numbers separated by colons. eg: +40:8e:0a:12:34:56</P +><P +>Every network interfrace must have an MAC address. Associated with +a MAC address there may be one or more IP addresses. There is NO +relationship between an IP address and a MAC address, all such assignments +are arbitary or discretionary in nature. At the most basic level all +network communications takes place using MAC addressing. Since MAC +addresses must be globally unique, and generally remains fixed for +any particular interface, the assignment of an IP address makes sense +from a network management perspective. More than one IP address can +be assigned per MAC address. One address must be the primary IP address, +this is the address that will be returned in the ARP reply.</P +><P +>When a user or a process wants to communicate with another machine +the protocol implementation ensures that the "machine name" or "host +name" is resolved to an IP address in a manner that is controlled +by the TCP/IP configuration control files. The file +<TT +CLASS="FILENAME" +>/etc/hosts</TT +> is one such file.</P +><P +>When the IP address of the destination interface has been +determined a protocol called ARP/RARP isused to identify +the MAC address of the target interface. ARP stands for Address +Resolution Protocol, and is a broadcast oriented method that +uses UDP (User Datagram Protocol) to send a request to all +interfaces on the local network segment using the all 1's MAC +address. Network interfaces are programmed to respond to two +MAC addresses only; their own unique address and the address +ff:ff:ff:ff:ff:ff. The reply packet from an ARP request will +contain the MAC address and the primary IP address for each +interface.</P +><P +>The <TT +CLASS="FILENAME" +>/etc/hosts</TT +> file is foundational to all +Unix/Linux TCP/IP installations and as a minumum will contain +the localhost and local network interface IP addresses and the +primary names by which they are known within the local machine. +This file helps to prime the pump so that a basic level of name +resolution can exist before any other method of name resolution +becomes available.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN57" +><TT +CLASS="FILENAME" +>/etc/resolv.conf</TT +></A +></H2 +><P +>This file tells the name resolution libraries:</P +><P +></P +><UL +><LI +><P +>The name of the domain to which the machine + belongs + </P +></LI +><LI +><P +>The name(s) of any domains that should be + automatically searched when trying to resolve unqualified + host names to their IP address + </P +></LI +><LI +><P +>The name or IP address of available Domain + Name Servers that may be asked to perform name to address + translation lookups + </P +></LI +></UL +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN68" +><TT +CLASS="FILENAME" +>/etc/host.conf</TT +></A +></H2 +><P +><TT +CLASS="FILENAME" +>/etc/host.conf</TT +> is the primary means by +which the setting in /etc/resolv.conf may be affected. It is a +critical configuration file. This file controls the order by +which name resolution may procede. The typical structure is:</P +><P +><PRE +CLASS="PROGRAMLISTING" +> order hosts,bind + multi on</PRE +></P +><P +>then both addresses should be returned. Please refer to the +man page for host.conf for further details.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN76" +><TT +CLASS="FILENAME" +>/etc/nsswitch.conf</TT +></A +></H2 +><P +>This file controls the actual name resolution targets. The +file typically has resolver object specifications as follows:</P +><P +><PRE +CLASS="PROGRAMLISTING" +> # /etc/nsswitch.conf + # + # Name Service Switch configuration file. + # + + passwd: compat + # Alternative entries for password authentication are: + # passwd: compat files nis ldap winbind + shadow: compat + group: compat + + hosts: files nis dns + # Alternative entries for host name resolution are: + # hosts: files dns nis nis+ hesoid db compat ldap wins + networks: nis files dns + + ethers: nis files + protocols: nis files + rpc: nis files + services: nis files</PRE +></P +><P +>Of course, each of these mechanisms requires that the appropriate +facilities and/or services are correctly configured.</P +><P +>It should be noted that unless a network request/message must be +sent, TCP/IP networks are silent. All TCP/IP communications assumes a +principal of speaking only when necessary.</P +><P +>Samba version 2.2.0 will add Linux support for extensions to +the name service switch infrastructure so that linux clients will +be able to obtain resolution of MS Windows NetBIOS names to IP +Addresses. To gain this functionality Samba needs to be compiled +with appropriate arguments to the make command (ie: <B +CLASS="COMMAND" +>make +nsswitch/libnss_wins.so</B +>). The resulting library should +then be installed in the <TT +CLASS="FILENAME" +>/lib</TT +> directory and +the "wins" parameter needs to be added to the "hosts:" line in +the <TT +CLASS="FILENAME" +>/etc/nsswitch.conf</TT +> file. At this point it +will be possible to ping any MS Windows machine by it's NetBIOS +machine name, so long as that machine is within the workgroup to +which both the samba machine and the MS Windows machine belong.</P +></DIV +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN88" +>Name resolution as used within MS Windows networking</A +></H1 +><P +>MS Windows networking is predicated about the name each machine +is given. This name is known variously (and inconsistently) as +the "computer name", "machine name", "networking name", "netbios name", +"SMB name". All terms mean the same thing with the exception of +"netbios name" which can apply also to the name of the workgroup or the +domain name. The terms "workgroup" and "domain" are really just a +simply name with which the machine is associated. All NetBIOS names +are exactly 16 characters in length. The 16th character is reserved. +It is used to store a one byte value that indicates service level +information for the NetBIOS name that is registered. A NetBIOS machine +name is therefore registered for each service type that is provided by +the client/server.</P +><P +>The following are typical NetBIOS name/service type registrations:</P +><P +><PRE +CLASS="PROGRAMLISTING" +> Unique NetBIOS Names: + MACHINENAME<00> = Server Service is running on MACHINENAME + MACHINENAME<03> = Generic Machine Name (NetBIOS name) + MACHINENAME<20> = LanMan Server service is running on MACHINENAME + WORKGROUP<1b> = Domain Master Browser + + Group Names: + WORKGROUP<03> = Generic Name registered by all members of WORKGROUP + WORKGROUP<1c> = Domain Controllers / Netlogon Servers + WORKGROUP<1d> = Local Master Browsers + WORKGROUP<1e> = Internet Name Resolvers</PRE +></P +><P +>It should be noted that all NetBIOS machines register their own +names as per the above. This is in vast contrast to TCP/IP +installations where traditionally the system administrator will +determine in the /etc/hosts or in the DNS database what names +are associated with each IP address.</P +><P +>One further point of clarification should be noted, the <TT +CLASS="FILENAME" +>/etc/hosts</TT +> +file and the DNS records do not provide the NetBIOS name type information +that MS Windows clients depend on to locate the type of service that may +be needed. An example of this is what happens when an MS Windows client +wants to locate a domain logon server. It find this service and the IP +address of a server that provides it by performing a lookup (via a +NetBIOS broadcast) for enumeration of all machines that have +registered the name type *<1c>. A logon request is then sent to each +IP address that is returned in the enumerated list of IP addresses. Which +ever machine first replies then ends up providing the logon services.</P +><P +>The name "workgroup" or "domain" really can be confusing since these +have the added significance of indicating what is the security +architecture of the MS Windows network. The term "workgroup" indicates +that the primary nature of the network environment is that of a +peer-to-peer design. In a WORKGROUP all machines are responsible for +their own security, and generally such security is limited to use of +just a password (known as SHARE MORE security). In most situations +with peer-to-peer networking the users who control their own machines +will simply opt to have no security at all. It is possible to have +USER MODE security in a WORKGROUP environment, thus requiring use +of a user name and a matching password.</P +><P +>MS Windows networking is thus predetermined to use machine names +for all local and remote machine message passing. The protocol used is +called Server Message Block (SMB) and this is implemented using +the NetBIOS protocol (Network Basic Input Output System). NetBIOS can +be encapsulated using LLC (Logical Link Control) protocol - in which case +the resulting protocol is called NetBEUI (Network Basic Extended User +Interface). NetBIOS can also be run over IPX (Internetworking Packet +Exchange) protocol as used by Novell NetWare, and it can be run +over TCP/IP protocols - in which case the resulting protocol is called +NBT or NetBT, the NetBIOS over TCP/IP.</P +><P +>MS Windows machines use a complex array of name resolution mechanisms. +Since we are primarily concerned with TCP/IP this demonstration is +limited to this area.</P +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN100" +>The NetBIOS Name Cache</A +></H2 +><P +>All MS Windows machines employ an in memory buffer in which is +stored the NetBIOS names and their IP addresses for all external +machines that that the local machine has communicated with over the +past 10-15 minutes. It is more efficient to obtain an IP address +for a machine from the local cache than it is to go through all the +configured name resolution mechanisms.</P +><P +>If a machine whose name is in the local name cache has been shut +down before the name had been expired and flushed from the cache, then +an attempt to exchange a message with that machine will be subject +to time-out delays. ie: It's name is in the cache, so a name resolution +lookup will succeed, but the machine can not respond. This can be +frustrating for users - but it is a characteristic of the protocol.</P +><P +>The MS Windows utility that allows examination of the NetBIOS +name cache is called "nbtstat". The Samba equivalent of this +is called "nmblookup".</P +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN105" +>The LMHOSTS file</A +></H2 +><P +>This file is usually located in MS Windows NT 4.0 or +2000 in <TT +CLASS="FILENAME" +>C:\WINNT\SYSTEM32\DRIVERS\ETC</TT +> and contains +the IP Address and the machine name in matched pairs. The +<TT +CLASS="FILENAME" +>LMHOSTS</TT +> file performs NetBIOS name +to IP address mapping oriented.</P +><P +>It typically looks like:</P +><P +><PRE +CLASS="PROGRAMLISTING" +> # Copyright (c) 1998 Microsoft Corp. + # + # This is a sample LMHOSTS file used by the Microsoft Wins Client (NetBIOS + # over TCP/IP) stack for Windows98 + # + # This file contains the mappings of IP addresses to NT computernames + # (NetBIOS) names. Each entry should be kept on an individual line. + # The IP address should be placed in the first column followed by the + # corresponding computername. The address and the comptername + # should be separated by at least one space or tab. The "#" character + # is generally used to denote the start of a comment (see the exceptions + # below). + # + # This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts + # files and offers the following extensions: + # + # #PRE + # #DOM:<domain> + # #INCLUDE <filename> + # #BEGIN_ALTERNATE + # #END_ALTERNATE + # \0xnn (non-printing character support) + # + # Following any entry in the file with the characters "#PRE" will cause + # the entry to be preloaded into the name cache. By default, entries are + # not preloaded, but are parsed only after dynamic name resolution fails. + # + # Following an entry with the "#DOM:<domain>" tag will associate the + # entry with the domain specified by <domain>. This affects how the + # browser and logon services behave in TCP/IP environments. To preload + # the host name associated with #DOM entry, it is necessary to also add a + # #PRE to the line. The <domain> is always preloaded although it will not + # be shown when the name cache is viewed. + # + # Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT) + # software to seek the specified <filename> and parse it as if it were + # local. <filename> is generally a UNC-based name, allowing a + # centralized lmhosts file to be maintained on a server. + # It is ALWAYS necessary to provide a mapping for the IP address of the + # server prior to the #INCLUDE. This mapping must use the #PRE directive. + # In addtion the share "public" in the example below must be in the + # LanManServer list of "NullSessionShares" in order for client machines to + # be able to read the lmhosts file successfully. This key is under + # \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares + # in the registry. Simply add "public" to the list found there. + # + # The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE + # statements to be grouped together. Any single successful include + # will cause the group to succeed. + # + # Finally, non-printing characters can be embedded in mappings by + # first surrounding the NetBIOS name in quotations, then using the + # \0xnn notation to specify a hex value for a non-printing character. + # + # The following example illustrates all of these extensions: + # + # 102.54.94.97 rhino #PRE #DOM:networking #net group's DC + # 102.54.94.102 "appname \0x14" #special app server + # 102.54.94.123 popular #PRE #source server + # 102.54.94.117 localsrv #PRE #needed for the include + # + # #BEGIN_ALTERNATE + # #INCLUDE \\localsrv\public\lmhosts + # #INCLUDE \\rhino\public\lmhosts + # #END_ALTERNATE + # + # In the above example, the "appname" server contains a special + # character in its name, the "popular" and "localsrv" server names are + # preloaded, and the "rhino" server name is specified so it can be used + # to later #INCLUDE a centrally maintained lmhosts file if the "localsrv" + # system is unavailable. + # + # Note that the whole file is parsed including comments on each lookup, + # so keeping the number of comments to a minimum will improve performance. + # Therefore it is not advisable to simply add lmhosts file entries onto the + # end of this file.</PRE +></P +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN113" +>HOSTS file</A +></H2 +><P +>This file is usually located in MS Windows NT 4.0 or 2000 in +<TT +CLASS="FILENAME" +>C:\WINNT\SYSTEM32\DRIVERS\ETC</TT +> and contains +the IP Address and the IP hostname in matched pairs. It can be +used by the name resolution infrastructure in MS Windows, depending +on how the TCP/IP environment is configured. This file is in +every way the equivalent of the Unix/Linux <TT +CLASS="FILENAME" +>/etc/hosts</TT +> file.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN118" +>DNS Lookup</A +></H2 +><P +>This capability is configured in the TCP/IP setup area in the network +configuration facility. If enabled an elaborate name resolution sequence +is followed the precise nature of which isdependant on what the NetBIOS +Node Type parameter is configured to. A Node Type of 0 means use +NetBIOS broadcast (over UDP broadcast) is first used if the name +that is the subject of a name lookup is not found in the NetBIOS name +cache. If that fails then DNS, HOSTS and LMHOSTS are checked. If set to +Node Type 8, then a NetBIOS Unicast (over UDP Unicast) is sent to the +WINS Server to obtain a lookup before DNS, HOSTS, LMHOSTS, or broadcast +lookup is used.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN121" +>WINS Lookup</A +></H2 +><P +>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 +><P +>To configure Samba to be a WINS server the following parameter needs +to be added to the <TT +CLASS="FILENAME" +>smb.conf</TT +> file:</P +><P +><PRE +CLASS="PROGRAMLISTING" +> wins support = Yes</PRE +></P +><P +>To configure Samba to use a WINS server the following parameters are +needed in the smb.conf file:</P +><P +><PRE +CLASS="PROGRAMLISTING" +> wins support = No + wins server = xxx.xxx.xxx.xxx</PRE +></P +><P +>where <TT +CLASS="REPLACEABLE" +><I +>xxx.xxx.xxx.xxx</I +></TT +> is the IP address +of the WINS server.</P +></DIV +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN133" +>How browsing functions and how to deploy stable and +dependable browsing using Samba</A +></H1 +><P +>As stated above, MS Windows machines register their NetBIOS names +(ie: the machine name for each service type in operation) on start +up. Also, as stated above, the exact method by which this name registration +takes place is determined by whether or not the MS Windows client/server +has been given a WINS server address, whether or not LMHOSTS lookup +is enabled, or if DNS for NetBIOS name resolution is enabled, etc.</P +><P +>In the case where there is no WINS server all name registrations as +well as name lookups are done by UDP broadcast. This isolates name +resolution to the local subnet, unless LMHOSTS is used to list all +names and IP addresses. In such situations Samba provides a means by +which the samba server name may be forcibly injected into the browse +list of a remote MS Windows network (using the "remote announce" parameter).</P +><P +>Where a WINS server is used, the MS Windows client will use UDP +unicast to register with the WINS server. Such packets can be routed +and thus WINS allows name resolution to function across routed networks.</P +><P +>During the startup process an election will take place to create a +local master browser if one does not already exist. On each NetBIOS network +one machine will be elected to function as the domain master browser. This +domain browsing has nothing to do with MS security domain control. +Instead, the domain master browser serves the role of contacting each local +master browser (found by asking WINS or from LMHOSTS) and exchanging browse +list contents. This way every master browser will eventually obtain a complete +list of all machines that are on the network. Every 11-15 minutes an election +is held to determine which machine will be the master browser. By nature of +the election criteria used, the machine with the highest uptime, or the +most senior protocol version, or other criteria, will win the election +as domain master browser.</P +><P +>Clients wishing to browse the network make use of this list, but also depend +on the availability of correct name resolution to the respective IP +address/addresses. </P +><P +>Any configuration that breaks name resolution and/or browsing intrinsics +will annoy users because they will have to put up with protracted +inability to use the network services.</P +><P +>Samba supports a feature that allows forced synchonisation +of browse lists across routed networks using the "remote +browse sync" parameter in the smb.conf file. This causes Samba +to contact the local master browser on a remote network and +to request browse list synchronisation. This effectively bridges +two networks that are separated by routers. The two remote +networks may use either broadcast based name resolution or WINS +based name resolution, but it should be noted that the "remote +browse sync" parameter provides browse list synchronisation - and +that is distinct from name to address resolution, in other +words, for cross subnet browsing to function correctly it is +essential that a name to address resolution mechanism be provided. +This mechanism could be via DNS, <TT +CLASS="FILENAME" +>/etc/hosts</TT +>, +and so on.</P +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN143" +>MS Windows security options and how to configure +Samba for seemless integration</A +></H1 +><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 +>An MD4 hash of the UNICODE of the password + string. This is known as the NT hash. + </P +></LI +><LI +><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 +>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 +password authentication. All versions of MS Windows that follow +these versions no longer support plain text passwords by default.</P +><P +>MS Windows clients have a habit of dropping network mappings that +have been idle for 10 minutes or longer. When the user attempts to +use the mapped drive connection that has been dropped the SMB protocol +has a mechanism by which the connection can be re-established using +a cached copy of the password.</P +><P +>When Microsoft changed the default password mode, they dropped support for +caching of the plain text password. This means that when the registry +parameter is changed to re-enable use of plain text passwords it appears to +work, but when a dropped mapping attempts to revalidate it will fail if +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 +>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 +><PRE +CLASS="PROGRAMLISTING" +> <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 +></P +><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 <I +CLASS="EMPHASIS" +>could</I +> 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 +for support of encrypted passwords:</P +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN171" +>Use MS Windows NT as an authentication server</A +></H2 +><P +>This method involves the additions of the following parameters +in the smb.conf file:</P +><P +><PRE +CLASS="PROGRAMLISTING" +> encrypt passwords = Yes + security = server + password server = "NetBIOS_name_of_PDC"</PRE +></P +><P +>There are two ways of identifying whether or not a username and +password pair was valid or not. One uses the reply information provided +as part of the authentication messaging process, the other uses +just and error code.</P +><P +>The down-side of this mode of configuration is the fact that +for security reasons Samba will send the password server a bogus +username and a bogus password and if the remote server fails to +reject the username and password pair then an alternative mode +of identification of validation is used. Where a site uses password +lock out after a certain number of failed authentication attempts +this will result in user lockouts.</P +><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 +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN179" +>Make Samba a member of an MS Windows NT security domain</A +></H2 +><P +>This method involves additon of the following paramters in the smb.conf file:</P +><P +><PRE +CLASS="PROGRAMLISTING" +> encrypt passwords = Yes + security = domain + workgroup = "name of NT domain" + password server = *</PRE +></P +><P +>The use of the "*" argument to "password server" will cause samba +to locate the domain controller in a way analogous to the way +this is done within MS Windows NT.</P +><P +>In order for this method to work the Samba server needs to join the +MS Windows NT security domain. This is done as follows:</P +><P +></P +><UL +><LI +><P +>On the MS Windows NT domain controller using + the Server Manager add a machine account for the Samba server. + </P +></LI +><LI +><P +>Next, on the Linux system execute: + <B +CLASS="COMMAND" +>smbpasswd -r PDC_NAME -j DOMAIN_NAME</B +> + </P +></LI +></UL +><P +>Use of this mode of authentication does require there to be +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="AEN196" +>Configure Samba as an authentication server</A +></H2 +><P +>This mode of authentication demands that there be on the +Unix/Linux system both a Unix style account as well as and +smbpasswd entry for the user. The Unix system account can be +locked if required as only the encrypted password will be +used for SMB client authentication.</P +><P +>This method involves addition of the following parameters to +the smb.conf file:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>## 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 +></P +><P +>in order for this method to work a Unix system account needs +to be created for each user, as well as for each MS Windows NT/2000 +machine. The following structure is required.</P +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN203" +>Users</A +></H3 +><P +>A user account that may provide a home directory should be +created. The following Linux system commands are typical of +the procedure for creating an account.</P +><P +><PRE +CLASS="PROGRAMLISTING" +> # useradd -s /bin/bash -d /home/"userid" -m "userid" + # passwd "userid" + Enter Password: <pw> + + # smbpasswd -a "userid" + Enter Password: <pw></PRE +></P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN208" +>MS Windows NT Machine Accounts</A +></H3 +><P +>These are required only when Samba is used as a domain +controller. Refer to the Samba-PDC-HOWTO for more details.</P +><P +><PRE +CLASS="PROGRAMLISTING" +> # useradd -s /bin/false -d /dev/null "machine_name"\$ + # passwd -l "machine_name"\$ + # smbpasswd -a -m "machine_name"</PRE +></P +></DIV +></DIV +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN213" +>Conclusions</A +></H1 +><P +>Samba provides a flexible means to operate as...</P +><P +></P +><UL +><LI +><P +>A Stand-alone server - No special action is needed + other than to create user accounts. Stand-alone servers do NOT + provide network logon services, meaning that machines that use this + server do NOT perform a domain logon but instead make use only of + the MS Windows logon which is local to the MS Windows + workstation/server. + </P +></LI +><LI +><P +>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. + </P +></LI +></UL +></DIV +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/NT_Security.html b/docs/htmldocs/NT_Security.html index 43ba056624..ab8797563e 100644 --- a/docs/htmldocs/NT_Security.html +++ b/docs/htmldocs/NT_Security.html @@ -1,7 +1,7 @@ <HTML ><HEAD ><TITLE ->UNIX Permission Bits and WIndows NT Access Control Lists</TITLE +>UNIX Permission Bits and Windows NT Access Control Lists</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD @@ -19,8 +19,8 @@ CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="AEN1" ->UNIX Permission Bits and WIndows NT Access Control Lists</A +NAME="UNIX-PERMISSIONS" +>UNIX Permission Bits and Windows NT Access Control Lists</A ></H1 ><HR></DIV ><DIV @@ -153,7 +153,7 @@ CLASS="REPLACEABLE" >(Long name)</I ></TT > - is the discriptive string identifying the user (normally found in the + 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 @@ -182,7 +182,7 @@ CLASS="COMMAND" 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 + for this is that changing the ownership of a file is a privileged operation in UNIX, available only to the <I CLASS="EMPHASIS" >root</I @@ -192,7 +192,7 @@ CLASS="EMPHASIS" 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 + 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 <I @@ -242,7 +242,7 @@ CLASS="REPLACEABLE" >(Long name)</I ></TT > - is the discriptive string identifying the user (normally found in the + is the descriptive string identifying the user (normally found in the GECOS field of the UNIX password database).</P ><P >If the parameter <TT @@ -274,7 +274,7 @@ NAME="AEN58" ></H2 ><P >The standard UNIX user/group/world triple and - the correspinding "read", "write", "execute" permissions + 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 @@ -400,7 +400,7 @@ CLASS="COMMAND" 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 +>"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 @@ -450,7 +450,7 @@ CLASS="COMMAND" CLASS="COMMAND" >"Take Ownership"</B -> permission (dsplayed as <B +> permission (displayed as <B CLASS="COMMAND" >"O" </B @@ -582,7 +582,7 @@ CLASS="PARAMETER" ></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, + 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 diff --git a/docs/htmldocs/OS2-Client-HOWTO.html b/docs/htmldocs/OS2-Client-HOWTO.html index 84a424c017..90f62306e8 100644 --- a/docs/htmldocs/OS2-Client-HOWTO.html +++ b/docs/htmldocs/OS2-Client-HOWTO.html @@ -19,7 +19,7 @@ CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="AEN1" +NAME="OS2" >OS2 Client HOWTO</A ></H1 ><HR></DIV @@ -173,7 +173,7 @@ NAME="AEN33" 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 diff --git a/docs/htmldocs/PAM-Authentication-And-Samba.html b/docs/htmldocs/PAM-Authentication-And-Samba.html new file mode 100644 index 0000000000..332a8a7349 --- /dev/null +++ b/docs/htmldocs/PAM-Authentication-And-Samba.html @@ -0,0 +1,309 @@ +<HTML +><HEAD +><TITLE +>Configuring PAM for distributed but centrally +managed authentication</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD +><BODY +CLASS="ARTICLE" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="ARTICLE" +><DIV +CLASS="TITLEPAGE" +><H1 +CLASS="TITLE" +><A +NAME="PAM" +>Configuring PAM for distributed but centrally +managed authentication</A +></H1 +><HR></DIV +><DIV +CLASS="SECT1" +><H1 +CLASS="SECT1" +><A +NAME="AEN3" +>Samba and PAM</A +></H1 +><P +>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" +>/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 +>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 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 +><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 +></P +><P +>PAM allows use of replacable modules. Those available on a +sample system include:</P +><P +><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 +></P +><P +>The following example for the login program replaces the use of +the <TT +CLASS="FILENAME" +>pam_pwdb.so</TT +> module which uses the system +password database (<TT +CLASS="FILENAME" +>/etc/passwd</TT +>, +<TT +CLASS="FILENAME" +>/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 +>, +<TT +CLASS="FILENAME" +>/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" +>configure</B +> program.</P +><P +><PRE +CLASS="PROGRAMLISTING" +>#%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 +></P +><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 +><PRE +CLASS="PROGRAMLISTING" +>#%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 +></P +><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 +><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 +></P +><P +>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" +>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="AEN45" +>Distributed Authentication</A +></H1 +><P +>The astute administrator will realize from this that the +combination of <TT +CLASS="FILENAME" +>pam_smbpass.so</TT +>, +<B +CLASS="COMMAND" +>winbindd</B +>, and <B +CLASS="COMMAND" +>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="AEN52" +>PAM Configuration in smb.conf</A +></H1 +><P +>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 +>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 +>Default: <B +CLASS="COMMAND" +>obey pam restrictions = no</B +></P +></DIV +></DIV +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index c7393bc71b..c4e4b2c74b 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -34,10 +34,14 @@ NAME="AEN4" ><HR></DIV ><HR><H1 ><A -NAME="AEN9" +NAME="AEN8" >Abstract</A ></H1 ><P +><EM +>Last Update</EM +> : Tue Jul 31 15:58:03 CDT 2001</P +><P >This book is a collection of HOWTOs added to Samba documentation over the years. I try to ensure that all are current, but sometimes the is a larger job than one person can maintain. The most recent version of this document @@ -62,34 +66,34 @@ CLASS="TOC" ></DT ><DT >1. <A -HREF="#AEN15" +HREF="#INSTALL" >How to Install and Test SAMBA</A ></DT ><DD ><DL ><DT >1.1. <A -HREF="#AEN17" +HREF="#AEN18" >Step 0: Read the man pages</A ></DT ><DT >1.2. <A -HREF="#AEN25" +HREF="#AEN26" >Step 1: Building the Binaries</A ></DT ><DT >1.3. <A -HREF="#AEN53" +HREF="#AEN54" >Step 2: The all important step</A ></DT ><DT >1.4. <A -HREF="#AEN57" +HREF="#AEN58" >Step 3: Create the smb configuration file.</A ></DT ><DT >1.5. <A -HREF="#AEN71" +HREF="#AEN72" >Step 4: Test your config file with <B CLASS="COMMAND" @@ -98,80 +102,80 @@ CLASS="COMMAND" ></DT ><DT >1.6. <A -HREF="#AEN77" +HREF="#AEN78" >Step 5: Starting the smbd and nmbd</A ></DT ><DD ><DL ><DT >1.6.1. <A -HREF="#AEN87" +HREF="#AEN88" >Step 5a: Starting from inetd.conf</A ></DT ><DT >1.6.2. <A -HREF="#AEN116" +HREF="#AEN117" >Step 5b. Alternative: starting it as a daemon</A ></DT ></DL ></DD ><DT >1.7. <A -HREF="#AEN132" +HREF="#AEN133" >Step 6: Try listing the shares available on your server</A ></DT ><DT >1.8. <A -HREF="#AEN141" +HREF="#AEN142" >Step 7: Try connecting with the unix client</A ></DT ><DT >1.9. <A -HREF="#AEN157" +HREF="#AEN158" >Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</A ></DT ><DT >1.10. <A -HREF="#AEN171" +HREF="#AEN172" >What If Things Don't Work?</A ></DT ><DD ><DL ><DT >1.10.1. <A -HREF="#AEN176" +HREF="#AEN177" >Diagnosing Problems</A ></DT ><DT >1.10.2. <A -HREF="#AEN180" +HREF="#AEN181" >Scope IDs</A ></DT ><DT >1.10.3. <A -HREF="#AEN183" +HREF="#AEN184" >Choosing the Protocol Level</A ></DT ><DT >1.10.4. <A -HREF="#AEN192" +HREF="#AEN193" >Printing from UNIX to a Client PC</A ></DT ><DT >1.10.5. <A -HREF="#AEN196" +HREF="#AEN197" >Locking</A ></DT ><DT >1.10.6. <A -HREF="#AEN206" +HREF="#AEN207" >Mapping Usernames</A ></DT ><DT >1.10.7. <A -HREF="#AEN209" +HREF="#AEN210" >Other Character Sets</A ></DT ></DL @@ -180,26 +184,26 @@ HREF="#AEN209" ></DD ><DT >2. <A -HREF="#AEN212" +HREF="#INTEGRATE-MS-NETWORKS" >Integrating MS Windows networks with Samba</A ></DT ><DD ><DL ><DT >2.1. <A -HREF="#AEN223" +HREF="#AEN224" >Agenda</A ></DT ><DT >2.2. <A -HREF="#AEN245" +HREF="#AEN246" >Name Resolution in a pure Unix/Linux world</A ></DT ><DD ><DL ><DT >2.2.1. <A -HREF="#AEN248" +HREF="#AEN262" ><TT CLASS="FILENAME" >/etc/hosts</TT @@ -207,7 +211,7 @@ CLASS="FILENAME" ></DT ><DT >2.2.2. <A -HREF="#AEN264" +HREF="#AEN278" ><TT CLASS="FILENAME" >/etc/resolv.conf</TT @@ -215,7 +219,7 @@ CLASS="FILENAME" ></DT ><DT >2.2.3. <A -HREF="#AEN275" +HREF="#AEN289" ><TT CLASS="FILENAME" >/etc/host.conf</TT @@ -223,7 +227,7 @@ CLASS="FILENAME" ></DT ><DT >2.2.4. <A -HREF="#AEN283" +HREF="#AEN297" ><TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -233,47 +237,47 @@ CLASS="FILENAME" ></DD ><DT >2.3. <A -HREF="#AEN295" +HREF="#AEN309" >Name resolution as used within MS Windows networking</A ></DT ><DD ><DL ><DT >2.3.1. <A -HREF="#AEN307" +HREF="#AEN321" >The NetBIOS Name Cache</A ></DT ><DT >2.3.2. <A -HREF="#AEN312" +HREF="#AEN326" >The LMHOSTS file</A ></DT ><DT >2.3.3. <A -HREF="#AEN320" +HREF="#AEN334" >HOSTS file</A ></DT ><DT >2.3.4. <A -HREF="#AEN325" +HREF="#AEN339" >DNS Lookup</A ></DT ><DT >2.3.5. <A -HREF="#AEN328" +HREF="#AEN342" >WINS Lookup</A ></DT ></DL ></DD ><DT >2.4. <A -HREF="#AEN342" +HREF="#AEN354" >How browsing functions and how to deploy stable and dependable browsing using Samba</A ></DT ><DT >2.5. <A -HREF="#AEN352" +HREF="#AEN364" >MS Windows security options and how to configure Samba for seemless integration</A ></DT @@ -281,29 +285,29 @@ Samba for seemless integration</A ><DL ><DT >2.5.1. <A -HREF="#AEN369" +HREF="#AEN392" >Use MS Windows NT as an authentication server</A ></DT ><DT >2.5.2. <A -HREF="#AEN377" +HREF="#AEN400" >Make Samba a member of an MS Windows NT security domain</A ></DT ><DT >2.5.3. <A -HREF="#AEN391" +HREF="#AEN417" >Configure Samba as an authentication server</A ></DT ><DD ><DL ><DT >2.5.3.1. <A -HREF="#AEN398" +HREF="#AEN424" >Users</A ></DT ><DT >2.5.3.2. <A -HREF="#AEN405" +HREF="#AEN429" >MS Windows NT Machine Accounts</A ></DT ></DL @@ -312,168 +316,198 @@ HREF="#AEN405" ></DD ><DT >2.6. <A -HREF="#AEN410" ->Configuration of Samba as ...</A +HREF="#AEN434" +>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="#AEN455" +>Samba and PAM</A ></DT ><DT >3.2. <A -HREF="#AEN436" ->How does it work?</A +HREF="#AEN497" +>Distributed Authentication</A ></DT ><DT >3.3. <A -HREF="#AEN447" ->Important Notes About Security</A +HREF="#AEN504" +>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="#AEN524" +>Instructions</A ></DT +><DD +><DL ><DT ->3.3.2. <A -HREF="#AEN473" ->Advantages of non-encrypted passwords</A +>4.1.1. <A +HREF="#AEN559" +>Notes</A ></DT ></DL ></DD +></DL +></DD ><DT ->3.4. <A -HREF="#AEN482" -><A -NAME="SMBPASSWDFILEFORMAT" -></A ->The smbpasswd file</A -></DT -><DT ->3.5. <A -HREF="#AEN534" ->The smbpasswd Command</A +>5. <A +HREF="#UNIX-PERMISSIONS" +>UNIX Permission Bits and Windows NT Access Control Lists</A ></DT +><DD +><DL ><DT ->3.6. <A -HREF="#AEN573" ->Setting up Samba to support LanManager Encryption</A +>5.1. <A +HREF="#AEN579" +>Viewing and changing UNIX permissions using the NT + security dialogs</A ></DT -></DL -></DD ><DT ->4. <A +>5.2. <A HREF="#AEN588" ->Hosting a Microsoft Distributed File System tree on Samba</A +>How to view file security on a Samba share</A ></DT -><DD -><DL ><DT ->4.1. <A +>5.3. <A HREF="#AEN599" ->Instructions</A +>Viewing file ownership</A +></DT +><DT +>5.4. <A +HREF="#AEN619" +>Viewing file or directory permissions</A ></DT ><DD ><DL ><DT ->4.1.1. <A +>5.4.1. <A HREF="#AEN634" ->Notes</A +>File Permissions</A +></DT +><DT +>5.4.2. <A +HREF="#AEN648" +>Directory Permissions</A ></DT ></DL ></DD +><DT +>5.5. <A +HREF="#AEN655" +>Modifying file or directory permissions</A +></DT +><DT +>5.6. <A +HREF="#AEN677" +>Interaction with the standard Samba create mask + parameters</A +></DT +><DT +>5.7. <A +HREF="#AEN741" +>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="#AEN762" >Introduction</A ></DT ><DT ->5.2. <A -HREF="#AEN676" +>6.2. <A +HREF="#AEN784" >Configuration</A ></DT ><DD ><DL ><DT ->5.2.1. <A -HREF="#AEN687" +>6.2.1. <A +HREF="#AEN795" >Creating [print$]</A ></DT ><DT ->5.2.2. <A -HREF="#AEN722" +>6.2.2. <A +HREF="#AEN830" >Setting Drivers for Existing Printers</A ></DT ><DT ->5.2.3. <A -HREF="#AEN739" +>6.2.3. <A +HREF="#AEN847" >Support a large number of printers</A ></DT ><DT ->5.2.4. <A -HREF="#AEN750" +>6.2.4. <A +HREF="#AEN858" >Adding New Printers via the Windows NT APW</A ></DT ><DT ->5.2.5. <A -HREF="#AEN775" +>6.2.5. <A +HREF="#AEN883" >Samba and Printer Ports</A ></DT ></DL ></DD ><DT ->5.3. <A -HREF="#AEN783" +>6.3. <A +HREF="#AEN891" >The Imprints Toolset</A ></DT ><DD ><DL ><DT ->5.3.1. <A -HREF="#AEN787" +>6.3.1. <A +HREF="#AEN895" >What is Imprints?</A ></DT ><DT ->5.3.2. <A -HREF="#AEN797" +>6.3.2. <A +HREF="#AEN905" >Creating Printer Driver Packages</A ></DT ><DT ->5.3.3. <A -HREF="#AEN800" +>6.3.3. <A +HREF="#AEN908" >The Imprints server</A ></DT ><DT ->5.3.4. <A -HREF="#AEN804" +>6.3.4. <A +HREF="#AEN912" >The Installation Client</A ></DT ></DL ></DD ><DT ->5.4. <A -HREF="#AEN826" +>6.4. <A +HREF="#AEN934" ><A NAME="MIGRATION" ></A @@ -482,138 +516,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="#AEN988" >Joining an NT Domain with Samba 2.2</A ></DT ><DT ->6.2. <A -HREF="#AEN952" +>7.2. <A +HREF="#AEN1052" >Samba and Windows 2000 Domains</A ></DT ><DT ->6.3. <A -HREF="#AEN957" +>7.3. <A +HREF="#AEN1057" >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="#AEN1090" >Prerequisite Reading</A ></DT ><DT ->7.2. <A -HREF="#AEN996" +>8.2. <A +HREF="#AEN1096" >Background</A ></DT ><DT ->7.3. <A -HREF="#AEN1036" +>8.3. <A +HREF="#AEN1138" >Configuring the Samba Domain Controller</A ></DT ><DT ->7.4. <A -HREF="#AEN1079" +>8.4. <A +HREF="#AEN1180" >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="#AEN1194" >Manually creating machine trust accounts</A ></DT ><DT ->7.4.2. <A -HREF="#AEN1121" +>8.4.2. <A +HREF="#AEN1225" >Creating machine trust accounts "on the fly"</A ></DT ></DL ></DD ><DT ->7.5. <A -HREF="#AEN1132" +>8.5. <A +HREF="#AEN1236" >Common Problems and Errors</A ></DT ><DT ->7.6. <A -HREF="#AEN1180" +>8.6. <A +HREF="#AEN1284" >System Policies and Profiles</A ></DT ><DT ->7.7. <A -HREF="#AEN1224" +>8.7. <A +HREF="#AEN1328" >What other help can I get ?</A ></DT ><DT ->7.8. <A -HREF="#AEN1338" +>8.8. <A +HREF="#AEN1442" >Domain Control for Windows 9x/ME</A ></DT ><DD ><DL ><DT ->7.8.1. <A -HREF="#AEN1368" +>8.8.1. <A +HREF="#AEN1472" >Configuration Instructions: Network Logons</A ></DT ><DT ->7.8.2. <A -HREF="#AEN1402" +>8.8.2. <A +HREF="#AEN1506" >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="#AEN1514" >Windows NT Configuration</A ></DT ><DT ->7.8.2.2. <A -HREF="#AEN1418" +>8.8.2.2. <A +HREF="#AEN1522" >Windows 9X Configuration</A ></DT ><DT ->7.8.2.3. <A -HREF="#AEN1426" +>8.8.2.3. <A +HREF="#AEN1530" >Win9X and WinNT Configuration</A ></DT ><DT ->7.8.2.4. <A -HREF="#AEN1433" +>8.8.2.4. <A +HREF="#AEN1537" >Windows 9X Profile Setup</A ></DT ><DT ->7.8.2.5. <A -HREF="#AEN1469" +>8.8.2.5. <A +HREF="#AEN1573" >Windows NT Workstation 4.0</A ></DT ><DT ->7.8.2.6. <A -HREF="#AEN1482" +>8.8.2.6. <A +HREF="#AEN1586" >Windows NT Server</A ></DT ><DT ->7.8.2.7. <A -HREF="#AEN1485" +>8.8.2.7. <A +HREF="#AEN1589" >Sharing Profiles between W95 and NT Workstation 4.0</A ></DT ></DL @@ -621,190 +655,187 @@ HREF="#AEN1485" ></DL ></DD ><DT ->7.9. <A -HREF="#AEN1495" +>8.9. <A +HREF="#AEN1599" >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="#AEN1642" >Abstract</A ></DT ><DT ->8.2. <A -HREF="#AEN1542" +>9.2. <A +HREF="#AEN1646" >Introduction</A ></DT ><DT ->8.3. <A -HREF="#AEN1555" +>9.3. <A +HREF="#AEN1659" >What Winbind Provides</A ></DT ><DD ><DL ><DT ->8.3.1. <A -HREF="#AEN1562" +>9.3.1. <A +HREF="#AEN1666" >Target Uses</A ></DT ></DL ></DD ><DT ->8.4. <A -HREF="#AEN1566" +>9.4. <A +HREF="#AEN1670" >How Winbind Works</A ></DT ><DD ><DL ><DT ->8.4.1. <A -HREF="#AEN1571" +>9.4.1. <A +HREF="#AEN1675" >Microsoft Remote Procedure Calls</A ></DT ><DT ->8.4.2. <A -HREF="#AEN1575" +>9.4.2. <A +HREF="#AEN1679" >Name Service Switch</A ></DT ><DT ->8.4.3. <A -HREF="#AEN1591" +>9.4.3. <A +HREF="#AEN1695" >Pluggable Authentication Modules</A ></DT ><DT ->8.4.4. <A -HREF="#AEN1599" +>9.4.4. <A +HREF="#AEN1703" >User and Group ID Allocation</A ></DT ><DT ->8.4.5. <A -HREF="#AEN1603" +>9.4.5. <A +HREF="#AEN1707" >Result Caching</A ></DT ></DL ></DD ><DT ->8.5. <A -HREF="#AEN1606" +>9.5. <A +HREF="#AEN1710" >Installation and Configuration</A ></DT +><DD +><DL ><DT ->8.6. <A -HREF="#AEN1612" ->Limitations</A +>9.5.1. <A +HREF="#AEN1715" +>Introduction</A ></DT ><DT ->8.7. <A -HREF="#AEN1624" ->Conclusion</A +>9.5.2. <A +HREF="#AEN1728" +>Requirements</A ></DT -></DL -></DD ><DT ->9. <A -HREF="#AEN1627" ->UNIX Permission Bits and WIndows NT Access Control Lists</A +>9.5.3. <A +HREF="#AEN1736" +>Testing Things Out</A ></DT ><DD ><DL ><DT ->9.1. <A -HREF="#AEN1638" ->Viewing and changing UNIX permissions using the NT - security dialogs</A +>9.5.3.1. <A +HREF="#AEN1745" +>Configure and compile SAMBA</A ></DT ><DT ->9.2. <A -HREF="#AEN1647" ->How to view file security on a Samba share</A +>9.5.3.2. <A +HREF="#AEN1757" +>Configure nsswitch.conf and the winbind libraries</A ></DT ><DT ->9.3. <A -HREF="#AEN1658" ->Viewing file ownership</A +>9.5.3.3. <A +HREF="#AEN1776" +>Configure smb.conf</A ></DT ><DT ->9.4. <A -HREF="#AEN1678" ->Viewing file or directory permissions</A +>9.5.3.4. <A +HREF="#AEN1785" +>Join the SAMBA server to the PDC domain</A ></DT -><DD -><DL ><DT ->9.4.1. <A -HREF="#AEN1693" ->File Permissions</A +>9.5.3.5. <A +HREF="#AEN1795" +>Start up the winbindd daemon and test it!</A ></DT ><DT ->9.4.2. <A -HREF="#AEN1707" ->Directory Permissions</A +>9.5.3.6. <A +HREF="#AEN1822" +>Fix the /etc/rc.d/init.d/smb startup files</A ></DT -></DL -></DD ><DT ->9.5. <A -HREF="#AEN1714" ->Modifying file or directory permissions</A +>9.5.3.7. <A +HREF="#AEN1839" +>Configure Winbind and PAM</A ></DT +></DL +></DD +></DL +></DD ><DT >9.6. <A -HREF="#AEN1736" ->Interaction with the standard Samba create mask - parameters</A +HREF="#AEN1880" +>Limitations</A ></DT ><DT >9.7. <A -HREF="#AEN1800" ->Interaction with the standard Samba file attribute - mapping</A +HREF="#AEN1890" +>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="#AEN1904" >FAQs</A ></DT ><DD ><DL ><DT >10.1.1. <A -HREF="#AEN1823" +HREF="#AEN1906" >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="#AEN1921" >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="#AEN1930" >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="#AEN1934" >How do I get printer driver download working for OS/2 clients?</A ></DT @@ -814,44 +845,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="#AEN1950" >Introduction</A ></DT ><DT >11.2. <A -HREF="#AEN1872" +HREF="#AEN1955" >CVS Access to samba.org</A ></DT ><DD ><DL ><DT >11.2.1. <A -HREF="#AEN1875" +HREF="#AEN1958" >Access via CVSweb</A ></DT ><DT >11.2.2. <A -HREF="#AEN1880" +HREF="#AEN1963" >Access via cvs</A ></DT ></DL ></DD ></DL ></DD +><DT +><A +HREF="#AEN1991" +>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 @@ -859,7 +895,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN17" +NAME="AEN18" >1.1. Step 0: Read the man pages</A ></H1 ><P @@ -891,7 +927,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN25" +NAME="AEN26" >1.2. Step 1: Building the Binaries</A ></H1 ><P @@ -915,7 +951,7 @@ CLASS="USERINPUT" ></P ><P >first to see what special options you can enable. - Then exectuting</P + Then executing</P ><P ><TT CLASS="PROMPT" @@ -990,7 +1026,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN53" +NAME="AEN54" >1.3. Step 2: The all important step</A ></H1 ><P @@ -1007,7 +1043,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN57" +NAME="AEN58" >1.4. Step 3: Create the smb configuration file.</A ></H1 ><P @@ -1042,7 +1078,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" @@ -1072,7 +1108,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN71" +NAME="AEN72" >1.5. Step 4: Test your config file with <B CLASS="COMMAND" @@ -1089,14 +1125,14 @@ 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" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN77" +NAME="AEN78" >1.6. Step 5: Starting the smbd and nmbd</A ></H1 ><P @@ -1136,7 +1172,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN87" +NAME="AEN88" >1.6.1. Step 5a: Starting from inetd.conf</A ></H2 ><P @@ -1207,7 +1243,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 +1256,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 @@ -1249,7 +1285,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN116" +NAME="AEN117" >1.6.2. Step 5b. Alternative: starting it as a daemon</A ></H2 ><P @@ -1315,7 +1351,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN132" +NAME="AEN133" >1.7. Step 6: Try listing the shares available on your server</A ></H1 @@ -1356,7 +1392,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN141" +NAME="AEN142" >1.8. Step 7: Try connecting with the unix client</A ></H1 ><P @@ -1419,7 +1455,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN157" +NAME="AEN158" >1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT, Win2k, OS/2, etc... client</A ></H1 @@ -1468,7 +1504,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN171" +NAME="AEN172" >1.10. What If Things Don't Work?</A ></H1 ><P @@ -1491,11 +1527,11 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN176" +NAME="AEN177" >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 @@ -1507,7 +1543,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN180" +NAME="AEN181" >1.10.2. Scope IDs</A ></H2 ><P @@ -1523,7 +1559,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN183" +NAME="AEN184" >1.10.3. Choosing the Protocol Level</A ></H2 ><P @@ -1564,7 +1600,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN192" +NAME="AEN193" >1.10.4. Printing from UNIX to a Client PC</A ></H2 ><P @@ -1582,7 +1618,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN196" +NAME="AEN197" >1.10.5. Locking</A ></H2 ><P @@ -1594,20 +1630,25 @@ NAME="AEN196" The second is the "deny modes" that are specified when a file is open.</P ><P ->Samba supports "record locking" using the fcntl() unix system - call. This is often implemented using rpc calls to a rpc.lockd process - running on the system that owns the filesystem. Unfortunately many - rpc.lockd implementations are very buggy, particularly when made to - talk to versions from other vendors. It is not uncommon for the - rpc.lockd to crash.</P -><P ->There is also a problem translating the 32 bit lock - requests generated by PC clients to 31 bit requests supported - by most unixes. Unfortunately many PC applications (typically - OLE2 applications) use byte ranges with the top bit set - as semaphore sets. Samba attempts translation to support - these types of applications, and the translation has proved - to be quite successful.</P +>Record locking semantics under Unix is very + different from record locking under Windows. Versions + of Samba before 2.2 have tried to use the native + fcntl() unix system call to implement proper record + locking between different Samba clients. This can not + be fully correct due to several reasons. The simplest + is the fact that a Windows client is allowed to lock a + byte range up to 2^32 or 2^64, depending on the client + OS. The unix locking only supports byte ranges up to + 2^31. So it is not possible to correctly satisfy a + lock request above 2^31. There are many more + differences, too many to be listed here.</P +><P +>Samba 2.2 and above implements record locking + completely independent of the underlying unix + system. If a byte range lock that the client requests + happens to fall into the range 0-2^31, Samba hands + this request down to the Unix system. All other locks + can not be seen by unix anyway.</P ><P >Strictly a SMB server should check for locks before every read and write call on a file. Unfortunately with the @@ -1629,7 +1670,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". @@ -1643,7 +1684,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN206" +NAME="AEN207" >1.10.6. Mapping Usernames</A ></H2 ><P @@ -1656,13 +1697,13 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN209" +NAME="AEN210" >1.10.7. Other Character Sets</A ></H2 ><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 +1713,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 @@ -1680,7 +1721,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN223" +NAME="AEN224" >2.1. Agenda</A ></H1 ><P @@ -1747,17 +1788,49 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN245" +NAME="AEN246" >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="AEN262" >2.2.1. <TT CLASS="FILENAME" >/etc/hosts</TT @@ -1847,7 +1920,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN264" +NAME="AEN278" >2.2.2. <TT CLASS="FILENAME" >/etc/resolv.conf</TT @@ -1885,7 +1958,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN275" +NAME="AEN289" >2.2.3. <TT CLASS="FILENAME" >/etc/host.conf</TT @@ -1923,7 +1996,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN283" +NAME="AEN297" >2.2.4. <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -2001,7 +2074,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN295" +NAME="AEN309" >2.3. Name resolution as used within MS Windows networking</A ></H1 ><P @@ -2095,7 +2168,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN307" +NAME="AEN321" >2.3.1. The NetBIOS Name Cache</A ></H2 ><P @@ -2122,7 +2195,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN312" +NAME="AEN326" >2.3.2. The LMHOSTS file</A ></H2 ><P @@ -2234,7 +2307,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN320" +NAME="AEN334" >2.3.3. HOSTS file</A ></H2 ><P @@ -2256,7 +2329,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN325" +NAME="AEN339" >2.3.4. DNS Lookup</A ></H2 ><P @@ -2276,14 +2349,11 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN328" +NAME="AEN342" >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 +2390,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 +2410,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN342" +NAME="AEN354" >2.4. How browsing functions and how to deploy stable and dependable browsing using Samba</A ></H1 @@ -2412,35 +2477,47 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN352" +NAME="AEN364" >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 +2538,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 +2551,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 +2619,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN369" +NAME="AEN392" >2.5.1. Use MS Windows NT as an authentication server</A ></H2 ><P @@ -2539,7 +2664,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN377" +NAME="AEN400" >2.5.2. Make Samba a member of an MS Windows NT security domain</A ></H2 ><P @@ -2589,15 +2714,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="AEN417" >2.5.3. Configure Samba as an authentication server</A ></H2 ><P @@ -2618,8 +2757,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 +2782,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN398" +NAME="AEN424" >2.5.3.1. Users</A ></H3 ><P @@ -2649,22 +2798,12 @@ WIDTH="100%" ><TD ><PRE CLASS="PROGRAMLISTING" -> # useradd -s /bin/bash -d /home/"userid" -m +> # useradd -s /bin/bash -d /home/"userid" -m "userid" # 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 +2814,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN405" +NAME="AEN429" >2.5.3.2. MS Windows NT Machine Accounts</A ></H3 ><P @@ -2690,7 +2829,7 @@ WIDTH="100%" ><TD ><PRE CLASS="PROGRAMLISTING" -> # useradd -a /bin/false -d /dev/null "machine_name"\$ +> # useradd -s /bin/false -d /dev/null "machine_name"\$ # passwd -l "machine_name"\$ # smbpasswd -a -m "machine_name"</PRE ></TD @@ -2705,10 +2844,12 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN410" ->2.6. Configuration of Samba as ...</A +NAME="AEN434" +>2.6. Conclusions</A ></H1 ><P +>Samba provides a flexible means to operate as...</P +><P ></P ><UL ><LI @@ -2723,384 +2864,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="AEN455" +>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 +3052,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 +3078,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="AEN497" +>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 -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 +>The astute administrator will realize from this that the +combination of <TT +CLASS="FILENAME" +>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="AEN504" +>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 +3220,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN599" +NAME="AEN524" >4.1. Instructions</A ></H1 ><P @@ -3577,7 +3377,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN634" +NAME="AEN559" >4.1.1. Notes</A ></H2 ><P @@ -3610,16 +3410,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="AEN654" ->5.1. Introduction</A +NAME="AEN579" +>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="AEN588" +>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="AEN599" +>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="AEN619" +>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="AEN634" +>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="AEN648" +>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="AEN655" +>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="AEN677" +>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="AEN741" +>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="AEN762" +>6.1. Introduction</A ></H1 ><P >Beginning with the 2.2.0 release, Samba supports @@ -3702,8 +4255,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN676" ->5.2. Configuration</A +NAME="AEN784" +>6.2. Configuration</A ></H1 ><DIV CLASS="WARNING" @@ -3770,8 +4323,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN687" ->5.2.1. Creating [print$]</A +NAME="AEN795" +>6.2.1. Creating [print$]</A ></H2 ><P >In order to support the uploading of printer driver @@ -3781,7 +4334,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 +4348,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 +4364,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 @@ -3822,7 +4382,7 @@ CLASS="PARAMETER" > is used to allow administrative level user accounts to have write access in order to update files on the share. See the <A -HREF="smb./conf.5.html" +HREF="smb.conf.5.html" TARGET="_top" >smb.conf(5) man page</A @@ -3964,8 +4524,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN722" ->5.2.2. Setting Drivers for Existing Printers</A +NAME="AEN830" +>6.2.2. Setting Drivers for Existing Printers</A ></H2 ><P >The initial listing of printers in the Samba host's @@ -4036,8 +4596,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN739" ->5.2.3. Support a large number of printers</A +NAME="AEN847" +>6.2.3. Support a large number of printers</A ></H2 ><P >One issue that has arisen during the development @@ -4111,8 +4671,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN750" ->5.2.4. Adding New Printers via the Windows NT APW</A +NAME="AEN858" +>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 +4688,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 +4777,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN775" ->5.2.5. Samba and Printer Ports</A +NAME="AEN883" +>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 +4814,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN783" ->5.3. The Imprints Toolset</A +NAME="AEN891" +>6.3. The Imprints Toolset</A ></H1 ><P >The Imprints tool set provides a UNIX equivalent of the @@ -4272,8 +4832,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN787" ->5.3.1. What is Imprints?</A +NAME="AEN895" +>6.3.1. What is Imprints?</A ></H2 ><P >Imprints is a collection of tools for supporting the goals @@ -4304,8 +4864,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN797" ->5.3.2. Creating Printer Driver Packages</A +NAME="AEN905" +>6.3.2. Creating Printer Driver Packages</A ></H2 ><P >The process of creating printer driver packages is beyond @@ -4320,8 +4880,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN800" ->5.3.3. The Imprints server</A +NAME="AEN908" +>6.3.3. The Imprints server</A ></H2 ><P >The Imprints server is really a database server that @@ -4340,8 +4900,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN804" ->5.3.4. The Installation Client</A +NAME="AEN912" +>6.3.4. The Installation Client</A ></H2 ><P >More information regarding the Imprints installation client @@ -4410,7 +4970,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 +5003,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN826" ->5.4. <A +NAME="AEN934" +>6.4. <A NAME="MIGRATION" ></A >Migration to from Samba 2.0.x to 2.2.x</A @@ -4452,51 +5012,67 @@ NAME="MIGRATION" ><P >Given that printer driver management has changed (we hope improved) in 2.2 over prior releases, migration from an existing setup to 2.2 can -follow several paths.</P +follow several paths. Here are the possible scenarios for +migration:</P ><P ->Windows clients have a tendency to remember things for quite a while. -For example, if a Windows NT client has attached to a Samba 2.0 server, -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 +><UL +><LI ><P ->In order to give an NT client printing "amesia" (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 -CLASS="CONSTANT" ->[HKLM\SYSTEM\CurrentControlSet\Control\Print]</TT ->. The -spooler service on the client should be stopped prior to doing this:</P +>If you do not desire the new Windows NT + print driver support, nothing needs to be done. + All existing parameters work the same.</P +></LI +><LI ><P -><TT -CLASS="PROMPT" ->C:\WINNT\ ></TT -> <TT -CLASS="USERINPUT" -><B ->net stop spooler</B -></TT -></P +>If you want to take advantage of NT printer + driver support but do not want to migrate the + 9x drivers to the new setup, the leave the existing + <TT +CLASS="FILENAME" +>printers.def</TT +> file. When smbd attempts + to locate a + 9x driver for the printer in the TDB and fails it + will drop down to using the printers.def (and all + associated parameters). The <B +CLASS="COMMAND" +>make_printerdef</B +> + tool will also remain for backwards compatibility but will + be removed in the next major release.</P +></LI +><LI ><P -><EM ->All the normal disclaimers about editing the registry go -here.</EM -> Be careful, and know what you are doing.</P +>If you install a Windows 9x driver for a printer + on your Samba host (in the printing TDB), this information will + take precedence and the three old printing parameters + will be ignored (including print driver location).</P +></LI +><LI ><P ->The spooler service should be restarted after you have finished -removing the appropriate registry entries by replacing the -<B +>If you want to migrate an existing <TT +CLASS="FILENAME" +>printers.def</TT +> + file into the new setup, the current only solution is to use the Windows + NT APW to install the NT drivers and the 9x drivers. This can be scripted + using <B CLASS="COMMAND" ->stop</B -> command above with <B +>smbclient</B +> and <B CLASS="COMMAND" ->start</B ->.</P -><P ->Windows 9x clients will continue to use LanMan printing calls -with a 2.2 Samba server so there is no need to perform any of these -modifications on non-NT clients.</P +>rpcclient</B +>. See the + Imprints installation client at <A +HREF="http://imprints.sourceforge.net/" +TARGET="_top" +>http://imprints.sourceforge.net/</A +> + for an example. + </P +></LI +></UL ><DIV CLASS="WARNING" ><P @@ -4516,8 +5092,12 @@ ALIGN="CENTER" ><TD ALIGN="LEFT" ><P ->The following smb.conf parameters are considered to be depreciated and will -be removed soon. Do not use them in new installations</P +>The following <TT +CLASS="FILENAME" +>smb.conf</TT +> parameters are considered to +be deprecated and will be removed soon. Do not use them in new +installations</P ><P ></P ><UL @@ -4557,79 +5137,38 @@ CLASS="PARAMETER" ></TABLE ></DIV ><P ->Here are the possible scenarios for supporting migration:</P -><P -></P -><UL -><LI -><P ->If you do not desire the new Windows NT - print driver support, nothing needs to be done. - All existing parameters work the same.</P -></LI -><LI -><P ->If you want to take advantage of NT printer - driver support but do not want to migrate the - 9x drivers to the new setup, the leave the existing - printers.def file. When smbd attempts to locate a - 9x driver for the printer in the TDB and fails it - will drop down to using the printers.def (and all - associated parameters). The <B -CLASS="COMMAND" ->make_printerdef</B -> - tool will also remain for backwards compatibility but will - be moved to the "this tool is the old way of doing it" - pile.</P -></LI -><LI -><P ->If you install a Windows 9x driver for a printer - on your Samba host (in the printing TDB), this information will - take precedence and the three old printing parameters - will be ignored (including print driver location).</P -></LI -><LI -><P ->If you want to migrate an existing <TT -CLASS="FILENAME" ->printers.def</TT -> - file into the new setup, the current only solution is to use the Windows - NT APW to install the NT drivers and the 9x drivers. This can be scripted - using <B -CLASS="COMMAND" ->smbclient</B -> and <B -CLASS="COMMAND" ->rpcclient</B ->. See the - Imprints installation client at <A -HREF="http://imprints.sourceforge.net/" -TARGET="_top" ->http://imprints.sourceforge.net/</A -> - for an example. - </P -></LI -></UL +>The have been two new parameters add in Samba 2.2.2 to for +better support of Samba 2.0.x backwards capability (<TT +CLASS="PARAMETER" +><I +>disable +spoolss</I +></TT +>) and for using local printers drivers on Windows +NT/2000 clients (<TT +CLASS="PARAMETER" +><I +>use client driver</I +></TT +>). Both of +these options are described in the smb.coinf(5) man page and are +disabled by default.</P ></DIV ></DIV ><DIV 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="AEN988" +>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 +5394,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN952" ->6.2. Samba and Windows 2000 Domains</A +NAME="AEN1052" +>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 +5419,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN957" ->6.3. Why is this better than security = server?</A +NAME="AEN1057" +>7.3. Why is this better than security = server?</A ></H1 ><P >Currently, domain security in Samba doesn't free you from @@ -4966,21 +5505,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="AEN1090" +>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 +5530,7 @@ CLASS="FILENAME" ></A > manpage and the <A -HREF="EMCRYPTION.html" +HREF="ENCRYPTION.html" TARGET="_top" >Encryption chapter</A > @@ -5002,8 +5541,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN996" ->7.2. Background</A +NAME="AEN1096" +>8.2. Background</A ></H1 ><DIV CLASS="NOTE" @@ -5016,12 +5555,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 +5698,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1036" ->7.3. Configuring the Samba Domain Controller</A +NAME="AEN1138" +>8.3. Configuring the Samba Domain Controller</A ></H1 ><P >The first step in creating a working Samba PDC is to @@ -5364,16 +5903,11 @@ CLASS="FILENAME" >As Samba 2.2 does not offer a complete implementation of group mapping between Windows NT groups and UNIX groups (this is really quite complicated to explain in a short space), you should refer to the <A -HREF="smb.conf.5.html#DOMAINADMINUSERS" -TARGET="_top" ->domain -admin users</A -> and <A HREF="smb.conf.5.html#DOMAINADMINGROUP" TARGET="_top" >domain admin group</A -> smb.conf parameters for information of creating a Domain Admins +> smb.conf parameter for information of creating "Domain Admins" style accounts.</P ></DIV ><DIV @@ -5381,15 +5915,15 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1079" ->7.4. Creating Machine Trust Accounts and Joining Clients +NAME="AEN1180" +>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 +5956,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 +5973,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1093" ->7.4.1. Manually creating machine trust accounts</A +NAME="AEN1194" +>8.4.1. Manually creating machine trust accounts</A ></H2 ><P >The first step in creating a machine trust account by hand is to @@ -5458,9 +5992,20 @@ CLASS="PROMPT" >/usr/sbin/useradd -g 100 -d /dev/null -c <TT CLASS="REPLACEABLE" ><I ->machine_nickname</I +>"machine +nickname"</I +></TT +> -s /bin/false <TT +CLASS="REPLACEABLE" +><I +>machine_name</I ></TT -> -m -s /bin/false <TT +>$ </P +><P +><TT +CLASS="PROMPT" +>root# </TT +>passwd -l <TT CLASS="REPLACEABLE" ><I >machine_name</I @@ -5509,7 +6054,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 +6084,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 +6110,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 +6124,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1121" ->7.4.2. Creating machine trust accounts "on the fly"</A +NAME="AEN1225" +>8.4.2. Creating machine trust accounts "on the fly"</A ></H2 ><P >The second, and most recommended way of creating machine trust accounts @@ -5615,7 +6160,7 @@ an entry in smbpasswd for <EM >. The password <EM >SHOULD</EM -> be set to s different password that the +> be set to a different password that the associated <TT CLASS="FILENAME" >/etc/passwd</TT @@ -5627,8 +6172,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1132" ->7.5. Common Problems and Errors</A +NAME="AEN1236" +>8.5. Common Problems and Errors</A ></H1 ><P ></P @@ -5746,8 +6291,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 +6317,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 +6371,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1180" ->7.6. System Policies and Profiles</A +NAME="AEN1284" +>8.6. System Policies and Profiles</A ></H1 ><P >Much of the information necessary to implement System Policies and @@ -5890,7 +6435,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 +6528,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1224" ->7.7. What other help can I get ?</A +NAME="AEN1328" +>8.7. What other help can I get ?</A ></H1 ><P >There are many sources of information available in the form @@ -6003,7 +6548,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 +6604,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 +6856,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 +6924,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1338" ->7.8. Domain Control for Windows 9x/ME</A +NAME="AEN1442" +>8.8. Domain Control for Windows 9x/ME</A ></H1 ><DIV CLASS="NOTE" @@ -6417,7 +6962,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 +7042,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 +7060,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1368" ->7.8.1. Configuration Instructions: Network Logons</A +NAME="AEN1472" +>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 +7170,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 +7220,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 +7249,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1402" ->7.8.2. Configuration Instructions: Setting up Roaming User Profiles</A +NAME="AEN1506" +>8.8.2. Configuration Instructions: Setting up Roaming User Profiles</A ></H2 ><DIV CLASS="WARNING" @@ -6740,7 +7285,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 +7296,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1410" ->7.8.2.1. Windows NT Configuration</A +NAME="AEN1514" +>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 +7340,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1418" ->7.8.2.2. Windows 9X Configuration</A +NAME="AEN1522" +>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 +7380,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1426" ->7.8.2.3. Win9X and WinNT Configuration</A +NAME="AEN1530" +>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 +7418,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1433" ->7.8.2.4. Windows 9X Profile Setup</A +NAME="AEN1537" +>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, @@ -6882,7 +7427,7 @@ as are folders "Start Menu", "Desktop", "Programs" and "Nethood". These directories and their contents will be merged with the local versions stored in c:\windows\profiles\username on subsequent logins, taking the most recent from each. You will need to use the [global] -options "preserve case = yes", "short case preserve = yes" and +options "preserve case = yes", "short preserve case = yes" and "case sensitive = no" in order to maintain capital letters in shortcuts in any of the profile folders.</P ><P @@ -6997,7 +7542,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 +7574,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1469" ->7.8.2.5. Windows NT Workstation 4.0</A +NAME="AEN1573" +>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 +7636,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 +7656,8 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN1482" ->7.8.2.6. Windows NT Server</A +NAME="AEN1586" +>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 +7670,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="AEN1589" +>8.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</A ></H3 ><DIV CLASS="WARNING" @@ -7190,8 +7735,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1495" ->7.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A +NAME="AEN1599" +>8.9. DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></H1 ><DIV CLASS="WARNING" @@ -7287,7 +7832,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 +7843,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,25 +7856,26 @@ 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="AEN1642" +>9.1. Abstract</A ></H1 ><P >Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a "holy grail" in heterogeneous - computing environments for a long time. We present <EM ->winbind - </EM ->, a component of the Samba suite of programs as a - solution to the unied logon problem. Winbind uses a UNIX implementation + computing environments for a long time. We present + <EM +>winbind</EM +>, a component of the Samba suite + of programs as a 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 +7887,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1542" ->8.2. Introduction</A +NAME="AEN1646" +>9.2. Introduction</A ></H1 ><P >It is well known that UNIX and Microsoft Windows NT have @@ -7356,11 +7902,11 @@ NAME="AEN1542" and use the Samba suite of programs to provide file and print services between the two. This solution is far from perfect however, as adding and deleting users on both sets of machines becomes a chore - and two sets of passwords are required both of which which + and two sets of passwords are required both of which 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 +7933,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 +7941,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1555" ->8.3. What Winbind Provides</A +NAME="AEN1659" +>9.3. What Winbind Provides</A ></H1 ><P >Winbind unifies UNIX and Windows NT account management by @@ -7409,7 +7955,7 @@ NAME="AEN1555" >The end result is that whenever any program on the UNIX machine asks the operating system to lookup a user or group name, the query will be resolved by asking the - NT domain controller for the specied domain to do the lookup. + NT domain controller for the specified domain to do the lookup. Because Winbind hooks into the operating system at a low level (via the NSS name resolution modules in the C library) this redirection to the NT domain controller is completely @@ -7426,28 +7972,28 @@ NAME="AEN1555" that redirection to a domain controller is wanted for a particular lookup and which trusted domain is being referenced.</P ><P ->Additionally, Winbind provides a authentication service +>Additionally, Winbind provides an authentication service that hooks into the Pluggable Authentication Modules (PAM) system to provide authentication via a NT domain to any PAM enabled applications. This capability solves the problem of synchronizing - passwords between systems as all passwords are stored in a single + passwords between systems since all passwords are stored in a single location (on the domain controller).</P ><DIV CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1562" ->8.3.1. Target Uses</A +NAME="AEN1666" +>9.3.1. Target Uses</A ></H2 ><P >Winbind is targeted at organizations that have an existing NT based domain infrastructure into which they wish to put UNIX workstations or servers. Winbind will allow these organizations to deploy UNIX workstations without having to - maintain a separate account infrastructure. This greatly simplies - the administrative overhead of deploying UNIX workstations into - a NT based organization.</P + maintain a separate account infrastructure. This greatly + simplifies the administrative overhead of deploying UNIX + workstations into a NT based organization.</P ><P >Another interesting way in which we expect Winbind to be used is as a central part of UNIX based appliances. Appliances @@ -7461,8 +8007,8 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1566" ->8.4. How Winbind Works</A +NAME="AEN1670" +>9.4. How Winbind Works</A ></H1 ><P >The winbind system is designed around a client/server @@ -7481,8 +8027,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1571" ->8.4.1. Microsoft Remote Procedure Calls</A +NAME="AEN1675" +>9.4.1. Microsoft Remote Procedure Calls</A ></H2 ><P >Over the last two years, efforts have been underway @@ -7507,18 +8053,18 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1575" ->8.4.2. Name Service Switch</A +NAME="AEN1679" +>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 + flat files stored on the local filesystem. A networked workstation may first attempt to resolve system information from local files, - then consult a NIS database for user information or a DNS server + and then consult a NIS database for user information or a DNS server for hostname information.</P ><P >The NSS application programming interface allows winbind @@ -7531,11 +8077,12 @@ NAME="AEN1575" a NT domain plus any trusted domain as though they were local users and groups.</P ><P ->The primary control le for NSS is <TT +>The primary control file for NSS is + <TT CLASS="FILENAME" ->/etc/nsswitch.conf - </TT ->. When a UNIX application makes a request to do a lookup +>/etc/nsswitch.conf</TT +>. + When a UNIX application makes a request to do a lookup the C library looks in <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -7543,7 +8090,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 +8133,14 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1591" ->8.4.3. Pluggable Authentication Modules</A +NAME="AEN1695" +>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 @@ -7605,10 +8152,10 @@ NAME="AEN1591" UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated against a suitable Primary Domain Controller. These users can also change their passwords and have - this change take eect directly on the Primary Domain Controller. + this change take effect 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 @@ -7625,7 +8172,7 @@ CLASS="FILENAME" is copied to <TT CLASS="FILENAME" >/lib/security/</TT -> and the pam +> and the PAM control files for relevant services are updated to allow authentication via winbind. See the PAM documentation for more details.</P @@ -7635,16 +8182,16 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1599" ->8.4.4. User and Group ID Allocation</A +NAME="AEN1703" +>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 that 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 @@ -7653,7 +8200,7 @@ NAME="AEN1599" to UNIX user ids and group ids.</P ><P >The results of this mapping are stored persistently in - a ID mapping database held in a tdb database). This ensures that + an ID mapping database held in a tdb database). This ensures that RIDs are mapped to UNIX IDs in a consistent way.</P ></DIV ><DIV @@ -7661,8 +8208,8 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1603" ->8.4.5. Result Caching</A +NAME="AEN1707" +>9.4.5. Result Caching</A ></H2 ><P >An active system can generate a lot of user and group @@ -7671,7 +8218,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,855 +8231,873 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1606" ->8.5. Installation and Configuration</A +NAME="AEN1710" +>9.5. Installation and Configuration</A ></H1 ><P ->The easiest way to install winbind is by using the packages - provided in the <TT -CLASS="FILENAME" ->pub/samba/appliance/</TT -> - directory on your nearest - Samba mirror. These packages provide snapshots of the Samba source - code and binaries already setup to provide the full functionality - of winbind. This setup is a little more complex than a normal Samba - build as winbind needs a small amount of functionality from a - development code branch called SAMBA_TNG.</P -><P ->Once you have installed the packages you should read - the <B -CLASS="COMMAND" ->winbindd(8)</B -> man page which will provide you - with conguration information and give you sample conguration 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 -></DIV +>Many thanks to John Trostel <A +HREF="mailto:jtrostel@snapserver.com" +TARGET="_top" +>jtrostel@snapserver.com</A +> +for providing the HOWTO for this section.</P +><P +>This HOWTO describes how to get winbind services up and running +to control access and authenticate users on your Linux box using +the winbind services which come with SAMBA 2.2.2.</P ><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" ><A -NAME="AEN1612" ->8.6. Limitations</A -></H1 +NAME="AEN1715" +>9.5.1. Introduction</A +></H2 ><P ->Winbind has a number of limitations in its current - released version which we hope to overcome in future - releases:</P +>This HOWTO describes the procedures used to get winbind up and +running on my RedHat 7.1 system. Winbind is capable of providing access +and authentication control for Windows Domain users through an NT +or Win2K PDC for 'regular' services, such as telnet a nd ftp, as +well for SAMBA services.</P +><P +>This HOWTO has been written from a 'RedHat-centric' perspective, so if +you are using another distribution, you may have to modify the instructions +somewhat to fit the way your distribution works.</P ><P ></P ><UL ><LI ><P ->Winbind is currently only available for - the Linux operating system, although ports to other operating - systems are certainly possible. For such ports to be feasible, - we require the C library of the target operating system to - support the Name Service Switch and Pluggable Authentication - Modules systems. This is becoming more common as NSS and - PAM gain support among UNIX vendors.</P -></LI -><LI +> <EM +>Why should I to this?</EM +> + </P ><P ->The mappings of Windows NT RIDs to UNIX ids - is not made algorithmically and depends on the order in which - unmapped users or groups are seen by winbind. It may be difficult - to recover the mappings of rid to UNIX id mapping if the file - containing this information is corrupted or destroyed.</P +>This allows the SAMBA administrator to rely on the + authentication mechanisms on the NT/Win2K PDC for the authentication + of domain members. NT/Win2K users no longer need to have separate + accounts on the SAMBA server. + </P ></LI ><LI ><P ->Currently the winbind PAM module does not take - into account possible workstation and logon time restrictions - that may be been set for Windows NT users.</P -></LI -><LI +> <EM +>Who should be reading this document?</EM +> + </P ><P ->Building winbind from source is currently - quite tedious as it requires combining source code from two Samba - branches. Work is underway to solve this by providing all - the necessary functionality in the main Samba code branch.</P +> This HOWTO is designed for system administrators. If you are + implementing SAMBA on a file server and wish to (fairly easily) + integrate existing NT/Win2K users from your PDC onto the + SAMBA server, this HOWTO is for you. That said, I am no NT or PAM + expert, so you may find a better or easier way to accomplish + these tasks. + </P ></LI ></UL ></DIV ><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" ><A -NAME="AEN1624" ->8.7. Conclusion</A -></H1 +NAME="AEN1728" +>9.5.2. Requirements</A +></H2 ><P ->The winbind system, through the use of the Name Service - Switch, Pluggable Authentication Modules, and appropriate - Microsoft RPC calls have allowed us to provide seamless - integration of Microsoft Windows NT domain users on a - UNIX system. The result is a great reduction in the administrative - cost of running a mixed UNIX and NT network.</P -></DIV +>If you have a samba configuration file that you are currently +using... BACK IT UP! If your system already uses PAM, BACK UP +THE <TT +CLASS="FILENAME" +>/etc/pam.d</TT +> directory contents! If you +haven't already made a boot disk, MAKE ON NOW!</P +><P +>Messing with the pam configuration files can make it nearly impossible +to log in to yourmachine. That's why you want to be able to boot back +into your machine in single user mode and restore your +<TT +CLASS="FILENAME" +>/etc/pam.d</TT +> back to the original state they were in if +you get frustrated with the way things are going. ;-)</P +><P +>The newest version of SAMBA (version 2.2.2), available from +cvs.samba.org, now include a functioning winbindd daemon. Please refer +to the main SAMBA web page or, better yet, your closest SAMBA mirror +site for instructions on downloading the source code.</P +><P +>To allow Domain users the ability to access SAMBA shares and +files, as well as potentially other services provided by your +SAMBA machine, PAM (pluggable authentication modules) must +be setup properly on your machine. In order to compile the +winbind modules, you should have at least the pam libraries resident +on your system. For recent RedHat systems (7.1, for instance), that +means 'pam-0.74-22'. For best results, it is helpful to also +install the development packages in 'pam-devel-0.74-22'.</P ></DIV ><DIV -CLASS="CHAPTER" -><HR><H1 +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" ><A -NAME="AEN1627" ->Chapter 9. UNIX Permission Bits and WIndows NT Access Control Lists</A -></H1 +NAME="AEN1736" +>9.5.3. Testing Things Out</A +></H2 +><P +>Before starting, it is probably best to kill off all the SAMBA +related daemons running on your server. Kill off all <B +CLASS="COMMAND" +>smbd</B +>, +<B +CLASS="COMMAND" +>nmbd</B +>, and <B +CLASS="COMMAND" +>winbindd</B +> processes that may +be running. To use PAM, you will want to make sure that you have the +standard PAM package (for RedHat) which supplies the <TT +CLASS="FILENAME" +>/etc/pam.d</TT +> +directory structure, including the pam modules are used by pam-aware +services, several pam libraries, and the <TT +CLASS="FILENAME" +>/usr/doc</TT +> +and <TT +CLASS="FILENAME" +>/usr/man</TT +> entries for pam. Winbind built better +in SAMBA if the pam-devel package was also installed. This package includes +the header files needed to compile pam-aware applications. For instance, my RedHat +system has both 'pam-0.74-22' and 'pam-devel-0.74-22' RPMs installed.</P ><DIV -CLASS="SECT1" -><H1 -CLASS="SECT1" +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" ><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 +NAME="AEN1745" +>9.5.3.1. Configure and compile SAMBA</A +></H3 ><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 +>The configuration and compilation of SAMBA is pretty straightforward. +The first three steps maynot be necessary depending upon +whether or not you have previously built the Samba binaries.</P ><P ->In Samba 2.0.4 and above the default value of the - parameter <A -HREF="smb.conf.5.html#NTACLSUPPORT" -TARGET="_top" +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" ><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 +CLASS="PROMPT" +>root# </TT +> autoconf +<TT +CLASS="PROMPT" +>root# </TT +> make clean +<TT +CLASS="PROMPT" +>root# </TT +> rm config.cache +<TT +CLASS="PROMPT" +>root# </TT +> ./configure --with-winbind +<TT +CLASS="PROMPT" +>root# </TT +> make +<TT +CLASS="PROMPT" +>root# </TT +> make install</PRE +></TD +></TR +></TABLE +></P ><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 +>This will, by default, install SAMBA in /usr/local/samba. See the +main SAMBA documentation if you want to install SAMBA somewhere else. +It will also build the winbindd executable and libraries. </P ></DIV ><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" ><A -NAME="AEN1658" ->9.3. Viewing file ownership</A -></H1 +NAME="AEN1757" +>9.5.3.2. Configure nsswitch.conf and the winbind libraries</A +></H3 ><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 +>The libraries needed to run the winbind daemon through nsswitch +need to be copied to their proper locations, so</P ><P -><B -CLASS="COMMAND" ->"SERVER\user (Long name)"</B -></P +><TT +CLASS="PROMPT" +>root# </TT +> cp ../samba/source/nsswitch/libnss_winbind.so /lib</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 +>I also found it necessary to make the following symbolic link:</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 +><TT +CLASS="PROMPT" +>root# </TT +> ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</P ><P ->The <B +>Now, as root you need to edit <TT +CLASS="FILENAME" +>/etc/nsswitch.conf</TT +> to +allow user and group entries to be visible from 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 +>winbindd</B > - 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 +daemon, as well as from your /etc/hosts files and NIS servers. My +<TT +CLASS="FILENAME" +>/etc/nsswitch.conf</TT +> file look like this after editing:</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 +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +> passwd: files winbind + shadow: files winbind + group: files winbind</PRE +></TD +></TR +></TABLE +></P +><P +> +The libraries needed by the winbind daemon will be automatically +entered into the ldconfig cache the next time your system reboots, but it +is faster (and you don't need to reboot) if you do it manually:</P +><P +><TT +CLASS="PROMPT" +>root# </TT +> /sbin/ldconfig -v | grep winbind</P +><P +>This makes <TT +CLASS="FILENAME" +>libnss_winbind</TT +> available to winbindd +and echos back a check to you.</P ></DIV ><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" ><A -NAME="AEN1678" ->9.4. Viewing file or directory permissions</A -></H1 +NAME="AEN1776" +>9.5.3.3. Configure smb.conf</A +></H3 ><P ->The third button is the <B +>Several parameters are needed in the smb.conf file to control +the behavior of <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 +>winbindd</B +>. Configure +<TT +CLASS="FILENAME" +>smb.conf</TT +> These are described in more detail in +the <A +HREF="winbindd.8.html" +TARGET="_top" +>winbindd(8)</A +> man page. My +<TT +CLASS="FILENAME" +>smb.conf</TT +> file was modified to +include the following entries in the [global] section:</P ><P -><B -CLASS="COMMAND" ->"SERVER\user (Long name)"</B +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>[global] + <...> + # separate domain and username with '+', like DOMAIN+username + winbind separator = + + # use uids from 10000 to 20000 for domain users + winbind uid = 10000-20000 + # use gids from 10000 to 20000 for domain groups + winbind gid = 10000-20000 + # allow enumeration of winbind users and groups + winbind enum users = yes + winbind enum groups = yes + # give winbind users a real shell (only needed if they have telnet access) + template shell = /bin/bash</PRE +></TD +></TR +></TABLE ></P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN1785" +>9.5.3.4. Join the SAMBA server to the PDC domain</A +></H3 ><P ->Where <TT +>Enter the following command to make the SAMBA server join the +PDC domain, where <TT CLASS="REPLACEABLE" ><I ->SERVER</I +>DOMAIN</I ></TT -> is the NetBIOS name of - the Samba server, <TT +> is the name of +your Windows domain and <TT CLASS="REPLACEABLE" ><I ->user</I +>Administrator</I ></TT -> is the user name of - the UNIX user who owns the file, and <TT +> is +a domain user who has administrative privileges in the domain.</P +><P +><TT +CLASS="PROMPT" +>root# </TT +>/usr/local/samba/bin/smbpasswd -j DOMAIN -r PDC -U Administrator</P +><P +>The proper response to the command should be: "Joined the domain +<TT CLASS="REPLACEABLE" ><I ->(Long name)</I +>DOMAIN</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" +>" where <TT +CLASS="REPLACEABLE" ><I ->nt acl support</I +>DOMAIN</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 +> +is your DOMAIN name.</P +></DIV ><DIV -CLASS="SECT2" -><HR><H2 -CLASS="SECT2" +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" ><A -NAME="AEN1693" ->9.4.1. File Permissions</A -></H2 +NAME="AEN1795" +>9.5.3.5. Start up the winbindd daemon and test it!</A +></H3 ><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 +>Eventually, you will want to modify your smb startup script to +automatically invoke the winbindd daemon when the other parts of +SAMBA start, but it is possible to test out just the winbind +portion first. To start up winbind services, enter the following +command as root:</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 +><TT +CLASS="PROMPT" +>root# </TT +>/usr/local/samba/bin/winbindd</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 +>I'm always paranoid and like to make sure the daemon +is really running...</P ><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 +><TT +CLASS="PROMPT" +>root# </TT +> ps -ae | grep winbindd +3025 ? 00:00:00 winbindd</P +><P +>Now... for the real test, try to get some information about the +users on your PDC</P +><P +><TT +CLASS="PROMPT" +>root# </TT +> # /usr/local/samba/bin/wbinfo -u</P +><P +> +This should echo back a list of users on your Windows users on +your PDC. For example, I get the following response:</P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>CEO+Administrator +CEO+burdell +CEO+Guest +CEO+jt-ad +CEO+krbtgt +CEO+TsInternetUser</PRE +></TD +></TR +></TABLE +></P +><P +>Obviously, I have named my domain 'CEO' and my winbindd separator is '+'.</P +><P +>You can do the same sort of thing to get group information from +the PDC:</P +><P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +><TT +CLASS="PROMPT" +>root# </TT +>/usr/local/samba/bin/wbinfo -g +CEO+Domain Admins +CEO+Domain Users +CEO+Domain Guests +CEO+Domain Computers +CEO+Domain Controllers +CEO+Cert Publishers +CEO+Schema Admins +CEO+Enterprise Admins +CEO+Group Policy Creator Owners</PRE +></TD +></TR +></TABLE +></P +><P +>The function 'getent' can now be used to get unified +lists of both local and PDC users and groups. +Try the following command:</P +><P +><TT +CLASS="PROMPT" +>root# </TT +> getent passwd</P +><P +>You should get a list that looks like your <TT +CLASS="FILENAME" +>/etc/passwd</TT > - 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 +list followed by the domain users with their new uids, gids, home +directories and default shells.</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 +>The same thing can be done for groups with the command</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 +><TT +CLASS="PROMPT" +>root# </TT +> getent group</P ></DIV ><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" ><A -NAME="AEN1714" ->9.5. Modifying file or directory permissions</A -></H1 +NAME="AEN1822" +>9.5.3.6. Fix the /etc/rc.d/init.d/smb startup files</A +></H3 ><P ->Modifying file and directory permissions is as simple - as changing the displayed permissions in the dialog box, and - clicking the <B +>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 +>winbindd</B +> daemon needs to start up after the +<B CLASS="COMMAND" ->"Access Denied" - </B -> message.</P -><P ->The first thing to note is that the <B +>smbd</B +> and <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 +>nmbd</B +> daemons are running. +To accomplish this task, you need to modify the <TT +CLASS="FILENAME" +>/etc/init.d/smb</TT +> +script to add commands to invoke this daemon in the proper sequence. My +<TT +CLASS="FILENAME" +>/etc/init.d/smb</TT +> file starts up <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 +>smbd</B +>, +<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 +>nmbd</B +>, and <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 +>winbindd</B +> from the +<TT +CLASS="FILENAME" +>/usr/local/samba/bin</TT +> directory directly. The 'start' +function in the script looks like this:</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 +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>start() { + KIND="SMB" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/smbd $SMBDOPTIONS + RETVAL=$? + echo + KIND="NMB" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS + RETVAL2=$? + echo + KIND="Winbind" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/winbindd + RETVAL3=$? + echo + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ + RETVAL=1 + return $RETVAL +}</PRE +></TD +></TR +></TABLE +></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 +>The 'stop' function has a corresponding entry to shut down the +services and look s like this:</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 +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>stop() { + KIND="SMB" + echo -n $"Shutting down $KIND services: " + killproc smbd + RETVAL=$? + echo + KIND="NMB" + echo -n $"Shutting down $KIND services: " + killproc nmbd + RETVAL2=$? + echo + KIND="Winbind" + echo -n $"Shutting down $KIND services: " + killproc winbindd + RETVAL3=$? + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb + echo "" + return $RETVAL +}</PRE +></TD +></TR +></TABLE +></P ></DIV ><DIV -CLASS="SECT1" -><HR><H1 -CLASS="SECT1" +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" ><A -NAME="AEN1736" ->9.6. Interaction with the standard Samba create mask - parameters</A -></H1 +NAME="AEN1839" +>9.5.3.7. Configure Winbind and PAM</A +></H3 ><P ->Note that with Samba 2.0.5 there are four new parameters - to control this interaction. These are :</P +>If you have made it this far, you know that winbindd is working. +Now it is time to integrate it into the operation of samba and other +services. The pam configuration files need to be altered in +this step. (Did you remember to make backups of your original +<TT +CLASS="FILENAME" +>/etc/pam.d</TT +> files? If not, do it now.)</P ><P -><TT -CLASS="PARAMETER" -><I ->security mask</I -></TT -></P +>To get samba to allow domain users and groups, I modified the +<TT +CLASS="FILENAME" +>/etc/pam.d/samba</TT +> file from</P ><P -><TT -CLASS="PARAMETER" -><I ->force security mode</I -></TT +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>auth required /lib/security/pam_stack.so service=system-auth +account required /lib/security/pam_stack.so service=system-auth</PRE +></TD +></TR +></TABLE ></P ><P -><TT -CLASS="PARAMETER" -><I ->directory security mask</I -></TT -></P +>to</P ><P -><TT -CLASS="PARAMETER" -><I ->force directory security mode</I -></TT +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>auth required /lib/security/pam_winbind.so +auth required /lib/security/pam_stack.so service=system-auth +account required /lib/security/pam_winbind.so +account required /lib/security/pam_stack.so service=system-auth</PRE +></TD +></TR +></TABLE ></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 +>The other services that I modified to allow the use of winbind +as an authentication service were the normal login on the console (or a terminal +session), telnet logins, and ftp service. In order to enable these +services, you may first need to change the entries in +<TT +CLASS="FILENAME" +>/etc/xinetd.d</TT +> (or <TT +CLASS="FILENAME" +>/etc/inetd.conf</TT +>). +RedHat 7.1 uses the new xinetd.d structure, in this case you need +to change the lines in <TT +CLASS="FILENAME" +>/etc/xinetd.d/telnet</TT > - 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 +and <TT +CLASS="FILENAME" +>/etc/xinetd.d/wu-ftp</TT +> from </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 +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>enable = no</PRE +></TD +></TR +></TABLE +></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 +>to</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 +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>enable = yes</PRE +></TD +></TR +></TABLE +></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 +> +For ftp services to work properly, you will also need to either +have individual directories for the domain users already present on +the server, or change the home directory template to a general +directory for all domain users. These can be easily set using +the <TT +CLASS="FILENAME" +>smb.conf</TT +> global entry +<B +CLASS="COMMAND" +>template homedir</B >.</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 +>/etc/pam.d/ftp</TT +> file can be changed +to allow winbind ftp access in a manner similar to the +samba file. My <TT +CLASS="FILENAME" +>/etc/pam.d/ftp</TT +> file was +changed to look like this:</P ><P -><TT -CLASS="PARAMETER" -><I ->security mask = 0777</I -></TT +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>auth sufficient /lib/security/pam_winbind.so +auth required /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed +auth required /lib/security/pam_stack.so service=system-auth +auth required /lib/security/pam_shells.so +account required /lib/security/pam_stack.so service=system-auth +session required /lib/security/pam_stack.so service=system-auth</PRE +></TD +></TR +></TABLE ></P ><P -><TT -CLASS="PARAMETER" -><I ->force security mode = 0</I -></TT -></P +>The <TT +CLASS="FILENAME" +>/etc/pam.d/login</TT +> file can be changed nearly the +same way. It now looks like this:</P ><P -><TT -CLASS="PARAMETER" -><I ->directory security mask = 0777</I -></TT +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +>auth required /lib/security/pam_securetty.so +auth sufficient /lib/security/pam_winbind.so +auth sufficient /lib/security/pam_unix.so use_first_pass +auth required /lib/security/pam_stack.so service=system-auth +auth required /lib/security/pam_nologin.so +account sufficient /lib/security/pam_winbind.so +account required /lib/security/pam_stack.so service=system-auth +password required /lib/security/pam_stack.so service=system-auth +session required /lib/security/pam_stack.so service=system-auth +session optional /lib/security/pam_console.so</PRE +></TD +></TR +></TABLE ></P ><P -><TT -CLASS="PARAMETER" -><I ->force directory security mode = 0</I -></TT -></P +>In this case, I added the <B +CLASS="COMMAND" +>auth sufficient /lib/security/pam_winbind.so</B +> +lines as before, but also added the <B +CLASS="COMMAND" +>required pam_securetty.so</B +> +above it, to disallow root logins over the network. I also added a +<B +CLASS="COMMAND" +>sufficient /lib/security/pam_unix.so use_first_pass</B +> +line after the <B +CLASS="COMMAND" +>winbind.so</B +> line to get rid of annoying +double prompts for passwords.</P ><P ->As described, in Samba 2.0.4 the parameters :</P +>Finally, don't forget to copy the winbind pam modules from +the source directory in which you originally compiled the new +SAMBA up to the /lib/security directory so that pam can use it:</P ><P ><TT -CLASS="PARAMETER" -><I ->create mask</I -></TT -></P +CLASS="PROMPT" +>root# </TT +> cp ../samba/source/nsswitch/pam_winbind.so /lib/security</P +></DIV +></DIV +></DIV +><DIV +CLASS="SECT1" +><HR><H1 +CLASS="SECT1" +><A +NAME="AEN1880" +>9.6. Limitations</A +></H1 ><P -><TT -CLASS="PARAMETER" -><I ->force create mode</I -></TT -></P +>Winbind has a number of limitations in its current + released version that we hope to overcome in future + releases:</P ><P -><TT -CLASS="PARAMETER" -><I ->directory mask</I -></TT ></P +><UL +><LI ><P -><TT -CLASS="PARAMETER" -><I ->force directory mode</I -></TT -></P +>Winbind is currently only available for + the Linux operating system, although ports to other operating + systems are certainly possible. For such ports to be feasible, + we require the C library of the target operating system to + support the Name Service Switch and Pluggable Authentication + Modules systems. This is becoming more common as NSS and + PAM gain support among UNIX vendors.</P +></LI +><LI ><P ->were used instead of the parameters discussed here.</P +>The mappings of Windows NT RIDs to UNIX ids + is not made algorithmically and depends on the order in which + unmapped users or groups are seen by winbind. It may be difficult + to recover the mappings of rid to UNIX id mapping if the file + containing this information is corrupted or destroyed.</P +></LI +><LI +><P +>Currently the winbind PAM module does not take + into account possible workstation and logon time restrictions + that may be been set for Windows NT users.</P +></LI +></UL ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1800" ->9.7. Interaction with the standard Samba file attribute - mapping</A +NAME="AEN1890" +>9.7. Conclusion</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 +>The winbind system, through the use of the Name Service + Switch, Pluggable Authentication Modules, and appropriate + Microsoft RPC calls have allowed us to provide seamless + integration of Microsoft Windows NT domain users on a + UNIX system. The result is a great reduction in the administrative + cost of running a mixed UNIX and NT network.</P ></DIV ></DIV ><DIV CLASS="CHAPTER" ><HR><H1 ><A -NAME="AEN1810" +NAME="OS2" >Chapter 10. OS2 Client HOWTO</A ></H1 ><DIV @@ -8540,7 +9105,7 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1821" +NAME="AEN1904" >10.1. FAQs</A ></H1 ><DIV @@ -8548,7 +9113,7 @@ CLASS="SECT2" ><H2 CLASS="SECT2" ><A -NAME="AEN1823" +NAME="AEN1906" >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 +9172,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1838" +NAME="AEN1921" >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 +9225,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1847" +NAME="AEN1930" >10.1.3. Are there any other issues when OS/2 (any version) is used as a client?</A ></H2 @@ -8682,7 +9247,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1851" +NAME="AEN1934" >10.1.4. How do I get printer driver download working for OS/2 clients?</A ></H2 @@ -8694,7 +9259,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 +9295,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 +9303,14 @@ CLASS="SECT1" ><H1 CLASS="SECT1" ><A -NAME="AEN1867" +NAME="AEN1950" >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 +9325,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN1872" +NAME="AEN1955" >11.2. CVS Access to samba.org</A ></H1 ><P @@ -8773,7 +9338,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1875" +NAME="AEN1958" >11.2.1. Access via CVSweb</A ></H2 ><P @@ -8794,14 +9359,14 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN1880" +NAME="AEN1963" >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 +9463,20 @@ CLASS="COMMAND" ></DIV ></DIV ></DIV +><HR><H1 +><A +NAME="AEN1991" +>Index</A +></H1 +><DL +><DT +>Primary Domain Controller, + <A +HREF="x1096.htm" +>Background</A +> + </DT +></DL ></DIV ></BODY ></HTML diff --git a/docs/htmldocs/Samba-PDC-HOWTO.html b/docs/htmldocs/Samba-PDC-HOWTO.html index 883de3a0ab..f9bde08898 100644 --- a/docs/htmldocs/Samba-PDC-HOWTO.html +++ b/docs/htmldocs/Samba-PDC-HOWTO.html @@ -19,7 +19,7 @@ CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="AEN1" +NAME="SAMBA-PDC" >How to Configure Samba 2.2 as a Primary Domain Controller</A ></H1 ><HR></DIV @@ -32,9 +32,9 @@ NAME="AEN3" >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" @@ -45,7 +45,7 @@ CLASS="FILENAME" ></A > manpage and the <A -HREF="EMCRYPTION.html" +HREF="ENCRYPTION.html" TARGET="_top" >Encryption chapter</A > @@ -71,12 +71,12 @@ CLASS="EMPHASIS" >Author's Note :</I > 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 @@ -214,7 +214,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN49" +NAME="AEN51" >Configuring the Samba Domain Controller</A ></H1 ><P @@ -410,16 +410,11 @@ CLASS="FILENAME" >As Samba 2.2 does not offer a complete implementation of group mapping between Windows NT groups and UNIX groups (this is really quite complicated to explain in a short space), you should refer to the <A -HREF="smb.conf.5.html#DOMAINADMINUSERS" -TARGET="_top" ->domain -admin users</A -> and <A HREF="smb.conf.5.html#DOMAINADMINGROUP" TARGET="_top" >domain admin group</A -> smb.conf parameters for information of creating a Domain Admins +> smb.conf parameter for information of creating "Domain Admins" style accounts.</P ></DIV ><DIV @@ -427,7 +422,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN92" +NAME="AEN93" >Creating Machine Trust Accounts and Joining Clients to the Domain</A ></H1 @@ -435,7 +430,7 @@ to the Domain</A >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 @@ -468,7 +463,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 @@ -485,7 +480,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN106" +NAME="AEN107" >Manually creating machine trust accounts</A ></H2 ><P @@ -504,9 +499,20 @@ CLASS="PROMPT" >/usr/sbin/useradd -g 100 -d /dev/null -c <TT CLASS="REPLACEABLE" ><I ->machine_nickname</I +>"machine +nickname"</I +></TT +> -s /bin/false <TT +CLASS="REPLACEABLE" +><I +>machine_name</I ></TT -> -m -s /bin/false <TT +>$ </P +><P +><TT +CLASS="PROMPT" +>root# </TT +>passwd -l <TT CLASS="REPLACEABLE" ><I >machine_name</I @@ -546,7 +552,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 @@ -576,7 +582,7 @@ CLASS="REPLACEABLE" ><I >machine_name</I ></TT -> is the machine's netbios +> is the machine's NetBIOS name. </P ><DIV CLASS="WARNING" @@ -602,7 +608,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 @@ -616,7 +622,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN134" +NAME="AEN138" >Creating machine trust accounts "on the fly"</A ></H2 ><P @@ -646,7 +652,7 @@ CLASS="EMPHASIS" <I CLASS="EMPHASIS" >SHOULD</I -> be set to s different password that the +> be set to a different password that the associated <TT CLASS="FILENAME" >/etc/passwd</TT @@ -658,7 +664,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN145" +NAME="AEN149" >Common Problems and Errors</A ></H1 ><P @@ -781,8 +787,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 @@ -808,7 +814,7 @@ CLASS="EMPHASIS" 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 @@ -853,7 +859,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN193" +NAME="AEN197" >System Policies and Profiles</A ></H1 ><P @@ -920,7 +926,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, @@ -1015,7 +1021,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN237" +NAME="AEN241" >What other help can I get ?</A ></H1 ><P @@ -1036,7 +1042,7 @@ CLASS="EMPHASIS" </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). @@ -1092,7 +1098,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 @@ -1347,7 +1353,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 @@ -1417,7 +1423,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN351" +NAME="AEN355" >Domain Control for Windows 9x/ME</A ></H1 ><DIV @@ -1455,7 +1461,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 @@ -1535,7 +1541,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 @@ -1553,7 +1559,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN381" +NAME="AEN385" >Configuration Instructions: Network Logons</A ></H2 ><P @@ -1636,7 +1642,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 @@ -1686,7 +1692,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 @@ -1715,7 +1721,7 @@ CLASS="SECT2" ><HR><H2 CLASS="SECT2" ><A -NAME="AEN415" +NAME="AEN419" >Configuration Instructions: Setting up Roaming User Profiles</A ></H2 ><DIV @@ -1752,7 +1758,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, @@ -1763,7 +1769,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN423" +NAME="AEN427" >Windows NT Configuration</A ></H3 ><P @@ -1798,7 +1804,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN431" +NAME="AEN435" >Windows 9X Configuration</A ></H3 ><P @@ -1829,7 +1835,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN439" +NAME="AEN443" >Win9X and WinNT Configuration</A ></H3 ><P @@ -1858,7 +1864,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN446" +NAME="AEN450" >Windows 9X Profile Setup</A ></H3 ><P @@ -1867,7 +1873,7 @@ as are folders "Start Menu", "Desktop", "Programs" and "Nethood". These directories and their contents will be merged with the local versions stored in c:\windows\profiles\username on subsequent logins, taking the most recent from each. You will need to use the [global] -options "preserve case = yes", "short case preserve = yes" and +options "preserve case = yes", "short preserve case = yes" and "case sensitive = no" in order to maintain capital letters in shortcuts in any of the profile folders.</P ><P @@ -1983,7 +1989,7 @@ CLASS="EMPHASIS" ></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 @@ -2015,7 +2021,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN482" +NAME="AEN486" >Windows NT Workstation 4.0</A ></H3 ><P @@ -2077,11 +2083,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 @@ -2097,7 +2103,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN495" +NAME="AEN499" >Windows NT Server</A ></H3 ><P @@ -2111,7 +2117,7 @@ CLASS="SECT3" ><HR><H3 CLASS="SECT3" ><A -NAME="AEN498" +NAME="AEN502" >Sharing Profiles between W95 and NT Workstation 4.0</A ></H3 ><DIV @@ -2176,7 +2182,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN508" +NAME="AEN512" >DOMAIN_CONTROL.txt : Windows NT Domain Control & Samba</A ></H1 ><DIV @@ -2274,7 +2280,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 @@ -2285,7 +2291,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 diff --git a/docs/htmldocs/UNIX_INSTALL.html b/docs/htmldocs/UNIX_INSTALL.html index 34f4ed9283..7194e1154e 100644 --- a/docs/htmldocs/UNIX_INSTALL.html +++ b/docs/htmldocs/UNIX_INSTALL.html @@ -19,7 +19,7 @@ CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="AEN1" +NAME="INSTALL" >How to Install and Test SAMBA</A ></H1 ><HR></DIV @@ -84,7 +84,7 @@ CLASS="USERINPUT" ></P ><P >first to see what special options you can enable. - Then exectuting</P + Then executing</P ><P ><TT CLASS="PROMPT" @@ -202,7 +202,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" @@ -249,7 +249,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" @@ -358,7 +358,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 @@ -371,7 +371,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 @@ -637,7 +637,7 @@ NAME="AEN162" >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 @@ -736,20 +736,25 @@ NAME="AEN182" The second is the "deny modes" that are specified when a file is open.</P ><P ->Samba supports "record locking" using the fcntl() unix system - call. This is often implemented using rpc calls to a rpc.lockd process - running on the system that owns the filesystem. Unfortunately many - rpc.lockd implementations are very buggy, particularly when made to - talk to versions from other vendors. It is not uncommon for the - rpc.lockd to crash.</P -><P ->There is also a problem translating the 32 bit lock - requests generated by PC clients to 31 bit requests supported - by most unixes. Unfortunately many PC applications (typically - OLE2 applications) use byte ranges with the top bit set - as semaphore sets. Samba attempts translation to support - these types of applications, and the translation has proved - to be quite successful.</P +>Record locking semantics under Unix is very + different from record locking under Windows. Versions + of Samba before 2.2 have tried to use the native + fcntl() unix system call to implement proper record + locking between different Samba clients. This can not + be fully correct due to several reasons. The simplest + is the fact that a Windows client is allowed to lock a + byte range up to 2^32 or 2^64, depending on the client + OS. The unix locking only supports byte ranges up to + 2^31. So it is not possible to correctly satisfy a + lock request above 2^31. There are many more + differences, too many to be listed here.</P +><P +>Samba 2.2 and above implements record locking + completely independent of the underlying unix + system. If a byte range lock that the client requests + happens to fall into the range 0-2^31, Samba hands + this request down to the Unix system. All other locks + can not be seen by unix anyway.</P ><P >Strictly a SMB server should check for locks before every read and write call on a file. Unfortunately with the @@ -771,7 +776,7 @@ NAME="AEN182" 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". @@ -804,7 +809,7 @@ NAME="AEN195" ><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 diff --git a/docs/htmldocs/lmhosts.5.html b/docs/htmldocs/lmhosts.5.html index 47df4a9733..13b162ce44 100644 --- a/docs/htmldocs/lmhosts.5.html +++ b/docs/htmldocs/lmhosts.5.html @@ -50,7 +50,7 @@ NAME="AEN12" ><H2 >DESCRIPTION</H2 ><P ->This file is part of the <<A +>This file is part of the <A HREF="samba.7.html" TARGET="_top" > Samba</A diff --git a/docs/htmldocs/make_unicodemap.1.html b/docs/htmldocs/make_unicodemap.1.html index a0b8740693..b8b768ce40 100644 --- a/docs/htmldocs/make_unicodemap.1.html +++ b/docs/htmldocs/make_unicodemap.1.html @@ -58,7 +58,7 @@ TARGET="_top" CLASS="COMMAND" >make_unicodemap</B > compiles text unicode map - files into binary unicodef map files for use with the + files into binary unicode map files for use with the internationalization features of Samba 2.2. </P ></DIV diff --git a/docs/htmldocs/msdfs_setup.html b/docs/htmldocs/msdfs_setup.html index 7bf6664dc6..36b9911bae 100644 --- a/docs/htmldocs/msdfs_setup.html +++ b/docs/htmldocs/msdfs_setup.html @@ -19,7 +19,7 @@ CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="AEN1" +NAME="MSDFS" >Hosting a Microsoft Distributed File System tree on Samba</A ></H1 ><HR></DIV diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html index 4b2c39dc4a..31afa11cf8 100644 --- a/docs/htmldocs/nmbd.8.html +++ b/docs/htmldocs/nmbd.8.html @@ -36,7 +36,7 @@ NAME="AEN8" ><P ><B CLASS="COMMAND" ->smbd</B +>nmbd</B > [-D] [-a] [-o] [-P] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log file>] [-n <primary netbios name>] [-p <port number>] [-s <configuration file>]</P ></DIV ><DIV @@ -539,7 +539,7 @@ CLASS="COMMAND" CLASS="COMMAND" >nmbd</B > will accept SIGHUP, which will cause - it to dump out it's namelists into the file <TT + it to dump out its namelists into the file <TT CLASS="FILENAME" >namelist.debug </TT @@ -555,27 +555,29 @@ CLASS="FILENAME" cause <B CLASS="COMMAND" >nmbd</B -> to dump out it's server database in +> to dump out its server database in the <TT CLASS="FILENAME" >log.nmb</TT -> file. In addition, the debug log level - of nmbd may be raised by sending it a SIGUSR1 (<B -CLASS="COMMAND" ->kill -USR1 - <nmbd-pid></B ->) and lowered by sending it a - SIGUSR2 (<B +> file.</P +><P +>The debug log level of nmbd may be raised or lowered using + <A +HREF="smbcontrol.1.html" +TARGET="_top" +><B CLASS="COMMAND" ->kill -USR2 <nmbd-pid></B ->). This is to - allow transient problems to be diagnosed, whilst still running at a - normally low log level.</P +>smbcontrol(1)</B +> + </A +> (SIGUSR[1|2] signals are no longer used in Samba 2.2). This is + to allow transient problems to be diagnosed, whilst still running + at a normally low log level.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN186" +NAME="AEN187" ></A ><H2 >VERSION</H2 @@ -586,7 +588,7 @@ NAME="AEN186" ><DIV CLASS="REFSECT1" ><A -NAME="AEN189" +NAME="AEN190" ></A ><H2 >SEE ALSO</H2 @@ -651,7 +653,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN206" +NAME="AEN207" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/nmblookup.1.html b/docs/htmldocs/nmblookup.1.html index 0cce300074..c87d7d35db 100644 --- a/docs/htmldocs/nmblookup.1.html +++ b/docs/htmldocs/nmblookup.1.html @@ -128,7 +128,7 @@ CLASS="CONSTANT" datagrams. The reason for this option is a bug in Windows 95 where it ignores the source port of the requesting packet and only replies to UDP port 137. Unfortunately, on most UNIX - systems root privilage is needed to bind to this port, and + systems root privilege is needed to bind to this port, and in addition, if the <A HREF="nmbd.8.html" TARGET="_top" diff --git a/docs/htmldocs/printer_driver2.html b/docs/htmldocs/printer_driver2.html index c44d9c5bf8..e6cc23b02c 100644 --- a/docs/htmldocs/printer_driver2.html +++ b/docs/htmldocs/printer_driver2.html @@ -19,7 +19,7 @@ CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="AEN1" +NAME="PRINTING" >Printing Support in Samba 2.2.x</A ></H1 ><HR></DIV @@ -192,14 +192,21 @@ 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 ><P ><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 @@ -209,7 +216,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 ></P ><P >The <A @@ -224,7 +231,7 @@ CLASS="PARAMETER" > is used to allow administrative level user accounts to have write access in order to update files on the share. See the <A -HREF="smb./conf.5.html" +HREF="smb.conf.5.html" TARGET="_top" >smb.conf(5) man page</A @@ -514,7 +521,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 @@ -788,7 +795,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 @@ -830,52 +837,67 @@ NAME="MIGRATION" ><P >Given that printer driver management has changed (we hope improved) in 2.2 over prior releases, migration from an existing setup to 2.2 can -follow several paths.</P +follow several paths. Here are the possible scenarios for +migration:</P ><P ->Windows clients have a tendency to remember things for quite a while. -For example, if a Windows NT client has attached to a Samba 2.0 server, -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 +><UL +><LI ><P ->In order to give an NT client printing "amesia" (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 -CLASS="CONSTANT" ->[HKLM\SYSTEM\CurrentControlSet\Control\Print]</TT ->. The -spooler service on the client should be stopped prior to doing this:</P +>If you do not desire the new Windows NT + print driver support, nothing needs to be done. + All existing parameters work the same.</P +></LI +><LI ><P -><TT -CLASS="PROMPT" ->C:\WINNT\ ></TT -> <TT -CLASS="USERINPUT" -><B ->net stop spooler</B -></TT -></P +>If you want to take advantage of NT printer + driver support but do not want to migrate the + 9x drivers to the new setup, the leave the existing + <TT +CLASS="FILENAME" +>printers.def</TT +> file. When smbd attempts + to locate a + 9x driver for the printer in the TDB and fails it + will drop down to using the printers.def (and all + associated parameters). The <B +CLASS="COMMAND" +>make_printerdef</B +> + tool will also remain for backwards compatibility but will + be removed in the next major release.</P +></LI +><LI ><P -><I -CLASS="EMPHASIS" ->All the normal disclaimers about editing the registry go -here.</I -> Be careful, and know what you are doing.</P +>If you install a Windows 9x driver for a printer + on your Samba host (in the printing TDB), this information will + take precedence and the three old printing parameters + will be ignored (including print driver location).</P +></LI +><LI ><P ->The spooler service should be restarted after you have finished -removing the appropriate registry entries by replacing the -<B +>If you want to migrate an existing <TT +CLASS="FILENAME" +>printers.def</TT +> + file into the new setup, the current only solution is to use the Windows + NT APW to install the NT drivers and the 9x drivers. This can be scripted + using <B CLASS="COMMAND" ->stop</B -> command above with <B +>smbclient</B +> and <B CLASS="COMMAND" ->start</B ->.</P -><P ->Windows 9x clients will continue to use LanMan printing calls -with a 2.2 Samba server so there is no need to perform any of these -modifications on non-NT clients.</P +>rpcclient</B +>. See the + Imprints installation client at <A +HREF="http://imprints.sourceforge.net/" +TARGET="_top" +>http://imprints.sourceforge.net/</A +> + for an example. + </P +></LI +></UL ><DIV CLASS="WARNING" ><P @@ -895,8 +917,12 @@ ALIGN="CENTER" ><TD ALIGN="LEFT" ><P ->The following smb.conf parameters are considered to be depreciated and will -be removed soon. Do not use them in new installations</P +>The following <TT +CLASS="FILENAME" +>smb.conf</TT +> parameters are considered to +be deprecated and will be removed soon. Do not use them in new +installations</P ><P ></P ><UL @@ -936,63 +962,22 @@ CLASS="PARAMETER" ></TABLE ></DIV ><P ->Here are the possible scenarios for supporting migration:</P -><P -></P -><UL -><LI -><P ->If you do not desire the new Windows NT - print driver support, nothing needs to be done. - All existing parameters work the same.</P -></LI -><LI -><P ->If you want to take advantage of NT printer - driver support but do not want to migrate the - 9x drivers to the new setup, the leave the existing - printers.def file. When smbd attempts to locate a - 9x driver for the printer in the TDB and fails it - will drop down to using the printers.def (and all - associated parameters). The <B -CLASS="COMMAND" ->make_printerdef</B -> - tool will also remain for backwards compatibility but will - be moved to the "this tool is the old way of doing it" - pile.</P -></LI -><LI -><P ->If you install a Windows 9x driver for a printer - on your Samba host (in the printing TDB), this information will - take precedence and the three old printing parameters - will be ignored (including print driver location).</P -></LI -><LI -><P ->If you want to migrate an existing <TT -CLASS="FILENAME" ->printers.def</TT -> - file into the new setup, the current only solution is to use the Windows - NT APW to install the NT drivers and the 9x drivers. This can be scripted - using <B -CLASS="COMMAND" ->smbclient</B -> and <B -CLASS="COMMAND" ->rpcclient</B ->. See the - Imprints installation client at <A -HREF="http://imprints.sourceforge.net/" -TARGET="_top" ->http://imprints.sourceforge.net/</A -> - for an example. - </P -></LI -></UL +>The have been two new parameters add in Samba 2.2.2 to for +better support of Samba 2.0.x backwards capability (<TT +CLASS="PARAMETER" +><I +>disable +spoolss</I +></TT +>) and for using local printers drivers on Windows +NT/2000 clients (<TT +CLASS="PARAMETER" +><I +>use client driver</I +></TT +>). Both of +these options are described in the smb.coinf(5) man page and are +disabled by default.</P ></DIV ></DIV ></BODY diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html index 9c19660a46..53a0ea98dd 100644 --- a/docs/htmldocs/rpcclient.1.html +++ b/docs/htmldocs/rpcclient.1.html @@ -137,7 +137,10 @@ CLASS="PROGRAMLISTING" ><P >set the debuglevel. Debug level 0 is the lowest and 100 being the highest. This should be set to 100 if you are - planning on submitting a bug report to the Samba team (see BUGS.txt). + planning on submitting a bug report to the Samba team (see <TT +CLASS="FILENAME" +>BUGS.txt</TT +>). </P ></DD ><DT @@ -152,7 +155,10 @@ CLASS="PROGRAMLISTING" ><DD ><P >File name for log/debug files. The extension - '.client' will be appended. The log file is never removed + <TT +CLASS="CONSTANT" +>'.client'</TT +> will be appended. The log file is never removed by the client. </P ></DD @@ -199,7 +205,7 @@ CLASS="ENVAR" <TT CLASS="ENVAR" >LOGNAME</TT -> variable and if either exist, the +> variable and if either exists, the string is uppercased. If these environmental variables are not found, the username <TT CLASS="CONSTANT" @@ -247,7 +253,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN90" +NAME="AEN92" ></A ><H2 >COMMANDS</H2 @@ -641,7 +647,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN210" +NAME="AEN212" ></A ><H2 >BUGS</H2 @@ -663,7 +669,7 @@ CLASS="COMMAND" available from the original creators (Microsoft) on how MSRPC over SMB works, or how the individual MSRPC services work. Microsoft's implementation of these services has been demonstrated (and reported) - to be... a bit flakey in places. </P + to be... a bit flaky in places. </P ><P >The development of Samba's implementation is also a bit rough, and as more of the services are understood, it can even result in @@ -682,7 +688,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN220" +NAME="AEN222" ></A ><H2 >VERSION</H2 @@ -693,7 +699,7 @@ NAME="AEN220" ><DIV CLASS="REFSECT1" ><A -NAME="AEN223" +NAME="AEN225" ></A ><H2 >AUTHOR</H2 @@ -704,7 +710,7 @@ NAME="AEN223" to the way the Linux kernel is developed.</P ><P >The original rpcclient man page was written by Matthew - Geddes, Luke Kenneth Casson, and rewriten by Gerald Carter. + Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter. The conversion to DocBook for Samba 2.2 was done by Gerald Carter.</P ></DIV diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html index 3a2a99a1f3..5fe4f3cf97 100644 --- a/docs/htmldocs/smb.conf.5.html +++ b/docs/htmldocs/smb.conf.5.html @@ -758,7 +758,7 @@ CLASS="VARIABLELIST" upper case, or if they are forced to be the "default" case. This option can be use with "preserve case = yes" to permit long filenames to retain their case, while short names - are lowered. Default <EM + are lowercased. Default <EM >yes</EM >.</P ></DD @@ -810,7 +810,7 @@ CLASS="REPLACEABLE" ></LI ><LI ><P ->The client's netbios name and any previously +>The client's NetBIOS name and any previously used user names are checked against the supplied password, if they match then the connection is allowed as the corresponding user.</P @@ -861,6 +861,18 @@ NAME="AEN254" ><LI ><P ><A +HREF="#ABORTSHUTDOWNSCRIPT" +><TT +CLASS="PARAMETER" +><I +>abort shutdown script</I +></TT +></A +></P +></LI +><LI +><P +><A HREF="#ADDPRINTERCOMMAND" ><TT CLASS="PARAMETER" @@ -897,6 +909,18 @@ CLASS="PARAMETER" ><LI ><P ><A +HREF="#ADDMACHINESCRIPT" +><TT +CLASS="PARAMETER" +><I +>add machine script</I +></TT +></A +></P +></LI +><LI +><P +><A HREF="#ALLOWTRUSTEDDOMAINS" ><TT CLASS="PARAMETER" @@ -1197,6 +1221,18 @@ CLASS="PARAMETER" ><LI ><P ><A +HREF="#DISABLESPOOLSS" +><TT +CLASS="PARAMETER" +><I +>disable spoolss</I +></TT +></A +></P +></LI +><LI +><P +><A HREF="#DNSPROXY" ><TT CLASS="PARAMETER" @@ -1317,6 +1353,18 @@ CLASS="PARAMETER" ><LI ><P ><A +HREF="#HIDEUNREADABLE" +><TT +CLASS="PARAMETER" +><I +>hide unreadable</I +></TT +></A +></P +></LI +><LI +><P +><A HREF="#HOMEDIRMAP" ><TT CLASS="PARAMETER" @@ -1401,6 +1449,18 @@ CLASS="PARAMETER" ><LI ><P ><A +HREF="#LARGEREADWRITE" +><TT +CLASS="PARAMETER" +><I +>large readwrite</I +></TT +></A +></P +></LI +><LI +><P +><A HREF="#LMANNOUNCE" ><TT CLASS="PARAMETER" @@ -2229,6 +2289,18 @@ CLASS="PARAMETER" ><LI ><P ><A +HREF="#SHUTDOWNSCRIPT" +><TT +CLASS="PARAMETER" +><I +>shutdown script</I +></TT +></A +></P +></LI +><LI +><P +><A HREF="#SMBPASSWDFILE" ><TT CLASS="PARAMETER" @@ -2637,6 +2709,18 @@ CLASS="PARAMETER" ><LI ><P ><A +HREF="#UTMP" +><TT +CLASS="PARAMETER" +><I +>utmp</I +></TT +></A +></P +></LI +><LI +><P +><A HREF="#UTMPDIRECTORY" ><TT CLASS="PARAMETER" @@ -2673,6 +2757,30 @@ CLASS="PARAMETER" ><LI ><P ><A +HREF="#WINBINDENUMUSERS" +><TT +CLASS="PARAMETER" +><I +>winbind enum users</I +></TT +></A +></P +></LI +><LI +><P +><A +HREF="#WINBINDENUMGROUPS" +><TT +CLASS="PARAMETER" +><I +>winbind enum groups</I +></TT +></A +></P +></LI +><LI +><P +><A HREF="#WINBINDGID" ><TT CLASS="PARAMETER" @@ -2783,7 +2891,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN898" +NAME="AEN934" ></A ><H2 >COMPLETE LIST OF SERVICE PARAMETERS</H2 @@ -3936,18 +4044,6 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#SHAREMODES" -><TT -CLASS="PARAMETER" -><I ->share modes</I -></TT -></A -></P -></LI -><LI -><P -><A HREF="#SHORTPRESERVECASE" ><TT CLASS="PARAMETER" @@ -4008,11 +4104,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#USER" +HREF="#USECLIENTDRIVER" ><TT CLASS="PARAMETER" ><I ->user</I +>use client driver</I ></TT ></A ></P @@ -4020,11 +4116,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#USERNAME" +HREF="#USER" ><TT CLASS="PARAMETER" ><I ->username</I +>user</I ></TT ></A ></P @@ -4032,11 +4128,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#USERS" +HREF="#USERNAME" ><TT CLASS="PARAMETER" ><I ->users</I +>username</I ></TT ></A ></P @@ -4044,11 +4140,11 @@ CLASS="PARAMETER" ><LI ><P ><A -HREF="#UTMP" +HREF="#USERS" ><TT CLASS="PARAMETER" ><I ->utmp</I +>users</I ></TT ></A ></P @@ -4202,7 +4298,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN1370" +NAME="AEN1402" ></A ><H2 >EXPLANATION OF EACH PARAMETER</H2 @@ -4213,6 +4309,46 @@ CLASS="VARIABLELIST" ><DL ><DT ><A +NAME="ABORTSHUTDOWNSCRIPT" +></A +>abort shutdown script (G)</DT +><DD +><P +><EM +>This parameter only exists in the HEAD cvs branch</EM +> + This a full path name to a script called by + <A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbd(8)</B +></A +> that + should stop a shutdown procedure issued by the <A +HREF="#SHUTDOWNSCRIPT" +><TT +CLASS="PARAMETER" +><I +>shutdown script</I +></TT +></A +>.</P +><P +>This command will be run as user.</P +><P +>Default: <EM +>None</EM +>.</P +><P +>Example: <B +CLASS="COMMAND" +>abort shutdown script = /sbin/shutdown -c</B +></P +></DD +><DT +><A NAME="ADDPRINTERCOMMAND" ></A >add printer command (G)</DT @@ -4226,7 +4362,7 @@ NAME="ADDPRINTERCOMMAND" NT/2000 print server.</P ><P >For a Samba host this means that the printer must be - physically added to underlying printing system. The <TT + physically added to the underlying printing system. The <TT CLASS="PARAMETER" ><I >add @@ -4521,6 +4657,37 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="ADDMACHINESCRIPT" +></A +>add machine script (G)</DT +><DD +><P +>This is the full pathname to a script that will + be run by <A +HREF="smbd.8.html" +TARGET="_top" +>smbd(8)</A +> when a machine is added + to it's domain using the administrator username and password method. </P +><P +>This option is only required when using sam back-ends tied to the + Unix uid method of RID calculation such as smbpasswd. This option is only + available in Samba 3.0.</P +><P +>Default: <B +CLASS="COMMAND" +>add machine script = <empty string> + </B +></P +><P +>Example: <B +CLASS="COMMAND" +>add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u + </B +></P +></DD +><DT +><A NAME="ADDUSERSCRIPT" ></A >add user script (G)</DT @@ -4729,7 +4896,11 @@ CLASS="CONSTANT" >domain</TT >. If it is set to no, then attempts to connect to a resource from - a domain or workgroup other than the one which smbd is running + a domain or workgroup other than the one which <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> is running in will fail, even if that domain is trusted by the remote server doing the authentication.</P ><P @@ -4787,7 +4958,7 @@ CLASS="COMMAND" ><A NAME="ANNOUNCEVERSION" ></A ->annouce version (G)</DT +>announce version (G)</DT ><DD ><P >This specifies the major and minor version numbers @@ -4797,7 +4968,7 @@ NAME="ANNOUNCEVERSION" ><P >Default: <B CLASS="COMMAND" ->announce version = 4.2</B +>announce version = 4.5</B ></P ><P >Example: <B @@ -4854,7 +5025,7 @@ NAME="BINDINTERFACESONLY" ><DD ><P >This global parameter allows the Samba admin - to limit what interfaces on a machine will serve smb requests. If + to limit what interfaces on a machine will serve SMB requests. If affects file service <A HREF="smbd.8.html" TARGET="_top" @@ -5084,7 +5255,7 @@ TARGET="_top" ><P >If this parameter is set to <TT CLASS="CONSTANT" ->False</TT +>false</TT >, then Samba 2.2 will behave as previous versions of Samba would and will fail the lock request immediately if the lock range @@ -5362,7 +5533,11 @@ NAME="CHARACTERSET" >character set (G)</DT ><DD ><P ->This allows a smbd to map incoming filenames +>This allows <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> to map incoming filenames from a DOS Code page (see the <A HREF="#CLIENTCODEPAGE" >client @@ -5749,7 +5924,7 @@ CLASS="COMMAND" ><A NAME="CODINGSYSTEM" ></A ->codingsystem (G)</DT +>coding system (G)</DT ><DD ><P >This parameter is used to determine how incoming @@ -6137,7 +6312,11 @@ NAME="DEBUGPID" ><DD ><P >When using only one log file for more then one - forked smbd-process there may be hard to follow which process + forked <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +>-process there may be hard to follow which process outputs which message. This boolean parameter is adds the process-id to the timestamp message headers in the logfile when turned on.</P ><P @@ -6547,7 +6726,7 @@ HREF="#ADDSHARECOMMAND" ><TT CLASS="PARAMETER" ><I ->delete share +>add share command</I ></TT ></A @@ -6557,7 +6736,7 @@ HREF="#CHANGESHARECOMMAND" CLASS="PARAMETER" ><I >change - share</I + share command</I ></TT ></A >. @@ -6763,13 +6942,16 @@ CLASS="PARAMETER" ></TT ></A > - option). If this option is set to False (the default) then if a vetoed + option). If this option is set to <TT +CLASS="CONSTANT" +>false</TT +> (the default) then if a vetoed directory contains any non-vetoed files or directories then the directory delete will fail. This is usually what you want.</P ><P >If this option is set to <TT CLASS="CONSTANT" ->True</TT +>true</TT >, then Samba will attempt to recursively delete any files and directories within the vetoed directory. This can be useful for integration with file @@ -7080,7 +7262,10 @@ NAME="DIRECTORYSECURITYMASK" Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave - it as the default of 0777.</P + it as the default of <TT +CLASS="CONSTANT" +>0777</TT +>.</P ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" @@ -7122,6 +7307,38 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="DISABLESPOOLSS" +></A +>disable spoolss (G)</DT +><DD +><P +>Enabling this parameter will disables Samba's support + for the SPOOLSS set of MS-RPC's and will yield identical behavior + as Samba 2.0.x. Windows NT/2000 clients will downgrade to using + Lanman style printing commands. Windows 9x/ME will be uneffected by + the parameter. However, this will also disable the ability to upload + printer drivers to a Samba server via the Windows NT Add Printer + Wizard or by using the NT printer properties dialog window. It will + also disable the capability of Windows NT/2000 clients to download + print drivers from the Samba host upon demand. + <EM +>Be very careful about enabling this parameter.</EM +> + </P +><P +>See also <A +HREF="#USECLIENTDRIVER" +>use client driver</A +> + </P +><P +>Default : <B +CLASS="COMMAND" +>disable spoolss = no</B +></P +></DD +><DT +><A NAME="DNSPROXY" ></A >dns proxy (G)</DT @@ -7268,7 +7485,10 @@ NAME="DOMAINLOGONS" >domain logons (G)</DT ><DD ><P ->If set to true, the Samba server will serve +>If set to <TT +CLASS="CONSTANT" +>true</TT +>, the Samba server will serve Windows 95/98 Domain logons for the <A HREF="#WORKGROUP" > <TT @@ -7447,7 +7667,7 @@ NAME="DOSFILEMODE" ><DD ><P > The default behavior in Samba is to provide - UNIX-like behavor where only the owner of a file/directory is + UNIX-like behavior where only the owner of a file/directory is able to change the permissions on it. However, this behavior is often confusing to DOS/Windows users. Enabling this parameter allows a user who has write access to the file (by whatever @@ -7516,8 +7736,12 @@ CLASS="COMMAND" > is acting on behalf of is not the file owner. Setting this option to <TT CLASS="CONSTANT" -> True</TT -> allows DOS semantics and smbd will change the file +> true</TT +> allows DOS semantics and <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> will change the file timestamp as DOS requires.</P ><P >Default: <B @@ -7590,18 +7814,15 @@ NAME="ENHANCEDBROWSING" ><DD ><P >This option enables a couple of enhancements to - cross-subnet browse propogation that have been added in Samba + cross-subnet browse propagation that have been added in Samba but which are not standard in Microsoft implementations. - <EM ->These enhancements are currently only available in - the HEAD Samba CVS tree (not Samba 2.2.x).</EM -></P + </P ><P ->The first enhancement to browse propogation consists of a regular +>The first enhancement to browse propagation consists of a regular wildcard query to a Samba WINS server for all Domain Master Browsers, - followed by a browse synchronisation with each of the returned + followed by a browse synchronization with each of the returned DMBs. The second enhancement consists of a regular randomised browse - synchronisation with all currently known DMBs.</P + synchronization with all currently known DMBs.</P ><P >You may wish to disable this option if you have a problem with empty workgroups not disappearing from browse lists. Due to the restrictions @@ -7609,7 +7830,7 @@ NAME="ENHANCEDBROWSING" to stay around forever which can be annoying.</P ><P >In general you should leave this option enabled as it makes - cross-subnet browse propogation much more reliable.</P + cross-subnet browse propagation much more reliable.</P ><P >Default: <B CLASS="COMMAND" @@ -7706,7 +7927,7 @@ NAME="FAKEDIRECTORYCREATETIMES" reported by Samba will be updated whenever a file is created or or deleted in the directory. NMAKE finds all object files in the object directory. The timestamp of the last one built is then - compared to the timestamp of the object dircetory. If the + compared to the timestamp of the object directory. If the directory's timestamp if newer, then all object files will be rebuilt. Enabling this option ensures directories always predate their contents and an NMAKE build @@ -7845,7 +8066,10 @@ CLASS="PARAMETER" mask</I ></TT ></A -> to true.</P +> to <TT +CLASS="CONSTANT" +>true</TT +>.</P ><P >See also the parameter <A HREF="#CREATEMASK" @@ -7917,7 +8141,10 @@ CLASS="PARAMETER" mask</I ></TT ></A -> to true.</P +> to <TT +CLASS="CONSTANT" +>true</TT +>.</P ><P >See also the parameter <A HREF="#DIRECTORYMASK" @@ -8270,7 +8497,7 @@ CLASS="PARAMETER" </A >parameter is set to <TT CLASS="CONSTANT" ->False</TT +>false</TT >.</P ><P >Default: <B @@ -8524,6 +8751,21 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="HIDEUNREADABLE" +></A +>hide unreadable (S)</DT +><DD +><P +>This parameter prevents clients from seeing the + existance of files that cannot be read. Defaults to off.</P +><P +>Default: <B +CLASS="COMMAND" +>hide unreadable = no</B +></P +></DD +><DT +><A NAME="HOMEDIRMAP" ></A >homedir map (G)</DT @@ -8540,7 +8782,7 @@ CLASS="PARAMETER" ></A > is <TT CLASS="CONSTANT" ->True</TT +>true</TT >, and <A HREF="smbd.8.html" TARGET="_top" @@ -8819,7 +9061,7 @@ CLASS="PARAMETER" > hosts equiv</I ></TT > may be useful for NT clients which will - not supply passwords to samba.</P + not supply passwords to Samba.</P ><P ><EM >NOTE :</EM @@ -8978,7 +9220,7 @@ CLASS="PARAMETER" inheritance (the code explicitly prohibits this).</P ><P >This can be particularly useful on large systems with - many users, perhaps several thousand,to allow a single [homes] + many users, perhaps several thousand, to allow a single [homes] share to be used flexibly by each user.</P ><P >See also <A @@ -9131,7 +9373,7 @@ CLASS="PARAMETER" the value <TT CLASS="PARAMETER" ><I ->&+group"</I +>&+group</I ></TT > means check the NIS netgroup database, followed by the UNIX group database (the @@ -9249,12 +9491,9 @@ CLASS="COMMAND" >This parameter defaults to <TT CLASS="CONSTANT" >on</TT -> on systems - that have the support, and <TT -CLASS="CONSTANT" ->off</TT -> on systems that - don't. You should never need to touch this parameter.</P +>, but is translated + to a no-op on systems that no not have the necessary kernel support. + You should never need to touch this parameter.</P ><P >See also the <A HREF="#OPLOCKS" @@ -9288,8 +9527,12 @@ NAME="LANMANAUTH" >lanman auth (G)</DT ><DD ><P ->This parameter determines whether or not smbd will - attempt to authentication users using the LANMAN password hash. +>This parameter determines whether or not <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> will + attempt to authenticate users using the LANMAN password hash. If disabled, only clients which support NT password hashes (e.g. Windows NT/2000 clients, smbclient, etc... but not Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host.</P @@ -9301,6 +9544,31 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="LARGEREADWRITE" +></A +>large readwrite (G)</DT +><DD +><P +>This parameter determines whether or not <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> + supports the new 64k streaming read and write varient SMB requests introduced + with Windows 2000. Note that due to Windows 2000 client redirector bugs + this requires Samba to be running on a 64-bit capable operating system such + as IRIX, Solaris or a Linux 2.4 kernel. Can improve performance by 10% with + Windows 2000 clients. Defaults to off. Not as tested as some other Samba + code paths. + </P +><P +>Default : <B +CLASS="COMMAND" +>large readwrite = no</B +></P +></DD +><DT +><A NAME="LEVEL2OPLOCKS" ></A >level2 oplocks (S)</DT @@ -9352,7 +9620,10 @@ CLASS="PARAMETER" ></TT > </A -> parameter must be set to "true" on this share in order for +> parameter must be set to <TT +CLASS="CONSTANT" +>true</TT +> on this share in order for this parameter to have any effect.</P ><P >See also the <A @@ -9545,13 +9816,19 @@ CLASS="COMMAND" > to try and become a local master browser on a subnet. If set to <TT CLASS="CONSTANT" ->False</TT +>false</TT > then <B CLASS="COMMAND" > nmbd</B > will not attempt to become a local master browser on a subnet and will also lose in all browsing elections. By - default this value is set to true. Setting this value to true doesn't + default this value is set to <TT +CLASS="CONSTANT" +>true</TT +>. Setting this value to <TT +CLASS="CONSTANT" +>true</TT +> doesn't mean that Samba will <EM >become</EM > the local master @@ -9562,7 +9839,10 @@ CLASS="COMMAND" > participate</EM > in elections for local master browser.</P ><P ->Setting this value to False will cause <B +>Setting this value to <TT +CLASS="CONSTANT" +>false</TT +> will cause <B CLASS="COMMAND" >nmbd</B > @@ -9653,7 +9933,7 @@ CLASS="COMMAND" filesystems which <EM >may</EM > not need locking (such as - cdrom drives), although setting this parameter of <TT + CDROM drives), although setting this parameter of <TT CLASS="CONSTANT" >no</TT > @@ -9783,7 +10063,7 @@ CLASS="COMMAND" in a NetUserGetInfo request. Win9X clients truncate the info to \\server\share when a user does <B CLASS="COMMAND" ->net use /home"</B +>net use /home</B > but use the whole string when dealing with profiles.</P ><P @@ -9866,7 +10146,7 @@ CLASS="FILENAME" ><P >The share and the path must be readable by the user for the preferences and directories to be loaded onto the Windows NT - client. The share must be writeable when the logs in for the first + client. The share must be writeable when the user logs in for the first time, in order that the Windows NT client can create the NTuser.dat and other directories.</P ><P @@ -9910,7 +10190,7 @@ NAME="LOGONSCRIPT" >This parameter specifies the batch file (.bat) or NT command file (.cmd) to be downloaded and run on a machine when a user successfully logs in. The file must contain the DOS - style cr/lf line endings. Using a DOS-style editor to create the + style CR/LF line endings. Using a DOS-style editor to create the file is recommended.</P ><P >The script must be a relative path to the [netlogon] @@ -9937,7 +10217,7 @@ CLASS="FILENAME" >/usr/local/samba/netlogon/STARTUP.BAT</TT ></P ><P ->The contents of the batch file is entirely your choice. A +>The contents of the batch file are entirely your choice. A suggested command would be to add <B CLASS="COMMAND" >NET TIME \\SERVER /SET @@ -9994,7 +10274,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. A <TT CLASS="PARAMETER" ><I @@ -10004,7 +10284,7 @@ CLASS="PARAMETER" the job number (an integer). On HPUX (see <TT CLASS="PARAMETER" ><I ->printing = hpux +>printing=hpux </I ></TT >), if the <TT @@ -10175,7 +10455,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. Otherwise it is placed at the end of the command.</P ><P @@ -10245,7 +10525,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. A <TT CLASS="PARAMETER" ><I @@ -10331,7 +10611,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. A <TT CLASS="PARAMETER" ><I @@ -10389,7 +10669,7 @@ NAME="MACHINEPASSWORDTIMEOUT" >machine password timeout (G)</DT ><DD ><P ->If a Samba server is a member of an Windows +>If a Samba server is a member of a Windows NT Domain (see the <A HREF="#SECURITYEQUALSDOMAIN" >security = domain</A @@ -10478,8 +10758,8 @@ NAME="MAGICSCRIPT" executed on behalf of the connected user.</P ><P >Scripts executed in this way will be deleted upon - completion assuming that the user has the appripriate level - of priviledge and the ile permissions allow the deletion.</P + completion assuming that the user has the appropriate level + of privilege and the file permissions allow the deletion.</P ><P >If the script generates output, output will be sent to the file specified by the <A @@ -10541,7 +10821,7 @@ NAME="MANGLEDMAP" ><DD ><P >This is for those who want to directly map UNIX - file names which can not be represented on Windows/DOS. The mangling + file names which cannot be represented on Windows/DOS. The mangling of names is not always what is needed. In particular you may have documents with file extensions that differ between DOS and UNIX. For example, under UNIX it is common to use <TT @@ -10572,7 +10852,7 @@ CLASS="COMMAND" CLASS="FILENAME" >;1 </TT -> off the ends of filenames on some CDROMS (only visible +> off the ends of filenames on some CDROMs (only visible under some UNIXes). To do this use a map of (*;1 *;).</P ><P >Default: <EM @@ -10689,12 +10969,12 @@ TARGET="_top" ><P >The larger this value, the more likely it is that mangled names can be successfully converted to correct long UNIX names. - However, large stack sizes will slow most directory access. Smaller + However, large stack sizes will slow most directory accesses. Smaller stacks save memory in the server (each stack element costs 256 bytes). </P ><P >It is not possible to absolutely guarantee correct long - file names, so be prepared for some surprises!</P + filenames, so be prepared for some surprises!</P ><P >Default: <B CLASS="COMMAND" @@ -11079,7 +11359,7 @@ NAME="MAXMUX" ><DD ><P >This option controls the maximum number of - outstanding simultaneous SMB operations that samba tells the client + outstanding simultaneous SMB operations that Samba tells the client it will allow. You should never need to set this parameter.</P ><P >Default: <B @@ -11252,10 +11532,14 @@ CLASS="COMMAND" ></A > processes concurrently running on a system and is intended - as a stop gap to prevent degrading service to clients in the event + as a stopgap to prevent degrading service to clients in the event that the server has insufficient resources to handle more than this number of connections. Remember that under normal operating - conditions, each user will have an smbd associated with him or her + conditions, each user will have an <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> associated with him or her to handle connections to all shares from a given host. </P ><P @@ -11393,7 +11677,7 @@ CLASS="COMMAND" >. That's why I have the '&' on the end. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover - after 30secs, hopefully).</P + after 30 seconds, hopefully).</P ><P >All messages are delivered as the global guest user. The command takes the standard substitutions, although <TT @@ -11798,7 +12082,7 @@ CLASS="PARAMETER" ><P >Default: <B CLASS="COMMAND" ->name resolve order = lmhosts wins host bcast +>name resolve order = lmhosts host wins bcast </B ></P ><P @@ -12047,7 +12331,7 @@ NAME="OBEYPAMRESTRICTIONS" >obey pam restrictions (G)</DT ><DD ><P ->When Samba 2.2 is configure to enable PAM support +>When Samba 2.2 is configured to enable PAM support (i.e. --with-pam), 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 @@ -12190,7 +12474,11 @@ TARGET="_top" improve the efficiency of the granting of oplocks under multiple client contention for the same file.</P ><P ->In brief it specifies a number, which causes smbd not to +>In brief it specifies a number, which causes <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> not to grant an oplock even when requested if the approximate number of clients contending for an oplock on the same file goes over this limit. This causes <B @@ -12216,7 +12504,10 @@ NAME="OPLOCKS" >oplocks (S)</DT ><DD ><P ->This boolean option tells smbd whether to +>This boolean option tells <B +CLASS="COMMAND" +>smbd</B +> whether to issue oplocks (opportunistic locks) to file open requests on this share. The oplock code can dramatically (approx. 30% or more) improve the speed of access to files on Samba servers. It allows the clients @@ -12338,7 +12629,7 @@ NAME="OS2DRIVERMAP" name>.<device name></P ><P >For example, a valid entry using the HP LaserJet 5 - printer driver woudl appear as <B + printer driver would appear as <B CLASS="COMMAND" >HP LaserJet 5L = LASERJET.HP LaserJet 5L</B @@ -12372,9 +12663,20 @@ NAME="PAMPASSWORDCHANGE" ><DD ><P >With the addition of better PAM support in Samba 2.2, - this parameter, it is possible to use PAM's password change control - flag for Samba. If enabled, then PAM will be used for password - changes when requested by an SMB client, and the <A + this parameter, it is possible to use PAM's password change control + flag for Samba. If enabled, then PAM will be used for password + changes when requested by an SMB client instead of the program listed in + <A +HREF="#PASSWDPROGRAM" +><TT +CLASS="PARAMETER" +><I +>passwd program</I +></TT +></A +>. + It should be possible to enable this without changing your + <A HREF="#PASSWDCHAT" ><TT CLASS="PARAMETER" @@ -12382,9 +12684,9 @@ CLASS="PARAMETER" >passwd chat</I ></TT ></A -> must be - be changed to work with the pam prompts. - </P +> + parameter for most setups. + </P ><P >Default: <B CLASS="COMMAND" @@ -12436,7 +12738,7 @@ HREF="smbd.8.html" TARGET="_top" >smbd</A > and the local password changing - program to change the users password. The string describes a + program to change the user's password. The string describes a sequence of response-receive pairs that <A HREF="smbd.8.html" TARGET="_top" @@ -12458,19 +12760,39 @@ CLASS="PARAMETER" on what local methods are used for password control (such as NIS etc).</P ><P ->The string can contain the macros <TT +>Note that this parameter only is only used if the <A +HREF="#UNIXPASSWORDSYNC" +><TT CLASS="PARAMETER" ><I ->%o</I +>unix + password sync</I ></TT -> - and <TT +></A +> parameter is set to <TT +CLASS="CONSTANT" +>yes</TT +>. This + sequence is then called <EM +>AS ROOT</EM +> when the SMB password + in the smbpasswd file is being changed, without access to the old + password cleartext. This means that root must be able to reset the user's password + without knowing the text of the previous password. In the presence of NIS/YP, + this means that the <A +HREF="#PASSWDPROGRAM" +>passwd program</A +> must be + executed on the NIS master. + </P +><P +>The string can contain the macro <TT CLASS="PARAMETER" ><I >%n</I ></TT -> which are substituted for the old - and new passwords respectively. It can also contain the standard +> which is substituted + for the new password. The chat sequence can also contain the standard macros <TT CLASS="CONSTANT" >\n</TT @@ -12482,54 +12804,30 @@ CLASS="CONSTANT" > \t</TT > and <TT CLASS="CONSTANT" ->%s</TT +>\s</TT > to give line-feed, - carriage-return, tab and space.</P -><P ->The string can also contain a '*' which matches - any sequence of characters.</P -><P ->Double quotes can be used to collect strings with spaces + carriage-return, tab and space. The chat sequence string can also contain + a '*' which matches any sequence of characters. + Double quotes can be used to collect strings with spaces in them into a single string.</P ><P >If the send string in any part of the chat sequence - is a fullstop ".", then no string is sent. Similarly, - if the expect string is a fullstop then no string is expected.</P -><P ->Note that if the <A -HREF="#UNIXPASSWORDSYNC" -><TT -CLASS="PARAMETER" -><I ->unix - password sync</I -></TT -></A -> parameter is set to true, then this - sequence is called <EM ->AS ROOT</EM -> when the SMB password - in the smbpasswd file is being changed, without access to the old - password cleartext. In this case the old password cleartext is set - to "" (the empty string).</P + is a full stop ".", then no string is sent. Similarly, + if the expect string is a full stop then no string is expected.</P ><P ->Also, if the <A +>If the <A HREF="#PAMPASSWORDCHANGE" ><TT CLASS="PARAMETER" ><I >pam - password change</I + password change</I ></TT ></A -> parameter is set to true, then the - chat sequence should consist of three elements. The first element should - match the pam prompt for the old password, the second element should match - the pam prompt for the first request for the new password, and the final - element should match the pam prompt for the second request for the new password. - These matches are done case insentively. Under most conditions this change - is done as root so the prompt for the old password will never be matched. - </P +> parameter is set to true, the chat pairs + may be matched in any order, and sucess is determined by the PAM result, + not any particular output. The \n macro is ignored for PAM conversions. + </P ><P >See also <A HREF="#UNIXPASSWORDSYNC" @@ -12622,10 +12920,19 @@ CLASS="PARAMETER" >passwd program</I ></TT > and should - be turned off after this has been done. This parameter is off by - default.</P + be turned off after this has been done. This option has no effect if the + <A +HREF="#PAMPASSWORDCHANGE" +><TT +CLASS="PARAMETER" +><I +>pam password change</I +></TT +></A +> + paramter is set. This parameter is off by default.</P ><P ->See also <<A +>See also <A HREF="#PASSWDCHAT" ><TT CLASS="PARAMETER" @@ -12633,7 +12940,16 @@ CLASS="PARAMETER" >passwd chat</I ></TT > - </A + </A +>, <A +HREF="#PAMPASSWORDCHANGE" +><TT +CLASS="PARAMETER" +><I +>pam password change</I +></TT +> + </A >, <A HREF="#PASSWDPROGRAM" ><TT @@ -12642,7 +12958,7 @@ CLASS="PARAMETER" >passwd program</I ></TT > - </A + </A >.</P ><P >Default: <B @@ -12685,7 +13001,7 @@ CLASS="PARAMETER" ></TT > parameter is set to <TT CLASS="CONSTANT" ->True +>true </TT > then this program is called <EM >AS ROOT</EM @@ -12722,7 +13038,7 @@ CLASS="PARAMETER" ></TT > is set to <TT CLASS="CONSTANT" ->False</TT +>false</TT >.</P ><P >See also <A @@ -13094,7 +13410,7 @@ NAME="POSTEXEC" substitutions. The command may be run as the root on some systems.</P ><P ->An interesting example may be do unmount server +>An interesting example may be to unmount server resources:</P ><P ><B @@ -13132,7 +13448,7 @@ NAME="POSTSCRIPT" ><DD ><P >This parameter forces a printer to interpret - the print files as postscript. This is done by adding a <TT + the print files as PostScript. This is done by adding a <TT CLASS="CONSTANT" >%! </TT @@ -13237,7 +13553,10 @@ TARGET="_top" > is a preferred master browser for its workgroup.</P ><P ->If this is set to true, on startup, <B +>If this is set to <TT +CLASS="CONSTANT" +>true</TT +>, on startup, <B CLASS="COMMAND" >nmbd</B > @@ -13708,17 +14027,15 @@ NAME="PRINTERDRIVER" ><P ><EM >Note :</EM ->This is a depreciated +>This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in - <TT -CLASS="FILENAME" ->PRINTER_DRIVER2.txt</TT -> in the <TT -CLASS="FILENAME" ->docs - </TT -> of the Samba distribution for more information + the <A +HREF="printer_driver2.html" +TARGET="_top" +>Samba 2.2. Printing + HOWTO</A +> for more information on the new method of loading printer drivers onto a Samba server. </P ><P @@ -13768,17 +14085,15 @@ NAME="PRINTERDRIVERFILE" ><P ><EM >Note :</EM ->This is a depreciated +>This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in - <TT -CLASS="FILENAME" ->PRINTER_DRIVER2.txt</TT -> in the <TT -CLASS="FILENAME" ->docs - </TT -> of the Samba distribution for more information + the <A +HREF="printer_driver2.html" +TARGET="_top" +>Samba 2.2. Printing + HOWTO</A +> for more information on the new method of loading printer drivers onto a Samba server. </P ><P @@ -13803,7 +14118,7 @@ CLASS="FILENAME" </TT > files found on the Windows 95 client system. For more details on setting up serving of printer drivers to Windows 95 - clients, see the documentation file in the <TT + clients, see the outdated documentation file in the <TT CLASS="FILENAME" >docs/</TT > @@ -13841,17 +14156,15 @@ NAME="PRINTERDRIVERLOCATION" ><P ><EM >Note :</EM ->This is a depreciated +>This is a deprecated parameter and will be removed in the next major release following version 2.2. Please see the instructions in - <TT -CLASS="FILENAME" ->PRINTER_DRIVER2.txt</TT -> in the <TT -CLASS="FILENAME" ->docs - </TT -> of the Samba distribution for more information + the <A +HREF="printer_driver2.html" +TARGET="_top" +>Samba 2.2. Printing + HOWTO</A +> for more information on the new method of loading printer drivers onto a Samba server. </P ><P @@ -13867,7 +14180,7 @@ CLASS="COMMAND" ><P >Where MACHINE is the NetBIOS name of your Samba server, and PRINTER$ is a share you set up for serving printer driver - files. For more details on setting this up see the documentation + files. For more details on setting this up see the outdated documentation file in the <TT CLASS="FILENAME" >docs/</TT @@ -13979,7 +14292,7 @@ CLASS="PARAMETER" >lprm command</I ></TT > if specified in the - [global]f> section.</P + [global] section.</P ><P >Currently eight printing styles are supported. They are <TT @@ -14072,14 +14385,14 @@ NAME="QUEUEPAUSECOMMAND" ><DD ><P >This parameter specifies the command to be - executed on the server host in order to pause the printerqueue.</P + executed on the server host in order to pause the printer queue.</P ><P >This command should be a program or script which takes - a printer name as its only parameter and stops the printerqueue, + a printer name as its only parameter and stops the printer queue, such that no longer jobs are submitted to the printer.</P ><P >This command is not supported by Windows for Workgroups, - but can be issued from the Printer's window under Windows 95 + but can be issued from the Printers window under Windows 95 and NT.</P ><P >If a <TT @@ -14087,7 +14400,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. Otherwise it is placed at the end of the command. </P ><P @@ -14118,7 +14431,7 @@ NAME="QUEUERESUMECOMMAND" ><DD ><P >This parameter specifies the command to be - executed on the server host in order to resume the printerqueue. It + executed on the server host in order to resume the printer queue. It is the command to undo the behavior that is caused by the previous parameter (<A HREF="#QUEUEPAUSECOMMAND" @@ -14131,11 +14444,11 @@ CLASS="PARAMETER" >).</P ><P >This command should be a program or script which takes - a printer name as its only parameter and resumes the printerqueue, + a printer name as its only parameter and resumes the printer queue, such that queued jobs are resubmitted to the printer.</P ><P >This command is not supported by Windows for Workgroups, - but can be issued from the Printer's window under Windows 95 + but can be issued from the Printers window under Windows 95 and NT.</P ><P >If a <TT @@ -14143,7 +14456,7 @@ CLASS="PARAMETER" ><I >%p</I ></TT -> is given then the printername +> is given then the printer name is put in its place. Otherwise it is placed at the end of the command.</P ><P @@ -14372,7 +14685,10 @@ CLASS="COMMAND" 192.168.4.255/STAFF</B ></P ><P ->the above line would cause nmbd to announce itself +>the above line would cause <B +CLASS="COMMAND" +>nmbd</B +> to announce itself to the two given IP addresses using the given workgroup names. If you leave out the workgroup name then the one given in the <A @@ -14417,10 +14733,10 @@ HREF="nmbd.8.html" TARGET="_top" >nmbd(8)</A > to periodically request - synchronization of browse lists with the master browser of a samba + synchronization of browse lists with the master browser of a Samba server that is on a remote segment. This option will allow you to gain browse lists for multiple workgroups across routed networks. This - is done in a manner that does not work with any non-samba servers.</P + is done in a manner that does not work with any non-Samba servers.</P ><P >This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse @@ -14447,7 +14763,7 @@ CLASS="COMMAND" of known browse masters if your network config is that stable. If a machine IP address is given Samba makes NO attempt to validate that the remote machine is available, is listening, nor that it - is in fact the browse master on it's segment.</P + is in fact the browse master on its segment.</P ><P >Default: <B CLASS="COMMAND" @@ -14462,12 +14778,18 @@ NAME="RESTRICTACLWITHMASK" >restrict acl with mask (S)</DT ><DD ><P ->This is a boolean parameter. If set to false (default), then - Creation of files with access control lists (ACLS) and modification of ACLs +>This is a boolean parameter. If set to <TT +CLASS="CONSTANT" +>false</TT +> (default), then + creation of files with access control lists (ACLS) and modification of ACLs using the Windows NT/2000 ACL editor will be applied directly to the file or directory.</P ><P ->If set to True, then all requests to set an ACL on a file will have the +>If set to <TT +CLASS="CONSTANT" +>true</TT +>, then all requests to set an ACL on a file will have the parameters <A HREF="#CREATEMASK" ><TT @@ -14558,10 +14880,16 @@ NAME="RESTRICTANONYMOUS" >restrict anonymous (G)</DT ><DD ><P ->This is a boolean parameter. If it is true, then +>This is a boolean parameter. If it is <TT +CLASS="CONSTANT" +>true</TT +>, then anonymous access to the server will be restricted, namely in the case where the server is expecting the client to send a username, - but it doesn't. Setting it to true will force these anonymous + but it doesn't. Setting it to <TT +CLASS="CONSTANT" +>true</TT +> will force these anonymous connections to be denied, and the client will be required to always supply a username and password when connecting. Use of this parameter is only recommended for homogeneous NT client environments.</P @@ -14571,10 +14899,13 @@ NAME="RESTRICTANONYMOUS" likes to use anonymous connections when refreshing the share list, and this is a way to work around that.</P ><P ->When restrict anonymous is true, all anonymous connections +>When restrict anonymous is <TT +CLASS="CONSTANT" +>true</TT +>, all anonymous connections are denied no matter what they are for. This can effect the ability - of a machine to access the samba Primary Domain Controller to revalidate - it's machine account after someone else has logged on the client + of a machine to access the Samba Primary Domain Controller to revalidate + its machine account after someone else has logged on the client interactively. The NT client will display a message saying that the machine's account in the domain doesn't exist or the password is bad. The best way to deal with this is to reboot NT client machines @@ -14631,7 +14962,7 @@ NAME="ROOTDIRECTORY" CLASS="COMMAND" >chroot()</B > (i.e. - Change it's root directory) to this directory on startup. This is + Change its root directory) to this directory on startup. This is not strictly necessary for secure operation. Even without it the server will deny access to files not in one of the service entries. It may also check for, and deny access to, soft links to other @@ -14705,7 +15036,7 @@ CLASS="PARAMETER" > parameter except that the command is run as root. This is useful for unmounting filesystems - (such as cdroms) after a connection is closed.</P + (such as CDROMs) after a connection is closed.</P ><P >See also <A HREF="#POSTEXEC" @@ -14737,8 +15068,8 @@ CLASS="PARAMETER" ></TT > parameter except that the command is run as root. This - is useful for mounting filesystems (such as cdroms) after a - connection is closed.</P + is useful for mounting filesystems (such as CDROMs) when a + connection is opened.</P ><P >See also <A HREF="#PREEXEC" @@ -14918,7 +15249,7 @@ NAME="SECURITYEQUALSSHARE" </EM ></P ><P ->When clients connect to a share level security server then +>When clients connect to a share level security server they need not log onto the server with a valid username and password before attempting to connect to a shared resource (although modern clients such as Windows 95/98 and Windows NT will send a logon request with @@ -15066,7 +15397,7 @@ HREF="#AEN235" NAME="SECURITYEQUALSUSER" ></A ><EM ->SECURIYT = USER +>SECURITY = USER </EM ></P ><P @@ -15175,7 +15506,7 @@ CLASS="FILENAME" ><P ><EM >Note</EM -> that from the clients point of +> that from the client's point of view <B CLASS="COMMAND" >security = server</B @@ -15277,7 +15608,7 @@ CLASS="CONSTANT" ><P ><EM >Note</EM -> that from the clients point +> that from the client's point of view <B CLASS="COMMAND" >security = domain</B @@ -15392,7 +15723,10 @@ NAME="SECURITYMASK" Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will - probably want to leave it set to 0777.</P + probably want to leave it set to <TT +CLASS="CONSTANT" +>0777</TT +>.</P ><P >See also the <A HREF="#FORCEDIRECTORYSECURITYMODE" @@ -15505,64 +15839,6 @@ CLASS="COMMAND" ></DD ><DT ><A -NAME="SHAREMODES" -></A ->share modes (S)</DT -><DD -><P ->This enables or disables the honoring of - the <TT -CLASS="PARAMETER" -><I ->share modes</I -></TT -> during a file open. These - modes are used by clients to gain exclusive read or write access - to a file.</P -><P ->These open modes are not directly supported by UNIX, so - they are simulated using shared memory, or lock files if your - UNIX doesn't support shared memory (almost all do).</P -><P ->The share modes that are enabled by this option are - <TT -CLASS="CONSTANT" ->DENY_DOS</TT ->, <TT -CLASS="CONSTANT" ->DENY_ALL</TT ->, - <TT -CLASS="CONSTANT" ->DENY_READ</TT ->, <TT -CLASS="CONSTANT" ->DENY_WRITE</TT ->, - <TT -CLASS="CONSTANT" ->DENY_NONE</TT -> and <TT -CLASS="CONSTANT" ->DENY_FCB</TT ->. - </P -><P ->This option gives full share compatibility and enabled - by default.</P -><P ->You should <EM ->NEVER</EM -> turn this parameter - off as many Windows applications will break if you do so.</P -><P ->Default: <B -CLASS="COMMAND" ->share modes = yes</B -></P -></DD -><DT -><A NAME="SHORTPRESERVECASE" ></A >short preserve case (S)</DT @@ -15624,7 +15900,7 @@ CLASS="PARAMETER" >printer admin</I ></TT > group), the OpenPrinterEx() - call fails and the clients another open call with a request for + call fails and the client makes another open call with a request for a lower privilege level. This should succeed, however the APW icon will not be displayed.</P ><P @@ -15674,6 +15950,115 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="SHUTDOWNSCRIPT" +></A +>shutdown script (G)</DT +><DD +><P +><EM +>This parameter only exists in the HEAD cvs branch</EM +> + This a full path name to a script called by + <A +HREF="smbd.8.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbd(8)</B +></A +> that + should start a shutdown procedure.</P +><P +>This command will be run as the user connected to the + server.</P +><P +>%m %t %r %f parameters are expanded</P +><P +><TT +CLASS="PARAMETER" +><I +>%m</I +></TT +> will be substituted with the + shutdown message sent to the server.</P +><P +><TT +CLASS="PARAMETER" +><I +>%t</I +></TT +> will be substituted with the + number of seconds to wait before effectively starting the + shutdown procedure.</P +><P +><TT +CLASS="PARAMETER" +><I +>%r</I +></TT +> will be substituted with the + switch <EM +>-r</EM +>. It means reboot after shutdown + for NT. + </P +><P +><TT +CLASS="PARAMETER" +><I +>%f</I +></TT +> will be substituted with the + switch <EM +>-f</EM +>. It means force the shutdown + even if applications do not respond for NT.</P +><P +>Default: <EM +>None</EM +>.</P +><P +>Example: <B +CLASS="COMMAND" +>abort shutdown script = /usr/local/samba/sbin/shutdown %m %t %r %f</B +></P +><P +>Shutdown script example: + <TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="PROGRAMLISTING" +> #!/bin/bash + + $time=0 + let "time/60" + let "time++" + + /sbin/shutdown $3 $4 +$time $1 & + </PRE +></TD +></TR +></TABLE +> + Shutdown does not return so we need to launch it in background. + </P +><P +>See also <A +HREF="#ABORTSHUTDOWNSCRIPT" +><TT +CLASS="PARAMETER" +><I +>abort shutdown script</I +></TT +></A +>.</P +></DD +><DT +><A NAME="SMBPASSWDFILE" ></A >smb passwd file (G)</DT @@ -15707,7 +16092,7 @@ NAME="SOCKETADDRESS" support multiple virtual interfaces on the one server, each with a different configuration.</P ><P ->By default samba will accept connections on any +>By default Samba will accept connections on any address.</P ><P >Example: <B @@ -15917,8 +16302,8 @@ CLASS="COMMAND" it is set to <TT CLASS="CONSTANT" >no</TT ->, the SSL enabled samba behaves - exactly like the non-SSL samba. If set to <TT +>, the SSL-enabled Samba behaves + exactly like the non-SSL Samba. If set to <TT CLASS="CONSTANT" >yes</TT >, @@ -15971,7 +16356,7 @@ CLASS="COMMAND" ><P >This variable defines where to look up the Certification Authorities. The given directory should contain one file for - each CA that samba will trust. The file name must be the hash + each CA that Samba will trust. The file name must be the hash value over the "Distinguished Name" of the CA. How this directory is set up is explained later in this document. All files within the directory that don't fit into this naming scheme are ignored. You @@ -16199,8 +16584,8 @@ CLASS="COMMAND" > enabled by default in any current binary version of Samba.</P ><P ->These two variables define whether samba will go - into SSL mode or not. If none of them is defined, samba will +>These two variables define whether Samba will go + into SSL mode or not. If none of them is defined, Samba will allow only SSL connections. If the <A HREF="#SSLHOSTS" > <TT @@ -16217,7 +16602,9 @@ CLASS="PARAMETER" > ssl hosts resign</I ></TT > variable lists hosts, only these - hosts will NOT be forced into SSL mode. The syntax for these two + hosts will <EM +>NOT</EM +> be forced into SSL mode. The syntax for these two variables is the same as for the <A HREF="#HOSTSALLOW" ><TT @@ -16587,7 +16974,7 @@ CLASS="CONSTANT" > the server does file lock checks only when the client explicitly asks for them.</P ><P ->Well behaved clients always ask for lock checks when it +>Well-behaved clients always ask for lock checks when it is important, so in the vast majority of cases <B CLASS="COMMAND" >strict @@ -16616,7 +17003,11 @@ NAME="STRICTSYNC" CLASS="CONSTANT" >no</TT > (the - default) means that smbd ignores the Windows applications requests for + default) means that <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> ignores the Windows applications requests for a sync call. There is only a possibility of losing data if the operating system itself that Samba is running on crashes, so there is little danger in this default setting. In addition, this fixes many @@ -16664,10 +17055,16 @@ NAME="SYNCALWAYS" ><P >This is a boolean parameter that controls whether writes will always be written to stable storage before - the write call returns. If this is false then the server will be + the write call returns. If this is <TT +CLASS="CONSTANT" +>false</TT +> then the server will be guided by the client's request in each write call (clients can set a bit indicating that a particular write should be synchronous). - If this is true then every write will be followed by a <B + If this is <TT +CLASS="CONSTANT" +>true</TT +> then every write will be followed by a <B CLASS="COMMAND" >fsync() </B @@ -16758,11 +17155,6 @@ NAME="TEMPLATEHOMEDIR" >template homedir (G)</DT ><DD ><P -><EM ->NOTE:</EM -> this parameter is - only available in Samba 3.0.</P -><P >When filling out the user information for a Windows NT user, the <A HREF="winbindd.8.html" @@ -16797,11 +17189,6 @@ NAME="TEMPLATESHELL" >template shell (G)</DT ><DD ><P -><EM ->NOTE:</EM -> this parameter is - only available in Samba 3.0.</P -><P >When filling out the user information for a Windows NT user, the <A HREF="winbindd.8.html" @@ -16884,7 +17271,11 @@ NAME="TOTALPRINTJOBS" >This parameter accepts an integer value which defines a limit on the maximum number of print jobs that will be accepted system wide at any given time. If a print job is submitted - by a client which will exceed this number, then smbd will return an + by a client which will exceed this number, then <A +HREF="smbd.8.html" +TARGET="_top" +>smbd</A +> will return an error indicating that no space is available on the server. The default value of 0 means that no such limit exists. This parameter can be used to prevent a server from exceeding its capacity and is @@ -16920,7 +17311,10 @@ NAME="UNIXPASSWORDSYNC" >This boolean parameter controls whether Samba attempts to synchronize the UNIX password with the SMB password when the encrypted SMB password in the smbpasswd file is changed. - If this is set to true the program specified in the <TT + If this is set to <TT +CLASS="CONSTANT" +>true</TT +> the program specified in the <TT CLASS="PARAMETER" ><I >passwd @@ -16930,7 +17324,7 @@ CLASS="PARAMETER" >AS ROOT</EM > - to allow the new UNIX password to be set without access to the - old UNIX password (as the SMB password has change code has no + old UNIX password (as the SMB password change code has no access to the old password cleartext, only the new).</P ><P >See also <A @@ -17014,13 +17408,66 @@ CLASS="COMMAND" ></DD ><DT ><A +NAME="USECLIENTDRIVER" +></A +>use client driver (S)</DT +><DD +><P +>This parameter applies only to Windows NT/2000 + clients. It has no affect on Windows 95/98/ME clients. When + serving a printer to Windows NT/2000 clients without first installing + a valid printer driver on the Samba host, the client will be required + to install a local printer driver. From this point on, the client + will treat the print as a local printer and not a network printer + connection. This is much the same behavior that will occur + when <B +CLASS="COMMAND" +>disable spoolss = yes</B +>. </P +><P +>The differentiating + factor is that under normal circumstances, the NT/2000 client will + attempt to open the network printer using MS-RPC. The problem is that + because the client considers the printer to be local, it will attempt + to issue the OpenPrinterEx() call requesting access rights associated + with the logged on user. If the user possesses local administator rights + but not root privilegde on the Samba host (often the case), the OpenPrinterEx() + call will fail. The result is that the client will now display an "Access + Denied; Unable to connect" message in the printer queue window (even though + jobs may successfully be printed). </P +><P +>If this parameter is enabled for a printer, then any attempt + to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped + to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx() + call to succeed. <EM +>This parameter MUST not be able enabled + on a print share which has valid print driver installed on the Samba + server.</EM +></P +><P +>See also <A +HREF="#DISABLESPOOLSS" +>disable spoolss</A +> + </P +><P +>Default: <B +CLASS="COMMAND" +>use client driver = no</B +></P +></DD +><DT +><A NAME="USERHOSTS" ></A >use rhosts (G)</DT ><DD ><P ->If this global parameter is a true, it specifies - that the UNIX users <TT +>If this global parameter is <TT +CLASS="CONSTANT" +>true</TT +>, it specifies + that the UNIX user's <TT CLASS="FILENAME" >.rhosts</TT > file in their home directory @@ -17145,7 +17592,7 @@ CLASS="PARAMETER" > parameter.</P ><P >If any of the usernames begin with a '@' then the name - will be looked up first in the yp netgroups list (if Samba + will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name.</P @@ -17155,7 +17602,7 @@ CLASS="PARAMETER" expand to a list of all users in the group of that name.</P ><P >If any of the usernames begin with a '&'then the name - will be looked up only in the yp netgroups database (if Samba + will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name.</P ><P @@ -17374,14 +17821,17 @@ CLASS="COMMAND" ><A NAME="UTMP" ></A ->utmp (S)</DT +>utmp (G)</DT ><DD ><P >This boolean parameter is only available if Samba has been configured and compiled with the option <B CLASS="COMMAND" > --with-utmp</B ->. If set to True then Samba will attempt +>. If set to <TT +CLASS="CONSTANT" +>true</TT +> then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server. Sites may use this to record the user connecting to a Samba share.</P @@ -17664,15 +18114,12 @@ CLASS="PARAMETER" ><I >yes</I ></TT ->. - - <P +>.</P +><P >Setting this parameter will affect the performance of Samba, as it will be forced to check all files and directories for a match as they are scanned.</P -> - - <P +><P >See also <A HREF="#HIDEFILES" ><TT @@ -17691,16 +18138,12 @@ CLASS="PARAMETER" ></TT ></A >.</P -> - - <P +><P >Default: <EM >No files or directories are vetoed. </EM ></P -> - - <P +><P >Examples:<TABLE BORDER="0" BGCOLOR="#E0E0E0" @@ -17722,8 +18165,6 @@ CLASS="PROGRAMLISTING" ></TR ></TABLE ></P -> - </P ></DD ><DT ><A @@ -17802,7 +18243,7 @@ NAME="VFSOPTIONS" ><DD ><P >This parameter allows parameters to be passed - to the vfs layer at initialisation time. The Samba VFS layer + to the vfs layer at initialization time. The Samba VFS layer is new to Samba 2.2 and must be enabled at compile time with --with-vfs. See also <A HREF="#VFSOBJECT" @@ -17862,11 +18303,6 @@ NAME="WINBINDCACHETIME" >winbind cache time</DT ><DD ><P -><EM ->NOTE:</EM -> this parameter is only - available in Samba 3.0.</P -><P >This parameter specifies the number of seconds the <A HREF="winbindd.8.html" @@ -17883,15 +18319,113 @@ CLASS="COMMAND" ></DD ><DT ><A -NAME="WINBINDGID" +NAME="WINBINDENUMUSERS" ></A ->winbind gid</DT +>winbind enum + users</DT ><DD ><P +>On large installations using + <A +HREF="winbindd.8.html" +TARGET="_top" +>winbindd(8)</A +> it may be + necessary to suppress the enumeration of users through the + <B +CLASS="COMMAND" +> setpwent()</B +>, + <B +CLASS="COMMAND" +>getpwent()</B +> and + <B +CLASS="COMMAND" +>endpwent()</B +> group of system calls. If + the <TT +CLASS="PARAMETER" +><I +>winbind enum users</I +></TT +> parameter is + false, calls to the <B +CLASS="COMMAND" +>getpwent</B +> system call + will not return any data. </P +><P ><EM ->NOTE:</EM -> this parameter is only - available in Samba 3.0.</P +>Warning:</EM +> Turning off user + enumeration may cause some programs to behave oddly. For + example, the finger program relies on having access to the + full user list when searching for matching + usernames. </P +><P +>Default: <B +CLASS="COMMAND" +>winbind enum users = yes </B +></P +></DD +><DT +><A +NAME="WINBINDENUMGROUPS" +></A +>winbind enum + groups</DT +><DD +><P +>On large installations using + <A +HREF="winbindd.8.html" +TARGET="_top" +>winbindd(8)</A +> it may be + necessary to suppress the enumeration of groups through the + <B +CLASS="COMMAND" +> setgrent()</B +>, + <B +CLASS="COMMAND" +>getgrent()</B +> and + <B +CLASS="COMMAND" +>endgrent()</B +> group of system calls. If + the <TT +CLASS="PARAMETER" +><I +>winbind enum groups</I +></TT +> parameter is + false, calls to the <B +CLASS="COMMAND" +>getgrent()</B +> system + call will not return any data. </P +><P +><EM +>Warning:</EM +> Turning off group + enumeration may cause some programs to behave oddly. + </P +><P +>Default: <B +CLASS="COMMAND" +>winbind enum groups = no </B +> + </P +></DD +><DT +><A +NAME="WINBINDGID" +></A +>winbind gid</DT +><DD ><P >The winbind gid parameter specifies the range of group ids that are allocated by the <A @@ -17899,7 +18433,7 @@ HREF="winbindd.8.html" TARGET="_top" > winbindd(8)</A > daemon. This range of group ids should have no - existing local or nis groups within it as strange conflicts can + existing local or NIS groups within it as strange conflicts can occur otherwise.</P ><P >Default: <B @@ -17920,11 +18454,6 @@ NAME="WINBINDSEPARATOR" >winbind separator</DT ><DD ><P -><EM ->NOTE:</EM -> this parameter is only - available in Samba 3.0.</P -><P >This parameter allows an admin to define the character used when listing a username of the form of <TT CLASS="REPLACEABLE" @@ -17965,18 +18494,13 @@ NAME="WINBINDUID" >winbind uid</DT ><DD ><P -><EM ->NOTE:</EM -> this parameter is only - available in Samba 3.0.</P -><P >The winbind gid parameter specifies the range of group ids that are allocated by the <A HREF="winbindd.8.html" TARGET="_top" > winbindd(8)</A > daemon. This range of ids should have no - existing local or nis users within it as strange conflicts can + existing local or NIS users within it as strange conflicts can occur otherwise.</P ><P >Default: <B @@ -18025,14 +18549,14 @@ CLASS="COMMAND" ></LI ><LI ><P ->The second argument is the netbios name. If the +>The second argument is the NetBIOS name. If the name is not a legal name then the wins hook is not called. Legal names contain only letters, digits, hyphens, underscores and periods.</P ></LI ><LI ><P ->The third argument is the netbios name +>The third argument is the NetBIOS name type as a 2 digit hexadecimal number. </P ></LI ><LI @@ -18130,14 +18654,20 @@ TARGET="_top" > nmbd(8)</A > process in Samba will act as a WINS server. You should - not set this to true unless you have a multi-subnetted network and + not set this to <TT +CLASS="CONSTANT" +>true</TT +> unless you have a multi-subnetted network and you wish a particular <B CLASS="COMMAND" >nmbd</B > to be your WINS server. Note that you should <EM >NEVER</EM -> set this to true +> set this to <TT +CLASS="CONSTANT" +>true</TT +> on more than one machine in your network.</P ><P >Default: <B @@ -18209,7 +18739,7 @@ NAME="WRITECACHESIZE" within it.</P ><P >This cache allows Samba to batch client writes into a more - efficient write size for RAID disks (ie. writes may be tuned to + efficient write size for RAID disks (i.e. writes may be tuned to be the RAID stripe size) and can improve performance on systems where the disk subsystem is a bottleneck but there is free memory for userspace programs.</P @@ -18301,7 +18831,7 @@ NAME="WRITERAW" ><DD ><P >This parameter controls whether or not the server - will support raw writes SMB's when transferring data from clients. + will support raw write SMB's when transferring data from clients. You should never need to change this parameter.</P ><P >Default: <B @@ -18353,7 +18883,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5794" +NAME="AEN5953" ></A ><H2 >WARNINGS</H2 @@ -18383,7 +18913,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5800" +NAME="AEN5959" ></A ><H2 >VERSION</H2 @@ -18394,7 +18924,7 @@ NAME="AEN5800" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5803" +NAME="AEN5962" ></A ><H2 >SEE ALSO</H2 @@ -18473,7 +19003,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN5823" +NAME="AEN5982" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbcacls.1.html b/docs/htmldocs/smbcacls.1.html index b8323dd8f5..637720fa6b 100644 --- a/docs/htmldocs/smbcacls.1.html +++ b/docs/htmldocs/smbcacls.1.html @@ -52,18 +52,24 @@ TARGET="_top" > Samba</A > suite.</P ><P ->The smbcacls program manipulates NT Access Control Lists +>The <B +CLASS="COMMAND" +>smbcacls</B +> program manipulates NT Access Control Lists (ACLs) on SMB file shares. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN27" +NAME="AEN28" ></A ><H2 >OPTIONS</H2 ><P ->The following options are available to the smbcacls program. +>The following options are available to the <B +CLASS="COMMAND" +>smbcacls</B +> program. The format of ACLs is described in the section ACL FORMAT </P ><P ></P @@ -90,7 +96,7 @@ CLASS="VARIABLELIST" >-D acls</DT ><DD ><P ->Delete any ACLs specfied on the command line. +>Delete any ACLs specified on the command line. An error will be printed for each ACL specified that was not already present in the ACL list. </P ></DD @@ -175,7 +181,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN73" +NAME="AEN75" ></A ><H2 >ACL FORMAT</H2 @@ -322,7 +328,7 @@ ACL:<sid or name>:<type>/<flags>/<mask> ><DIV CLASS="REFSECT1" ><A -NAME="AEN123" +NAME="AEN125" ></A ><H2 >EXIT STATUS</H2 @@ -334,8 +340,11 @@ CLASS="COMMAND" depending on the success or otherwise of the operations performed. The exit status may be one of the following values. </P ><P ->If the operation succeded, smbcacls returns and exit - status of 0. If smbcacls couldn't connect to the specified server, +>If the operation succeeded, smbcacls returns and exit + status of 0. If <B +CLASS="COMMAND" +>smbcacls</B +> couldn't connect to the specified server, or there was an error getting or setting the ACLs, an exit status of 1 is returned. If there was an error parsing any command line arguments, an exit status of 2 is returned. </P @@ -343,7 +352,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN128" +NAME="AEN131" ></A ><H2 >VERSION</H2 @@ -354,7 +363,7 @@ NAME="AEN128" ><DIV CLASS="REFSECT1" ><A -NAME="AEN131" +NAME="AEN134" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbclient.1.html b/docs/htmldocs/smbclient.1.html index 8232906680..16fc134405 100644 --- a/docs/htmldocs/smbclient.1.html +++ b/docs/htmldocs/smbclient.1.html @@ -37,12 +37,12 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbclient</B -> {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-S server] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-I destinationIP] [-E <terminal code>] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan]</P +> {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-I destinationIP] [-E <terminal code>] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN34" +NAME="AEN33" ></A ><H2 >DESCRIPTION</H2 @@ -70,7 +70,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN41" +NAME="AEN40" ></A ><H2 >OPTIONS</H2 @@ -121,8 +121,14 @@ CLASS="PARAMETER" ><I >-R</I ></TT -> parameter to smbclient or - using the name resolve order parameter in the smb.conf file, +> parameter to <B +CLASS="COMMAND" +>smbclient</B +> or + using the name resolve order parameter in the <TT +CLASS="FILENAME" +>smb.conf</TT +> file, allowing an administrator to change the order and methods by which server names are looked up. </P ></DD @@ -194,7 +200,7 @@ CLASS="FILENAME" ><P >This option is used by the programs in the Samba suite to determine what naming services and in what order to resolve - host names to IP addresses. The option takes a space separated + host names to IP addresses. The option takes a space-separated string of different name resolution options.</P ><P >The options are :"lmhosts", "host", "wins" and "bcast". They @@ -227,7 +233,7 @@ CLASS="FILENAME" >/etc/hosts </TT >, NIS, or DNS lookups. This method of name resolution - is operating system depended for instance on IRIX or Solaris this + is operating system dependent, for instance on IRIX or Solaris this may be controlled by the <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -284,7 +290,10 @@ CLASS="PARAMETER" >name resolve order </I ></TT -> parameter of the smb.conf file the name resolution +> parameter of the <TT +CLASS="FILENAME" +>smb.conf</TT +> file the name resolution methods will be attempted in this order. </P ></DD ><DT @@ -351,7 +360,14 @@ CLASS="FILENAME" ><P >This specifies a NetBIOS scope that smbclient will use to communicate with when generating NetBIOS names. For details - on the use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. + on the use of NetBIOS scopes, see <TT +CLASS="FILENAME" +>rfc1001.txt</TT +> + and <TT +CLASS="FILENAME" +>rfc1002.txt</TT +>. NetBIOS scopes are <EM >very</EM > rarely used, only set @@ -383,7 +399,12 @@ CLASS="FILENAME" >-d debuglevel</DT ><DD ><P ->debuglevel is an integer from 0 to 10, or +><TT +CLASS="REPLACEABLE" +><I +>debuglevel</I +></TT +> is an integer from 0 to 10, or the letter 'A'. </P ><P >The default value if this parameter is not specified @@ -400,7 +421,12 @@ CLASS="FILENAME" data, and should only be used when investigating a problem. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely - cryptic. If debuglevel is set to the letter 'A', then <EM + cryptic. If <TT +CLASS="REPLACEABLE" +><I +>debuglevel</I +></TT +> is set to the letter 'A', then <EM >all </EM > debug messages will be printed. This setting @@ -410,9 +436,9 @@ CLASS="FILENAME" to know how the code works internally). </P ><P >Note that specifying this parameter here will override - the log level parameter in the <B -CLASS="COMMAND" ->smb.conf (5)</B + the log level parameter in the <TT +CLASS="FILENAME" +>smb.conf (5)</TT > file. </P ></DD @@ -429,7 +455,12 @@ CLASS="COMMAND" >-l logfilename</DT ><DD ><P ->If specified, logfilename specifies a base filename +>If specified, <TT +CLASS="REPLACEABLE" +><I +>logfilename</I +></TT +> specifies a base filename into which operational data from the running client will be logged. </P ><P @@ -455,7 +486,12 @@ CLASS="FILENAME" >-I IP-address</DT ><DD ><P ->IP address is the address of the server to connect to. +><TT +CLASS="REPLACEABLE" +><I +>IP address</I +></TT +> is the address of the server to connect to. It should be specified in standard "a.b.c.d" notation. </P ><P >Normally the client would attempt to locate a named @@ -492,35 +528,37 @@ CLASS="PARAMETER" ><P >Sets the SMB username or username and password. If %pass is not specified, The user will be prompted. The client - will first check the USER environment variable, then the + will first check the <TT +CLASS="ENVAR" +>USER</TT +> environment variable, then the <TT -CLASS="PARAMETER" -><I ->$LOGNAME</I -></TT -> variable and if either exist, the +CLASS="ENVAR" +>LOGNAME</TT +> variable and if either exists, the string is uppercased. Anything in these variables following a '%' - sign will be treated as the password. If these environmental + sign will be treated as the password. If these environment variables are not found, the username <TT CLASS="CONSTANT" >GUEST</TT > is used. </P ><P ->If the password is not included in these environment - variables (using the %pass syntax), rpcclient will look for +>If the password is not included in these environment + variables (using the %pass syntax), <B +CLASS="COMMAND" +>smbclient</B +> will look for a <TT -CLASS="PARAMETER" -><I ->$PASSWD</I -></TT +CLASS="ENVAR" +>PASSWD</TT > environment variable from which to read the password. </P ><P >A third option is to use a credentials file which contains the plaintext of the username and password. This option is mainly provided for scripts where the admin doesn't - desire to pass the credentials on the command line or via environment + wish to pass the credentials on the command line or via environment variables. If this method is used, make certain that the permissions on the file restrict access from unwanted users. See the <TT @@ -532,10 +570,8 @@ CLASS="PARAMETER" ><P >Be cautious about including passwords in scripts or in the <TT -CLASS="PARAMETER" -><I ->$PASSWD</I -></TT +CLASS="ENVAR" +>PASSWD</TT > environment variable. Also, on many systems the command line of a running process may be seen via the <B @@ -544,7 +580,7 @@ CLASS="COMMAND" > command to be safe always allow <B CLASS="COMMAND" ->rpcclient</B +>smbclient</B > to prompt for a password and type it in directly. </P ></DD @@ -592,14 +628,17 @@ CLASS="PARAMETER" </I ></TT > option may be useful if your NetBIOS names don't - match your tcp/ip dns host names or if you are trying to reach a + match your TCP/IP DNS host names or if you are trying to reach a host on another network. </P ></DD ><DT >-t terminal code</DT ><DD ><P ->This option tells smbclient how to interpret +>This option tells <B +CLASS="COMMAND" +>smbclient</B +> how to interpret filenames coming from the remote server. Usually Asian language multibyte UNIX implementations use different character sets than SMB/CIFS servers (<EM @@ -771,7 +810,7 @@ CLASS="PARAMETER" >r</I ></TT > - Regular expression include - or exclude. Uses regular regular expression matching for + or exclude. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H. However this mode can be very slow. If not compiled with HAVE_REGEX_H, does a limited wildcard match on '*' and '?'. @@ -829,7 +868,10 @@ CLASS="COMMAND" >'s tar option now supports long file names both on backup and restore. However, the full path name of the file must be less than 1024 bytes. Also, when - a tar archive is created, smbclient's tar option places all + a tar archive is created, <B +CLASS="COMMAND" +>smbclient</B +>'s tar option places all files in the archive with relative names, not absolute names. </P ><P @@ -845,12 +887,15 @@ CLASS="COMMAND" >Examples</EM ></P ><P ->Restore from tar file backup.tar into myshare on mypc +>Restore from tar file <TT +CLASS="FILENAME" +>backup.tar</TT +> into myshare on mypc (no password on share). </P ><P ><B CLASS="COMMAND" ->smbclient //mypc/myshare "" -N -Tx backup.tar +>smbclient //mypc/yshare "" -N -Tx backup.tar </B ></P ><P @@ -906,7 +951,7 @@ CLASS="COMMAND" >-c command string</DT ><DD ><P ->command string is a semicolon separated list of +>command string is a semicolon-separated list of commands to be executed instead of prompting from stdin. <TT CLASS="PARAMETER" ><I @@ -931,7 +976,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN297" +NAME="AEN310" ></A ><H2 >OPERATIONS</H2 @@ -979,7 +1024,12 @@ CLASS="VARIABLELIST" >? [command]</DT ><DD ><P ->If "command" is specified, the ? command will display +>If <TT +CLASS="REPLACEABLE" +><I +>command</I +></TT +> is specified, the ? command will display a brief informative message about the specified command. If no command is specified, a list of available commands will be displayed. </P @@ -988,7 +1038,12 @@ CLASS="VARIABLELIST" >! [shell command]</DT ><DD ><P ->If "shell command" is specified, the ! +>If <TT +CLASS="REPLACEABLE" +><I +>shell command</I +></TT +> is specified, the ! command will execute a shell locally and run the specified shell command. If no command is specified, a local shell will be run. </P @@ -1010,14 +1065,24 @@ CLASS="VARIABLELIST" ><DD ><P >The client will request that the server attempt - to delete all files matching "mask" from the current working + to delete all files matching <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> from the current working directory on the server. </P ></DD ><DT >dir <mask></DT ><DD ><P ->A list of the files matching "mask" in the current +>A list of the files matching <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> in the current working directory on the server will be retrieved from the server and displayed. </P ></DD @@ -1032,9 +1097,15 @@ CLASS="VARIABLELIST" >get <remote file name> [local file name]</DT ><DD ><P ->Copy the file called "remote file name" from +>Copy the file called <TT +CLASS="FILENAME" +>remote file name</TT +> from the server to the machine running the client. If specified, name - the local copy "local file name". Note that all transfers in + the local copy <TT +CLASS="FILENAME" +>local file name</TT +>. Note that all transfers in <B CLASS="COMMAND" >smbclient</B @@ -1051,7 +1122,12 @@ CLASS="COMMAND" >lcd [directory name]</DT ><DD ><P ->If "directory name" is specified, the current +>If <TT +CLASS="REPLACEABLE" +><I +>directory name</I +></TT +> is specified, the current working directory on the local machine will be changed to the directory specified. This operation will fail if for any reason the specified directory is inaccessible. </P @@ -1114,13 +1190,26 @@ CLASS="COMMAND" >mget <mask></DT ><DD ><P ->Copy all files matching mask from the server to +>Copy all files matching <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> from the server to the machine running the client. </P ><P ->Note that mask is interpreted differently during recursive +>Note that <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information. Note that all transfers in - smbclient are binary. See also the lowercase command. </P + <B +CLASS="COMMAND" +>smbclient</B +> are binary. See also the lowercase command. </P ></DD ><DT >mkdir <directory name></DT @@ -1133,13 +1222,26 @@ CLASS="COMMAND" >mput <mask></DT ><DD ><P ->Copy all files matching mask in the current working +>Copy all files matching <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> in the current working directory on the local machine to the current working directory on the server. </P ><P ->Note that mask is interpreted differently during recursive +>Note that <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask - commands for more information. Note that all transfers in smbclient + commands for more information. Note that all transfers in <B +CLASS="COMMAND" +>smbclient</B +> are binary. </P ></DD ><DT @@ -1175,10 +1277,19 @@ CLASS="COMMAND" >put <local file name> [remote file name]</DT ><DD ><P ->Copy the file called "local file name" from the +>Copy the file called <TT +CLASS="FILENAME" +>local file name</TT +> from the machine running the client to the server. If specified, - name the remote copy "remote file name". Note that all transfers - in smbclient are binary. See also the lowercase command. + name the remote copy <TT +CLASS="FILENAME" +>remote file name</TT +>. Note that all transfers + in <B +CLASS="COMMAND" +>smbclient</B +> are binary. See also the lowercase command. </P ></DD ><DT @@ -1223,7 +1334,12 @@ CLASS="COMMAND" >rm <mask></DT ><DD ><P ->Remove all files matching mask from the current +>Remove all files matching <TT +CLASS="REPLACEABLE" +><I +>mask</I +></TT +> from the current working directory on the server. </P ></DD ><DT @@ -1255,7 +1371,12 @@ CLASS="PARAMETER" ><P >Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in - blocksize*TBLOCK (usually 512 byte) blocks. </P + <TT +CLASS="REPLACEABLE" +><I +>blocksize</I +></TT +>*TBLOCK (usually 512 byte) blocks. </P ></DD ><DT >tarmode <full|inc|reset|noreset></DT @@ -1288,7 +1409,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN446" +NAME="AEN477" ></A ><H2 >NOTES</H2 @@ -1309,35 +1430,40 @@ NAME="AEN446" ><DIV CLASS="REFSECT1" ><A -NAME="AEN451" +NAME="AEN482" ></A ><H2 >ENVIRONMENT VARIABLES</H2 ><P >The variable <TT -CLASS="PARAMETER" -><I ->$USER</I -></TT +CLASS="ENVAR" +>USER</TT > may contain the username of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords.</P ><P >The variable <TT -CLASS="PARAMETER" -><I ->$PASSWD</I -></TT +CLASS="ENVAR" +>PASSWD</TT > may contain the password of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords. </P +><P +>The variable <TT +CLASS="ENVAR" +>LIBSMB_PROG</TT +> may contain + the path, executed with system(), which the client should connect + to instead of connecting to a server. This functionality is primarily + intended as a development aid, and works best when using a LMHOSTS + file</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN457" +NAME="AEN490" ></A ><H2 >INSTALLATION</H2 @@ -1368,14 +1494,14 @@ CLASS="FILENAME" CLASS="COMMAND" >smbd(8) </B -> an ordinary user - running that server as a daemon +> as an ordinary user - running that server as a daemon on a user-accessible port (typically any port number over 1024) would provide a suitable test server. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN467" +NAME="AEN500" ></A ><H2 >DIAGNOSTICS</H2 @@ -1391,7 +1517,7 @@ NAME="AEN467" ><DIV CLASS="REFSECT1" ><A -NAME="AEN471" +NAME="AEN504" ></A ><H2 >VERSION</H2 @@ -1402,7 +1528,7 @@ NAME="AEN471" ><DIV CLASS="REFSECT1" ><A -NAME="AEN474" +NAME="AEN507" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbcontrol.1.html b/docs/htmldocs/smbcontrol.1.html index 7136d3e981..1f3b020c87 100644 --- a/docs/htmldocs/smbcontrol.1.html +++ b/docs/htmldocs/smbcontrol.1.html @@ -231,6 +231,14 @@ CLASS="CONSTANT" CLASS="CONSTANT" >smbd</TT >.</P +><P +>The <TT +CLASS="CONSTANT" +>close-share</TT +> message-type sends a + message to smbd which forces smbd to close the share that was + specified as an argument. This may be useful if you made changes + to the access controls on the share. </P ></DD ><DT >parameters</DT @@ -244,7 +252,7 @@ CLASS="CONSTANT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN76" +NAME="AEN78" ></A ><H2 >VERSION</H2 @@ -255,7 +263,7 @@ NAME="AEN76" ><DIV CLASS="REFSECT1" ><A -NAME="AEN79" +NAME="AEN81" ></A ><H2 >SEE ALSO</H2 @@ -281,7 +289,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN86" +NAME="AEN88" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html index 35520b05af..be82ef6d4e 100644 --- a/docs/htmldocs/smbd.8.html +++ b/docs/htmldocs/smbd.8.html @@ -98,12 +98,15 @@ CLASS="FILENAME" can force a reload by sending a SIGHUP to the server. Reloading the configuration file will not affect connections to any service that is already established. Either the user will have to - disconnect from the service, or smbd killed and restarted.</P + disconnect from the service, or <B +CLASS="COMMAND" +>smbd</B +> killed and restarted.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN35" +NAME="AEN36" ></A ><H2 >OPTIONS</H2 @@ -120,9 +123,12 @@ CLASS="VARIABLELIST" the server to operate as a daemon. That is, it detaches itself and runs in the background, fielding requests on the appropriate port. Operating the server as a - daemon is the recommended way of running smbd for + daemon is the recommended way of running <B +CLASS="COMMAND" +>smbd</B +> for servers that provide more than casual use file and - print services. This switch is assumed is <B + print services. This switch is assumed if <B CLASS="COMMAND" >smbd </B @@ -153,7 +159,10 @@ CLASS="COMMAND" >-P</DT ><DD ><P ->Passive option. Causes smbd not to +>Passive option. Causes <B +CLASS="COMMAND" +>smbd</B +> not to send any network traffic out. Used for debugging by the developers only.</P ></DD @@ -181,7 +190,12 @@ CLASS="COMMAND" >-d <debug level></DT ><DD ><P ->debuglevel is an integer +><TT +CLASS="REPLACEABLE" +><I +>debuglevel</I +></TT +> is an integer from 0 to 10. The default value if this parameter is not specified is zero.</P ><P @@ -217,8 +231,11 @@ CLASS="FILENAME" >-l <log file></DT ><DD ><P ->If specified, <EM ->log file</EM +>If specified, <TT +CLASS="REPLACEABLE" +><I +>log file</I +></TT > specifies a log filename into which informational and debug messages from the running server will be logged. The log @@ -261,7 +278,12 @@ CLASS="FILENAME" >-p <port number></DT ><DD ><P ->port number is a positive integer +><TT +CLASS="REPLACEABLE" +><I +>port number</I +></TT +> is a positive integer value. The default value if this parameter is not specified is 139.</P ><P @@ -309,7 +331,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN104" +NAME="AEN109" ></A ><H2 >FILES</H2 @@ -407,7 +429,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN137" +NAME="AEN142" ></A ><H2 >LIMITATIONS</H2 @@ -426,7 +448,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN141" +NAME="AEN146" ></A ><H2 >ENVIRONMENTVARIABLES</H2 @@ -436,12 +458,18 @@ NAME="AEN141" CLASS="VARIABLELIST" ><DL ><DT ->PRINTER</DT +><TT +CLASS="ENVAR" +>PRINTER</TT +></DT ><DD ><P >If no printer name is specified to printable services, most systems will use the value of - this variable (or lp if this variable is + this variable (or <TT +CLASS="CONSTANT" +>lp</TT +> if this variable is not defined) as the name of the printer to use. This is not specific to the server, however.</P ></DD @@ -451,7 +479,7 @@ CLASS="VARIABLELIST" ><DIV CLASS="REFSECT1" ><A -NAME="AEN148" +NAME="AEN155" ></A ><H2 >INSTALLATION</H2 @@ -469,10 +497,16 @@ CLASS="FILENAME" program itself should be executable by all, as users may wish to run the server themselves (in which case it will of course run with their privileges). The server should NOT be setuid. On some - systems it may be worthwhile to make smbd setgid to an empty group. + systems it may be worthwhile to make <B +CLASS="COMMAND" +>smbd</B +> setgid to an empty group. This is because some systems may have a security hole where daemon processes that become a user can be attached to with a debugger. - Making the smbd file setgid to an empty group may prevent + Making the <B +CLASS="COMMAND" +>smbd</B +> file setgid to an empty group may prevent this hole from being exploited. This security hole and the suggested fix has only been confirmed on old versions (pre-kernel 2.0) of Linux at the time this was written. It is possible that this hole only @@ -567,7 +601,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN179" +NAME="AEN188" ></A ><H2 >RUNNING THE SERVER AS A DAEMON</H2 @@ -622,7 +656,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN192" +NAME="AEN201" ></A ><H2 >RUNNING THE SERVER ON REQUEST</H2 @@ -631,7 +665,10 @@ NAME="AEN192" CLASS="COMMAND" >inetd </B ->, you can arrange to have the smbd server started +>, you can arrange to have the <B +CLASS="COMMAND" +>smbd</B +> server started whenever a process attempts to connect to it. This requires several changes to the startup files on the host machine. If you are experimenting as an ordinary user rather than as root, you will @@ -755,7 +792,52 @@ CLASS="COMPUTEROUTPUT" ><DIV CLASS="REFSECT1" ><A -NAME="AEN223" +NAME="AEN233" +></A +><H2 +>PAM INTERACTION</H2 +><P +>Samba uses PAM for authentication (when presented with a plaintext + password), for account checking (is this account disabled?) and for + session management. The degree too which samba supports PAM is restricted + by the limitations of the SMB protocol and the + <A +HREF="smb.conf.5.html#OBEYPAMRESRICTIONS" +TARGET="_top" +>obey pam restricions</A +> + smb.conf paramater. When this is set, the following restrictions apply: + </P +><P +></P +><UL +><LI +><P +><EM +>Account Validation</EM +>: All acccesses to a + samba server are checked + against PAM to see if the account is vaild, not disabled and is permitted to + login at this time. This also applies to encrypted logins. + </P +></LI +><LI +><P +><EM +>Session Management</EM +>: When not using share + level secuirty, users must pass PAM's session checks before access + is granted. Note however, that this is bypassed in share level secuirty. + Note also that some older pam configuration files may need a line + added for session support. + </P +></LI +></UL +></DIV +><DIV +CLASS="REFSECT1" +><A +NAME="AEN244" ></A ><H2 >TESTING THE INSTALLATION</H2 @@ -769,8 +851,18 @@ CLASS="COMMAND" > will reread their configuration tables if they receive a HUP signal.</P ><P ->If your machine's name is fred and your - name is mary, you should now be able to connect +>If your machine's name is <TT +CLASS="REPLACEABLE" +><I +>fred</I +></TT +> and your + name is <TT +CLASS="REPLACEABLE" +><I +>mary</I +></TT +>, you should now be able to connect to the service <TT CLASS="FILENAME" >\\fred\mary</TT @@ -803,7 +895,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN235" +NAME="AEN258" ></A ><H2 >VERSION</H2 @@ -814,7 +906,7 @@ NAME="AEN235" ><DIV CLASS="REFSECT1" ><A -NAME="AEN238" +NAME="AEN261" ></A ><H2 >DIAGNOSTICS</H2 @@ -837,19 +929,25 @@ NAME="AEN238" ><DIV CLASS="REFSECT1" ><A -NAME="AEN243" +NAME="AEN266" ></A ><H2 >SIGNALS</H2 ><P ->Sending the smbd a SIGHUP will cause it to - re-load its <TT +>Sending the <B +CLASS="COMMAND" +>smbd</B +> a SIGHUP will cause it to + reload its <TT CLASS="FILENAME" >smb.conf</TT > configuration file within a short period of time.</P ><P ->To shut down a users smbd process it is recommended +>To shut down a user's <B +CLASS="COMMAND" +>smbd</B +> process it is recommended that <B CLASS="COMMAND" >SIGKILL (-9)</B @@ -858,24 +956,37 @@ CLASS="COMMAND" > be used, except as a last resort, as this may leave the shared memory area in an inconsistent state. The safe way to terminate - an smbd is to send it a SIGTERM (-15) signal and wait for + an <B +CLASS="COMMAND" +>smbd</B +> is to send it a SIGTERM (-15) signal and wait for it to die on its own.</P ><P ->The debug log level of smbd may be raised by sending - it a SIGUSR1 (<B +>The debug log level of <B CLASS="COMMAND" ->kill -USR1 <smbd-pid></B ->) - and lowered by sending it a SIGUSR2 (<B +>smbd</B +> may be raised + or lowered using <A +HREF="smbcontrol.1.html" +TARGET="_top" +><B CLASS="COMMAND" ->kill -USR2 <smbd-pid> +>smbcontrol(1) </B ->). This is to allow transient problems to be diagnosed, +></A +> program (SIGUSR[1|2] signals are no longer used in + Samba 2.2). This is to allow transient problems to be diagnosed, whilst still running at a normally low log level.</P ><P >Note that as the signal handlers send a debug write, - they are not re-entrant in smbd. This you should wait until - smbd is in a state of waiting for an incoming smb before + they are not re-entrant in <B +CLASS="COMMAND" +>smbd</B +>. This you should wait until + <B +CLASS="COMMAND" +>smbd</B +> is in a state of waiting for an incoming SMB before issuing them. It is possible to make the signal handlers safe by un-blocking the signals before the select call and re-blocking them after, however this would affect performance.</P @@ -883,7 +994,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN254" +NAME="AEN283" ></A ><H2 >SEE ALSO</H2 @@ -949,7 +1060,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN271" +NAME="AEN300" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbmnt.8.html b/docs/htmldocs/smbmnt.8.html index e083cfd3ba..a7d10b6e19 100644 --- a/docs/htmldocs/smbmnt.8.html +++ b/docs/htmldocs/smbmnt.8.html @@ -54,10 +54,11 @@ CLASS="COMMAND" <B CLASS="COMMAND" >smbmnt</B -> is meant to be installed setuid root - so that normal users can mount their smb shares. It checks - whether the user has write permissions on the mount point and - then mounts the directory.</P +> can be installed setuid root if you want + normal users to be able to mount their SMB shares.</P +><P +>A setuid smbmnt will only allow mounts on directories owned + by the user, and that the user has write permission on.</P ><P >The <B CLASS="COMMAND" @@ -72,11 +73,14 @@ CLASS="COMMAND" > </A >. It should not be invoked directly by users. </P +><P +>smbmount searches the normal PATH for smbmnt. You must ensure + that the smbmnt version in your path matches the smbmount used.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN28" +NAME="AEN30" ></A ><H2 >OPTIONS</H2 @@ -125,7 +129,7 @@ CLASS="VARIABLELIST" ><DD ><P > list of options that are passed as-is to smbfs, if this - command is run on a 2.4 or higher linux kernel. + command is run on a 2.4 or higher Linux kernel. </P ></DD ></DL @@ -134,7 +138,7 @@ CLASS="VARIABLELIST" ><DIV CLASS="REFSECT1" ><A -NAME="AEN55" +NAME="AEN57" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbmount.8.html b/docs/htmldocs/smbmount.8.html index c8c9727be9..b7263ebf83 100644 --- a/docs/htmldocs/smbmount.8.html +++ b/docs/htmldocs/smbmount.8.html @@ -49,28 +49,41 @@ NAME="AEN14" ><B CLASS="COMMAND" >smbmount</B -> mounts a SMB filesystem. It +> mounts a Linux SMB filesystem. It is usually invoked as <B CLASS="COMMAND" ->mount.smb</B -> from +>mount.smbfs</B +> by the <B CLASS="COMMAND" >mount(8)</B > command when using the - "-t smb" option. The kernel must support the smbfs filesystem. </P + "-t smbfs" option. This command only works in Linux, and the kernel must + support the smbfs filesystem. </P ><P ->Options to smbmount are specified as a comma separated +>Options to <B +CLASS="COMMAND" +>smbmount</B +> are specified as a comma-separated list of key=value pairs. It is possible to send options other than those listed here, assuming that smbfs supports them. If you get mount failures, check your kernel log for errors on unknown options.</P ><P ->smbmount is a daemon. After mounting it keeps running until +><B +CLASS="COMMAND" +>smbmount</B +> is a daemon. After mounting it keeps running until the mounted smbfs is umounted. It will log things that happen when in daemon mode using the "machine name" smbmount, so - typically this output will end up in log.smbmount. The - smbmount process may also be called mount.smbfs.</P + typically this output will end up in <TT +CLASS="FILENAME" +>log.smbmount</TT +>. The + <B +CLASS="COMMAND" +>smbmount</B +> process may also be called mount.smbfs.</P ><P ><EM >NOTE:</EM @@ -91,7 +104,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN27" +NAME="AEN31" ></A ><H2 >OPTIONS</H2 @@ -129,6 +142,13 @@ CLASS="COMMAND" > will prompt for a passeword, unless the guest option is given. </P +><P +> Note that password which contain the arguement delimiter + character (i.e. a comma ',') will failed to be parsed correctly + on the command line. However, the same password defined + in the PASSWD environment variable or a credentials file (see + below) will be read correctly. + </P ></DD ><DT >credentials=<filename></DT @@ -155,7 +175,10 @@ CLASS="PROGRAMLISTING" </P ><P >This is preferred over having passwords in plaintext in a - shared file, such as /etc/fstab. Be sure to protect any + shared file, such as <TT +CLASS="FILENAME" +>/etc/fstab</TT +>. Be sure to protect any credentials file properly. </P ></DD @@ -203,7 +226,7 @@ CLASS="PROGRAMLISTING" >dmask=<arg></DT ><DD ><P ->sets the directory mask. This deterines the +>sets the directory mask. This determines the permissions that remote directories have in the local filesystem. The default is based on the current umask. </P ></DD @@ -212,7 +235,9 @@ CLASS="PROGRAMLISTING" ><DD ><P >sets the debug level. This is useful for - tracking down SMB connection problems. </P + tracking down SMB connection problems. A suggested value to + start with is 4. If set too high there will be a lot of + output, possibly hiding the useful output.</P ></DD ><DT >ip=<arg></DT @@ -275,7 +300,7 @@ CLASS="PARAMETER" >iocharset=<arg></DT ><DD ><P -> sets the charset used by the linux side for codepage +> sets the charset used by the Linux side for codepage to charset translations (NLS). Argument should be the name of a charset, like iso8859-1. (Note: only kernel 2.4.0 or later) @@ -311,7 +336,7 @@ CLASS="PARAMETER" ><DIV CLASS="REFSECT1" ><A -NAME="AEN119" +NAME="AEN125" ></A ><H2 >ENVIRONMENT VARIABLES</H2 @@ -336,20 +361,27 @@ CLASS="ENVAR" >The variable <TT CLASS="ENVAR" >PASSWD_FILE</TT -> may contain the pathname of - a file to read the password from. A single line of input is - read and used as password.</P +> may contain the pathname + of a file to read the password from. A single line of input is + read and used as the password.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN127" +NAME="AEN133" ></A ><H2 >BUGS</H2 ><P ->Not many known smbmount bugs. But one smbfs bug is - important enough to mention here anyway:</P +>Passwords and other options containing , can not be handled. + For passwords an alternative way of passing them is in a credentials + file or in the PASSWD environment.</P +><P +>The credentials file does not handle usernames or passwords with + leading space.</P +><P +>One smbfs bug is important enough to mention here, even if it + is a bit misplaced:</P ><P ></P ><UL @@ -357,13 +389,13 @@ NAME="AEN127" ><P >Mounts sometimes stop working. This is usually caused by smbmount terminating. Since smbfs needs smbmount to - reconnect when the server disconnects, the mount will go - dead. A re-mount normally fixes this. At least 2 ways to + reconnect when the server disconnects, the mount will eventually go + dead. An umount/mount normally fixes this. At least 2 ways to trigger this bug are known.</P ></LI ></UL ><P ->Note that the typical response to a bugreport is suggestion +>Note that the typical response to a bug report is suggestion to try the latest version first. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: samba, kernel, distribution)</P @@ -371,18 +403,32 @@ NAME="AEN127" ><DIV CLASS="REFSECT1" ><A -NAME="AEN134" +NAME="AEN142" ></A ><H2 >SEE ALSO</H2 ><P ->Documentation/filesystems/smbfs.txt in the kernel source tree - may contain additional options and information.</P +>Documentation/filesystems/smbfs.txt in the linux kernel + source tree may contain additional options and information.</P +><P +>FreeBSD also has a smbfs, but it is not related to smbmount</P +><P +>For Solaris, HP-UX and others you may want to look at + <A +HREF="smbsh.1.html" +TARGET="_top" +><B +CLASS="COMMAND" +>smbsh(1)</B +></A +> or at other + solutions, such as sharity or perhaps replacing the SMB server with + a NFS server.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN137" +NAME="AEN149" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbpasswd.5.html b/docs/htmldocs/smbpasswd.5.html index 7de54f6309..1f862b6611 100644 --- a/docs/htmldocs/smbpasswd.5.html +++ b/docs/htmldocs/smbpasswd.5.html @@ -101,9 +101,9 @@ CLASS="VARIABLELIST" >Lanman Password Hash</DT ><DD ><P ->This is the LANMAN hash of the users password, +>This is the LANMAN hash of the user's password, encoded as 32 hex digits. The LANMAN hash is created by DES - encrypting a well known string with the users password as the + encrypting a well known string with the user's password as the DES key. This is the same password used by Windows 95/98 machines. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the @@ -111,7 +111,7 @@ CLASS="VARIABLELIST" is not "salted" as the UNIX password is). If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string. If the hex string is equal to - 32 'X' characters then the users account is marked as + 32 'X' characters then the user's account is marked as <TT CLASS="CONSTANT" >disabled</TT @@ -140,14 +140,14 @@ CLASS="CONSTANT" >NT Password Hash</DT ><DD ><P ->This is the Windows NT hash of the users +>This is the Windows NT hash of the user's password, encoded as 32 hex digits. The Windows NT hash is - created by taking the users password as represented in + created by taking the user's password as represented in 16-bit, little-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it. </P ><P >This password hash is considered more secure than - the Lanman Password Hash as it preserves the case of the + the LANMAN Password Hash as it preserves the case of the password and uses a much higher quality hashing algorithm. However, it is still the case that if two users choose the same password this entry will be identical (i.e. the password is @@ -198,7 +198,7 @@ CLASS="CONSTANT" ><EM >N</EM > - This means the - account has no password (the passwords in the fields Lanman + account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored). Note that this will only allow users to log on with no password if the <TT CLASS="PARAMETER" diff --git a/docs/htmldocs/smbpasswd.8.html b/docs/htmldocs/smbpasswd.8.html index 1c4df51941..be82bc8809 100644 --- a/docs/htmldocs/smbpasswd.8.html +++ b/docs/htmldocs/smbpasswd.8.html @@ -24,7 +24,7 @@ NAME="AEN5" ></A ><H2 >Name</H2 ->smbpasswd -- change a users SMB password</DIV +>smbpasswd -- change a user's SMB password</DIV ><DIV CLASS="REFSYNOPSISDIV" ><A @@ -36,7 +36,7 @@ NAME="AEN8" ><B CLASS="COMMAND" >smbpasswd</B -> [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-j DOMAIN] [-U username] [-h] [-s] [username]</P +> [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-j DOMAIN] [-U username[%password]] [-h] [-s] [username]</P ></DIV ><DIV CLASS="REFSECT1" @@ -61,7 +61,7 @@ TARGET="_top" SMB passwords. </P ><P >By default (when run with no arguments) it will attempt to - change the current users SMB password on the local machine. This is + change the current user's SMB password on the local machine. This is similar to the way the <B CLASS="COMMAND" >passwd(1)</B @@ -86,10 +86,10 @@ CLASS="FILENAME" > file. </P ><P >When run by an ordinary user with no options. smbpasswd - will prompt them for their old smb password and then ask them + will prompt them for their old SMB password and then ask them for their new password twice, to ensure that the new password was typed correctly. No passwords will be echoed on the screen - whilst being typed. If you have a blank smb password (specified by + whilst being typed. If you have a blank SMB password (specified by the string "NO PASSWORD" in the smbpasswd file) then just press the <Enter> key when asked for your old password. </P ><P @@ -167,7 +167,7 @@ CLASS="CONSTANT" will fail. </P ><P >If the smbpasswd file is in the 'old' format (pre-Samba 2.0 - format) there is no space in the users password entry to write + format) there is no space in the user's password entry to write this information and so the user is disabled by writing 'X' characters into the password space in the smbpasswd file. See <B CLASS="COMMAND" @@ -217,7 +217,7 @@ CLASS="COMMAND" ><DD ><P ><TT -CLASS="PARAMETER" +CLASS="REPLACEABLE" ><I >debuglevel</I ></TT @@ -500,7 +500,7 @@ CLASS="COMMAND" ><DD ><P >This option causes smbpasswd to be silent (i.e. - not issue prompts) and to read it's old and new passwords from + not issue prompts) and to read its old and new passwords from standard input, rather than from <TT CLASS="FILENAME" >/dev/tty</TT diff --git a/docs/htmldocs/smbsh.1.html b/docs/htmldocs/smbsh.1.html index 3033a50ccd..66081bbe22 100644 --- a/docs/htmldocs/smbsh.1.html +++ b/docs/htmldocs/smbsh.1.html @@ -14,7 +14,7 @@ VLINK="#840084" ALINK="#0000FF" ><H1 ><A -NAME="FINDSMB" +NAME="SMBSH" >smbsh</A ></H1 ><DIV @@ -67,7 +67,7 @@ CLASS="COMMAND" CLASS="COMMAND" >rcp</B >. You must use a - shell that is dynmanically linked in order for <B + shell that is dynamically linked in order for <B CLASS="COMMAND" >smbsh</B > @@ -80,7 +80,7 @@ CLASS="COMMAND" CLASS="COMMAND" > smbsh</B > from the prompt and enter the username and password - that authenticate you to the machine running the Windows NT + that authenticates you to the machine running the Windows NT operating system.</P ><P ><TABLE @@ -133,10 +133,15 @@ CLASS="FILENAME" CLASS="COMMAND" >ls /smb </B -> will show all the machines in your workgroup. The command +> will show a list of workgroups. The command <B CLASS="COMMAND" ->ls /smb/<machine-name></B +>ls /smb/MYGROUP </B +> will show all the machines in + the workgroup MYGROUP. The command + <B +CLASS="COMMAND" +>ls /smb/MYGROUP/<machine-name></B > will show the share names for that machine. You could then, for example, use the <B CLASS="COMMAND" @@ -153,7 +158,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN39" +NAME="AEN40" ></A ><H2 >VERSION</H2 @@ -164,7 +169,7 @@ NAME="AEN39" ><DIV CLASS="REFSECT1" ><A -NAME="AEN42" +NAME="AEN43" ></A ><H2 >BUGS</H2 @@ -197,7 +202,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN51" +NAME="AEN52" ></A ><H2 >SEE ALSO</H2 @@ -220,7 +225,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN57" +NAME="AEN58" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/smbspool.8.html b/docs/htmldocs/smbspool.8.html index f689b4a0bc..254abe9a9d 100644 --- a/docs/htmldocs/smbspool.8.html +++ b/docs/htmldocs/smbspool.8.html @@ -89,10 +89,8 @@ TARGET="_top" ><P >smbspool tries to get the URI from argv[0]. If argv[0] contains the name of the program then it looks in the <TT -CLASS="PARAMETER" -><I -> DEVICE_URI</I -></TT +CLASS="ENVAR" +> DEVICE_URI</TT > environment variable.</P ><P >Programs using the <B @@ -101,10 +99,8 @@ CLASS="COMMAND" > functions can pass the URI in argv[0], while shell scripts must set the <TT -CLASS="PARAMETER" -><I ->DEVICE_URI</I -></TT +CLASS="ENVAR" +>DEVICE_URI</TT > environment variable prior to running smbspool.</P ></DIV diff --git a/docs/htmldocs/smbumount.8.html b/docs/htmldocs/smbumount.8.html index 0a26e72094..68929fd5f9 100644 --- a/docs/htmldocs/smbumount.8.html +++ b/docs/htmldocs/smbumount.8.html @@ -51,7 +51,7 @@ NAME="AEN12" CLASS="COMMAND" >smbumount</B > has - been written to give normal linux-users more control over their + been written to give normal Linux users more control over their resources. It is safe to install this program suid root, because only the user who has mounted a filesystem is allowed to unmount it again. For root it is not necessary to use smbumount. The normal umount diff --git a/docs/htmldocs/swat.8.html b/docs/htmldocs/swat.8.html index be16272bb6..386fe5bc7a 100644 --- a/docs/htmldocs/swat.8.html +++ b/docs/htmldocs/swat.8.html @@ -68,15 +68,24 @@ CLASS="FILENAME" CLASS="COMMAND" >swat</B > configuration page has help links - to all the configurable options in the smb.conf file allowing an + to all the configurable options in the <TT +CLASS="FILENAME" +>smb.conf</TT +> file allowing an administrator to easily look up the effects of any change. </P ><P ->swat is run from inetd </P +><B +CLASS="COMMAND" +>swat</B +> is run from <B +CLASS="COMMAND" +>inetd</B +> </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN23" +NAME="AEN26" ></A ><H2 >OPTIONS</H2 @@ -95,7 +104,10 @@ CLASS="VARIABLELIST" CLASS="COMMAND" >smbd </B -> server. This is the file that swat will modify. +> server. This is the file that <B +CLASS="COMMAND" +>swat</B +> will modify. The information in this file includes server-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide. @@ -110,8 +122,14 @@ CLASS="FILENAME" ><DD ><P >This option disables authentication and puts - swat in demo mode. In that mode anyone will be able to modify - the smb.conf file. </P + <B +CLASS="COMMAND" +>swat</B +> in demo mode. In that mode anyone will be able to modify + the <TT +CLASS="FILENAME" +>smb.conf</TT +> file. </P ><P ><EM >Do NOT enable this option on a production @@ -124,7 +142,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN38" +NAME="AEN44" ></A ><H2 >INSTALLATION</H2 @@ -158,7 +176,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT2" ><A -NAME="AEN50" +NAME="AEN56" ></A ><H3 >Inetd Installation</H3 @@ -171,7 +189,10 @@ CLASS="FILENAME" CLASS="FILENAME" >/etc/services</TT > - to enable SWAT to be launched via inetd.</P + to enable SWAT to be launched via <B +CLASS="COMMAND" +>inetd</B +>.</P ><P >In <TT CLASS="FILENAME" @@ -228,15 +249,15 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT2" ><A -NAME="AEN71" +NAME="AEN78" ></A ><H3 >Launching</H3 ><P ->To launch swat just run your favorite web browser and +>To launch SWAT just run your favorite web browser and point it at "http://localhost:901/".</P ><P ->Note that you can attach to swat from any IP connected +>Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire. </P @@ -245,7 +266,7 @@ NAME="AEN71" ><DIV CLASS="REFSECT1" ><A -NAME="AEN75" +NAME="AEN82" ></A ><H2 >FILES</H2 @@ -303,7 +324,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN96" +NAME="AEN103" ></A ><H2 >WARNINGS</H2 @@ -335,7 +356,7 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN104" +NAME="AEN111" ></A ><H2 >VERSION</H2 @@ -346,7 +367,7 @@ NAME="AEN104" ><DIV CLASS="REFSECT1" ><A -NAME="AEN107" +NAME="AEN114" ></A ><H2 >SEE ALSO</H2 @@ -373,7 +394,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN114" +NAME="AEN121" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/testparm.1.html b/docs/htmldocs/testparm.1.html index 599746e414..bae907c687 100644 --- a/docs/htmldocs/testparm.1.html +++ b/docs/htmldocs/testparm.1.html @@ -125,7 +125,12 @@ CLASS="COMMAND" >-L servername</DT ><DD ><P ->Sets the value of the %L macro to servername. +>Sets the value of the %L macro to <TT +CLASS="REPLACEABLE" +><I +>servername</I +></TT +>. This is useful for testing include files specified with the %L macro. </P ></DD @@ -146,7 +151,10 @@ CLASS="FILENAME" ><DD ><P >If this parameter and the following are - specified, then testparm will examine the <TT + specified, then <B +CLASS="COMMAND" +>testparm</B +> will examine the <TT CLASS="PARAMETER" ><I >hosts @@ -184,7 +192,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN64" +NAME="AEN66" ></A ><H2 >FILES</H2 @@ -213,13 +221,13 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN73" +NAME="AEN75" ></A ><H2 >DIAGNOSTICS</H2 ><P >The program will issue a message saying whether the - configuration file loaded OK or not. This message may be preceeded by + configuration file loaded OK or not. This message may be preceded by errors and warnings if the file did not load. If the file was loaded OK, the program then dumps all known service details to stdout. </P @@ -227,7 +235,7 @@ NAME="AEN73" ><DIV CLASS="REFSECT1" ><A -NAME="AEN76" +NAME="AEN78" ></A ><H2 >VERSION</H2 @@ -238,7 +246,7 @@ NAME="AEN76" ><DIV CLASS="REFSECT1" ><A -NAME="AEN79" +NAME="AEN81" ></A ><H2 >SEE ALSO</H2 @@ -264,7 +272,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN86" +NAME="AEN88" ></A ><H2 >AUTHOR</H2 diff --git a/docs/htmldocs/wbinfo.1.html b/docs/htmldocs/wbinfo.1.html index 2787f514c0..badeb6961e 100644 --- a/docs/htmldocs/wbinfo.1.html +++ b/docs/htmldocs/wbinfo.1.html @@ -35,7 +35,7 @@ NAME="AEN8" ><P ><B CLASS="COMMAND" ->nmblookup</B +>wbinfo</B > [-u] [-g] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m]</P ></DIV ><DIV @@ -243,25 +243,27 @@ NAME="AEN88" CLASS="COMMAND" >winbindd(8) </B -> daemon is not working wbinfo will always return +> daemon is not working <B +CLASS="COMMAND" +>wbinfo</B +> will always return failure. </P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN92" +NAME="AEN93" ></A ><H2 >VERSION</H2 ><P >This man page is correct for version 2.2 of - the Samba suite. winbindd is however not available in - stable release of Samba as of yet.</P + the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN95" +NAME="AEN96" ></A ><H2 >SEE ALSO</H2 @@ -279,7 +281,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN100" +NAME="AEN101" ></A ><H2 >AUTHOR</H2 @@ -296,7 +298,7 @@ CLASS="COMMAND" CLASS="COMMAND" >winbindd</B > - were written by TIm Potter.</P + were written by Tim Potter.</P ><P >The conversion to DocBook for Samba 2.2 was done by Gerald Carter</P diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html index 2f023561ed..addf74935c 100644 --- a/docs/htmldocs/winbind.html +++ b/docs/htmldocs/winbind.html @@ -1,7 +1,7 @@ <HTML ><HEAD ><TITLE ->Unifed Logons between Windows NT and UNIX using Winbind</TITLE +>Unified Logons between Windows NT and UNIX using Winbind</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD @@ -19,8 +19,8 @@ CLASS="TITLEPAGE" ><H1 CLASS="TITLE" ><A -NAME="AEN1" ->Unifed Logons between Windows NT and UNIX using Winbind</A +NAME="WINBIND" +>Unified Logons between Windows NT and UNIX using Winbind</A ></H1 ><HR></DIV ><DIV @@ -34,12 +34,13 @@ NAME="AEN3" ><P >Integration of UNIX and Microsoft Windows NT through a unified logon has been considered a "holy grail" in heterogeneous - computing environments for a long time. We present <I + computing environments for a long time. We present + <I CLASS="EMPHASIS" ->winbind - </I ->, a component of the Samba suite of programs as a - solution to the unied logon problem. Winbind uses a UNIX implementation +>winbind</I +>, a component of the Samba suite + of programs as a 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 @@ -66,11 +67,11 @@ NAME="AEN7" and use the Samba suite of programs to provide file and print services between the two. This solution is far from perfect however, as adding and deleting users on both sets of machines becomes a chore - and two sets of passwords are required both of which which + and two sets of passwords are required both of which 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 @@ -97,7 +98,7 @@ NAME="AEN7" 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 @@ -119,7 +120,7 @@ NAME="AEN20" >The end result is that whenever any program on the UNIX machine asks the operating system to lookup a user or group name, the query will be resolved by asking the - NT domain controller for the specied domain to do the lookup. + NT domain controller for the specified domain to do the lookup. Because Winbind hooks into the operating system at a low level (via the NSS name resolution modules in the C library) this redirection to the NT domain controller is completely @@ -136,11 +137,11 @@ NAME="AEN20" that redirection to a domain controller is wanted for a particular lookup and which trusted domain is being referenced.</P ><P ->Additionally, Winbind provides a authentication service +>Additionally, Winbind provides an authentication service that hooks into the Pluggable Authentication Modules (PAM) system to provide authentication via a NT domain to any PAM enabled applications. This capability solves the problem of synchronizing - passwords between systems as all passwords are stored in a single + passwords between systems since all passwords are stored in a single location (on the domain controller).</P ><DIV CLASS="SECT2" @@ -155,9 +156,9 @@ NAME="AEN27" existing NT based domain infrastructure into which they wish to put UNIX workstations or servers. Winbind will allow these organizations to deploy UNIX workstations without having to - maintain a separate account infrastructure. This greatly simplies - the administrative overhead of deploying UNIX workstations into - a NT based organization.</P + maintain a separate account infrastructure. This greatly + simplifies the administrative overhead of deploying UNIX + workstations into a NT based organization.</P ><P >Another interesting way in which we expect Winbind to be used is as a central part of UNIX based appliances. Appliances @@ -224,11 +225,11 @@ NAME="AEN40" >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 + flat files stored on the local filesystem. A networked workstation may first attempt to resolve system information from local files, - then consult a NIS database for user information or a DNS server + and then consult a NIS database for user information or a DNS server for hostname information.</P ><P >The NSS application programming interface allows winbind @@ -241,11 +242,12 @@ NAME="AEN40" a NT domain plus any trusted domain as though they were local users and groups.</P ><P ->The primary control le for NSS is <TT +>The primary control file for NSS is + <TT CLASS="FILENAME" ->/etc/nsswitch.conf - </TT ->. When a UNIX application makes a request to do a lookup +>/etc/nsswitch.conf</TT +>. + When a UNIX application makes a request to do a lookup the C library looks in <TT CLASS="FILENAME" >/etc/nsswitch.conf</TT @@ -253,7 +255,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 @@ -303,7 +305,7 @@ NAME="AEN56" >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 @@ -315,10 +317,10 @@ NAME="AEN56" UNIX system. This allows Windows NT users to log in to a UNIX machine and be authenticated against a suitable Primary Domain Controller. These users can also change their passwords and have - this change take eect directly on the Primary Domain Controller. + this change take effect 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 @@ -335,7 +337,7 @@ CLASS="FILENAME" is copied to <TT CLASS="FILENAME" >/lib/security/</TT -> and the pam +> and the PAM control files for relevant services are updated to allow authentication via winbind. See the PAM documentation for more details.</P @@ -350,11 +352,11 @@ NAME="AEN64" ></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 that 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 @@ -363,7 +365,7 @@ NAME="AEN64" to UNIX user ids and group ids.</P ><P >The results of this mapping are stored persistently in - a ID mapping database held in a tdb database). This ensures that + an ID mapping database held in a tdb database). This ensures that RIDs are mapped to UNIX IDs in a consistent way.</P ></DIV ><DIV @@ -381,7 +383,7 @@ NAME="AEN68" 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 @@ -398,39 +400,702 @@ NAME="AEN71" >Installation and Configuration</A ></H1 ><P ->The easiest way to install winbind is by using the packages - provided in the <TT +>Many thanks to John Trostel <A +HREF="mailto:jtrostel@snapserver.com" +TARGET="_top" +>jtrostel@snapserver.com</A +> +for providing the HOWTO for this section.</P +><P +>This HOWTO describes how to get winbind services up and running +to control access and authenticate users on your Linux box using +the winbind services which come with SAMBA 2.2.2.</P +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN76" +>Introduction</A +></H2 +><P +>This HOWTO describes the procedures used to get winbind up and +running on my RedHat 7.1 system. Winbind is capable of providing access +and authentication control for Windows Domain users through an NT +or Win2K PDC for 'regular' services, such as telnet a nd ftp, as +well for SAMBA services.</P +><P +>This HOWTO has been written from a 'RedHat-centric' perspective, so if +you are using another distribution, you may have to modify the instructions +somewhat to fit the way your distribution works.</P +><P +></P +><UL +><LI +><P +> <I +CLASS="EMPHASIS" +>Why should I to this?</I +> + </P +><P +>This allows the SAMBA administrator to rely on the + authentication mechanisms on the NT/Win2K PDC for the authentication + of domain members. NT/Win2K users no longer need to have separate + accounts on the SAMBA server. + </P +></LI +><LI +><P +> <I +CLASS="EMPHASIS" +>Who should be reading this document?</I +> + </P +><P +> This HOWTO is designed for system administrators. If you are + implementing SAMBA on a file server and wish to (fairly easily) + integrate existing NT/Win2K users from your PDC onto the + SAMBA server, this HOWTO is for you. That said, I am no NT or PAM + expert, so you may find a better or easier way to accomplish + these tasks. + </P +></LI +></UL +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN89" +>Requirements</A +></H2 +><P +>If you have a samba configuration file that you are currently +using... BACK IT UP! If your system already uses PAM, BACK UP +THE <TT +CLASS="FILENAME" +>/etc/pam.d</TT +> directory contents! If you +haven't already made a boot disk, MAKE ON NOW!</P +><P +>Messing with the pam configuration files can make it nearly impossible +to log in to yourmachine. That's why you want to be able to boot back +into your machine in single user mode and restore your +<TT +CLASS="FILENAME" +>/etc/pam.d</TT +> back to the original state they were in if +you get frustrated with the way things are going. ;-)</P +><P +>The newest version of SAMBA (version 2.2.2), available from +cvs.samba.org, now include a functioning winbindd daemon. Please refer +to the main SAMBA web page or, better yet, your closest SAMBA mirror +site for instructions on downloading the source code.</P +><P +>To allow Domain users the ability to access SAMBA shares and +files, as well as potentially other services provided by your +SAMBA machine, PAM (pluggable authentication modules) must +be setup properly on your machine. In order to compile the +winbind modules, you should have at least the pam libraries resident +on your system. For recent RedHat systems (7.1, for instance), that +means 'pam-0.74-22'. For best results, it is helpful to also +install the development packages in 'pam-devel-0.74-22'.</P +></DIV +><DIV +CLASS="SECT2" +><HR><H2 +CLASS="SECT2" +><A +NAME="AEN97" +>Testing Things Out</A +></H2 +><P +>Before starting, it is probably best to kill off all the SAMBA +related daemons running on your server. Kill off all <B +CLASS="COMMAND" +>smbd</B +>, +<B +CLASS="COMMAND" +>nmbd</B +>, and <B +CLASS="COMMAND" +>winbindd</B +> processes that may +be running. To use PAM, you will want to make sure that you have the +standard PAM package (for RedHat) which supplies the <TT +CLASS="FILENAME" +>/etc/pam.d</TT +> +directory structure, including the pam modules are used by pam-aware +services, several pam libraries, and the <TT +CLASS="FILENAME" +>/usr/doc</TT +> +and <TT +CLASS="FILENAME" +>/usr/man</TT +> entries for pam. Winbind built better +in SAMBA if the pam-devel package was also installed. This package includes +the header files needed to compile pam-aware applications. For instance, my RedHat +system has both 'pam-0.74-22' and 'pam-devel-0.74-22' RPMs installed.</P +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN106" +>Configure and compile SAMBA</A +></H3 +><P +>The configuration and compilation of SAMBA is pretty straightforward. +The first three steps maynot be necessary depending upon +whether or not you have previously built the Samba binaries.</P +><P +><PRE +CLASS="PROGRAMLISTING" +><TT +CLASS="PROMPT" +>root# </TT +> autoconf +<TT +CLASS="PROMPT" +>root# </TT +> make clean +<TT +CLASS="PROMPT" +>root# </TT +> rm config.cache +<TT +CLASS="PROMPT" +>root# </TT +> ./configure --with-winbind +<TT +CLASS="PROMPT" +>root# </TT +> make +<TT +CLASS="PROMPT" +>root# </TT +> make install</PRE +></P +><P +>This will, by default, install SAMBA in /usr/local/samba. See the +main SAMBA documentation if you want to install SAMBA somewhere else. +It will also build the winbindd executable and libraries. </P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN118" +>Configure nsswitch.conf and the winbind libraries</A +></H3 +><P +>The libraries needed to run the winbind daemon through nsswitch +need to be copied to their proper locations, so</P +><P +><TT +CLASS="PROMPT" +>root# </TT +> cp ../samba/source/nsswitch/libnss_winbind.so /lib</P +><P +>I also found it necessary to make the following symbolic link:</P +><P +><TT +CLASS="PROMPT" +>root# </TT +> ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</P +><P +>Now, as root you need to edit <TT CLASS="FILENAME" ->pub/samba/appliance/</TT +>/etc/nsswitch.conf</TT +> to +allow user and group entries to be visible from the <B +CLASS="COMMAND" +>winbindd</B > - directory on your nearest - Samba mirror. These packages provide snapshots of the Samba source - code and binaries already setup to provide the full functionality - of winbind. This setup is a little more complex than a normal Samba - build as winbind needs a small amount of functionality from a - development code branch called SAMBA_TNG.</P -><P ->Once you have installed the packages you should read - the <B +daemon, as well as from your /etc/hosts files and NIS servers. My +<TT +CLASS="FILENAME" +>/etc/nsswitch.conf</TT +> file look like this after editing:</P +><P +><PRE +CLASS="PROGRAMLISTING" +> passwd: files winbind + shadow: files winbind + group: files winbind</PRE +></P +><P +> +The libraries needed by the winbind daemon will be automatically +entered into the ldconfig cache the next time your system reboots, but it +is faster (and you don't need to reboot) if you do it manually:</P +><P +><TT +CLASS="PROMPT" +>root# </TT +> /sbin/ldconfig -v | grep winbind</P +><P +>This makes <TT +CLASS="FILENAME" +>libnss_winbind</TT +> available to winbindd +and echos back a check to you.</P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN137" +>Configure smb.conf</A +></H3 +><P +>Several parameters are needed in the smb.conf file to control +the behavior of <B CLASS="COMMAND" ->winbindd(8)</B -> man page which will provide you - with conguration information and give you sample conguration 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 +>winbindd</B +>. Configure +<TT +CLASS="FILENAME" +>smb.conf</TT +> These are described in more detail in +the <A +HREF="winbindd.8.html" +TARGET="_top" +>winbindd(8)</A +> man page. My +<TT +CLASS="FILENAME" +>smb.conf</TT +> file was modified to +include the following entries in the [global] section:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>[global] + <...> + # separate domain and username with '+', like DOMAIN+username + winbind separator = + + # use uids from 10000 to 20000 for domain users + winbind uid = 10000-20000 + # use gids from 10000 to 20000 for domain groups + winbind gid = 10000-20000 + # allow enumeration of winbind users and groups + winbind enum users = yes + winbind enum groups = yes + # give winbind users a real shell (only needed if they have telnet access) + template shell = /bin/bash</PRE +></P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN146" +>Join the SAMBA server to the PDC domain</A +></H3 +><P +>Enter the following command to make the SAMBA server join the +PDC domain, where <TT +CLASS="REPLACEABLE" +><I +>DOMAIN</I +></TT +> is the name of +your Windows domain and <TT +CLASS="REPLACEABLE" +><I +>Administrator</I +></TT +> is +a domain user who has administrative privileges in the domain.</P +><P +><TT +CLASS="PROMPT" +>root# </TT +>/usr/local/samba/bin/smbpasswd -j DOMAIN -r PDC -U Administrator</P +><P +>The proper response to the command should be: "Joined the domain +<TT +CLASS="REPLACEABLE" +><I +>DOMAIN</I +></TT +>" where <TT +CLASS="REPLACEABLE" +><I +>DOMAIN</I +></TT +> +is your DOMAIN name.</P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN156" +>Start up the winbindd daemon and test it!</A +></H3 +><P +>Eventually, you will want to modify your smb startup script to +automatically invoke the winbindd daemon when the other parts of +SAMBA start, but it is possible to test out just the winbind +portion first. To start up winbind services, enter the following +command as root:</P +><P +><TT +CLASS="PROMPT" +>root# </TT +>/usr/local/samba/bin/winbindd</P +><P +>I'm always paranoid and like to make sure the daemon +is really running...</P +><P +><TT +CLASS="PROMPT" +>root# </TT +> ps -ae | grep winbindd +3025 ? 00:00:00 winbindd</P +><P +>Now... for the real test, try to get some information about the +users on your PDC</P +><P +><TT +CLASS="PROMPT" +>root# </TT +> # /usr/local/samba/bin/wbinfo -u</P +><P +> +This should echo back a list of users on your Windows users on +your PDC. For example, I get the following response:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>CEO+Administrator +CEO+burdell +CEO+Guest +CEO+jt-ad +CEO+krbtgt +CEO+TsInternetUser</PRE +></P +><P +>Obviously, I have named my domain 'CEO' and my winbindd separator is '+'.</P +><P +>You can do the same sort of thing to get group information from +the PDC:</P +><P +><PRE +CLASS="PROGRAMLISTING" +><TT +CLASS="PROMPT" +>root# </TT +>/usr/local/samba/bin/wbinfo -g +CEO+Domain Admins +CEO+Domain Users +CEO+Domain Guests +CEO+Domain Computers +CEO+Domain Controllers +CEO+Cert Publishers +CEO+Schema Admins +CEO+Enterprise Admins +CEO+Group Policy Creator Owners</PRE +></P +><P +>The function 'getent' can now be used to get unified +lists of both local and PDC users and groups. +Try the following command:</P +><P +><TT +CLASS="PROMPT" +>root# </TT +> getent passwd</P +><P +>You should get a list that looks like your <TT +CLASS="FILENAME" +>/etc/passwd</TT +> +list followed by the domain users with their new uids, gids, home +directories and default shells.</P +><P +>The same thing can be done for groups with the command</P +><P +><TT +CLASS="PROMPT" +>root# </TT +> getent group</P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN183" +>Fix the /etc/rc.d/init.d/smb startup files</A +></H3 +><P +>The <B +CLASS="COMMAND" +>winbindd</B +> daemon needs to start up after the +<B +CLASS="COMMAND" +>smbd</B +> and <B +CLASS="COMMAND" +>nmbd</B +> daemons are running. +To accomplish this task, you need to modify the <TT +CLASS="FILENAME" +>/etc/init.d/smb</TT +> +script to add commands to invoke this daemon in the proper sequence. My +<TT +CLASS="FILENAME" +>/etc/init.d/smb</TT +> file starts up <B +CLASS="COMMAND" +>smbd</B +>, +<B +CLASS="COMMAND" +>nmbd</B +>, and <B +CLASS="COMMAND" +>winbindd</B +> from the +<TT +CLASS="FILENAME" +>/usr/local/samba/bin</TT +> directory directly. The 'start' +function in the script looks like this:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>start() { + KIND="SMB" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/smbd $SMBDOPTIONS + RETVAL=$? + echo + KIND="NMB" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/nmbd $NMBDOPTIONS + RETVAL2=$? + echo + KIND="Winbind" + echo -n $"Starting $KIND services: " + daemon /usr/local/samba/bin/winbindd + RETVAL3=$? + echo + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && touch /var/lock/subsys/smb || \ + RETVAL=1 + return $RETVAL +}</PRE +></P +><P +>The 'stop' function has a corresponding entry to shut down the +services and look s like this:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>stop() { + KIND="SMB" + echo -n $"Shutting down $KIND services: " + killproc smbd + RETVAL=$? + echo + KIND="NMB" + echo -n $"Shutting down $KIND services: " + killproc nmbd + RETVAL2=$? + echo + KIND="Winbind" + echo -n $"Shutting down $KIND services: " + killproc winbindd + RETVAL3=$? + [ $RETVAL -eq 0 -a $RETVAL2 -eq 0 -a $RETVAL3 -eq 0 ] && rm -f /var/lock/subsys/smb + echo "" + return $RETVAL +}</PRE +></P +></DIV +><DIV +CLASS="SECT3" +><HR><H3 +CLASS="SECT3" +><A +NAME="AEN200" +>Configure Winbind and PAM</A +></H3 +><P +>If you have made it this far, you know that winbindd is working. +Now it is time to integrate it into the operation of samba and other +services. The pam configuration files need to be altered in +this step. (Did you remember to make backups of your original +<TT +CLASS="FILENAME" +>/etc/pam.d</TT +> files? If not, do it now.)</P +><P +>To get samba to allow domain users and groups, I modified the +<TT +CLASS="FILENAME" +>/etc/pam.d/samba</TT +> file from</P +><P +><PRE +CLASS="PROGRAMLISTING" +>auth required /lib/security/pam_stack.so service=system-auth +account required /lib/security/pam_stack.so service=system-auth</PRE +></P +><P +>to</P +><P +><PRE +CLASS="PROGRAMLISTING" +>auth required /lib/security/pam_winbind.so +auth required /lib/security/pam_stack.so service=system-auth +account required /lib/security/pam_winbind.so +account required /lib/security/pam_stack.so service=system-auth</PRE +></P +><P +>The other services that I modified to allow the use of winbind +as an authentication service were the normal login on the console (or a terminal +session), telnet logins, and ftp service. In order to enable these +services, you may first need to change the entries in +<TT +CLASS="FILENAME" +>/etc/xinetd.d</TT +> (or <TT +CLASS="FILENAME" +>/etc/inetd.conf</TT +>). +RedHat 7.1 uses the new xinetd.d structure, in this case you need +to change the lines in <TT +CLASS="FILENAME" +>/etc/xinetd.d/telnet</TT +> +and <TT +CLASS="FILENAME" +>/etc/xinetd.d/wu-ftp</TT +> from </P +><P +><PRE +CLASS="PROGRAMLISTING" +>enable = no</PRE +></P +><P +>to</P +><P +><PRE +CLASS="PROGRAMLISTING" +>enable = yes</PRE +></P +><P +> +For ftp services to work properly, you will also need to either +have individual directories for the domain users already present on +the server, or change the home directory template to a general +directory for all domain users. These can be easily set using +the <TT +CLASS="FILENAME" +>smb.conf</TT +> global entry +<B +CLASS="COMMAND" +>template homedir</B +>.</P +><P +>The <TT +CLASS="FILENAME" +>/etc/pam.d/ftp</TT +> file can be changed +to allow winbind ftp access in a manner similar to the +samba file. My <TT +CLASS="FILENAME" +>/etc/pam.d/ftp</TT +> file was +changed to look like this:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>auth sufficient /lib/security/pam_winbind.so +auth required /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed +auth required /lib/security/pam_stack.so service=system-auth +auth required /lib/security/pam_shells.so +account required /lib/security/pam_stack.so service=system-auth +session required /lib/security/pam_stack.so service=system-auth</PRE +></P +><P +>The <TT +CLASS="FILENAME" +>/etc/pam.d/login</TT +> file can be changed nearly the +same way. It now looks like this:</P +><P +><PRE +CLASS="PROGRAMLISTING" +>auth required /lib/security/pam_securetty.so +auth sufficient /lib/security/pam_winbind.so +auth sufficient /lib/security/pam_unix.so use_first_pass +auth required /lib/security/pam_stack.so service=system-auth +auth required /lib/security/pam_nologin.so +account sufficient /lib/security/pam_winbind.so +account required /lib/security/pam_stack.so service=system-auth +password required /lib/security/pam_stack.so service=system-auth +session required /lib/security/pam_stack.so service=system-auth +session optional /lib/security/pam_console.so</PRE +></P +><P +>In this case, I added the <B +CLASS="COMMAND" +>auth sufficient /lib/security/pam_winbind.so</B +> +lines as before, but also added the <B +CLASS="COMMAND" +>required pam_securetty.so</B +> +above it, to disallow root logins over the network. I also added a +<B +CLASS="COMMAND" +>sufficient /lib/security/pam_unix.so use_first_pass</B +> +line after the <B +CLASS="COMMAND" +>winbind.so</B +> line to get rid of annoying +double prompts for passwords.</P +><P +>Finally, don't forget to copy the winbind pam modules from +the source directory in which you originally compiled the new +SAMBA up to the /lib/security directory so that pam can use it:</P +><P +><TT +CLASS="PROMPT" +>root# </TT +> cp ../samba/source/nsswitch/pam_winbind.so /lib/security</P +></DIV +></DIV ></DIV ><DIV CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN77" +NAME="AEN241" >Limitations</A ></H1 ><P >Winbind has a number of limitations in its current - released version which we hope to overcome in future + released version that we hope to overcome in future releases:</P ><P ></P @@ -459,13 +1124,6 @@ NAME="AEN77" into account possible workstation and logon time restrictions that may be been set for Windows NT users.</P ></LI -><LI -><P ->Building winbind from source is currently - quite tedious as it requires combining source code from two Samba - branches. Work is underway to solve this by providing all - the necessary functionality in the main Samba code branch.</P -></LI ></UL ></DIV ><DIV @@ -473,7 +1131,7 @@ CLASS="SECT1" ><HR><H1 CLASS="SECT1" ><A -NAME="AEN89" +NAME="AEN251" >Conclusion</A ></H1 ><P diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html index 938c2dcb2f..ad54228a6f 100644 --- a/docs/htmldocs/winbindd.8.html +++ b/docs/htmldocs/winbindd.8.html @@ -36,23 +36,22 @@ NAME="AEN8" ><P ><B CLASS="COMMAND" ->nmblookup</B -> [-d debuglevel] [-i] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] {name}</P +>winbindd</B +> [-i] [-d <debug level>] [-s <smb config file>]</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN24" +NAME="AEN14" ></A ><H2 >DESCRIPTION</H2 ><P ->This tool is part of the <A +>This program is part of the <A HREF="samba.7.html" TARGET="_top" > Samba</A -> suite version 3.0 and describes functionality not - yet implemented in the main version of Samba.</P +> suite.</P ><P ><B CLASS="COMMAND" @@ -70,7 +69,10 @@ CLASS="FILENAME" of user and group ids specified by the administrator of the Samba system.</P ><P ->The service provided by winbindd is called `winbind' and +>The service provided by <B +CLASS="COMMAND" +>winbindd</B +> is called `winbind' and can be used to resolve user and group information from a Windows NT server. The service can also provide authentication services via an associated PAM module. </P @@ -147,7 +149,7 @@ group: files winbind ><DIV CLASS="REFSECT1" ><A -NAME="AEN52" +NAME="AEN43" ></A ><H2 >OPTIONS</H2 @@ -186,7 +188,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN65" +NAME="AEN56" ></A ><H2 >NAME AND ID RESOLUTION</H2 @@ -217,7 +219,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN71" +NAME="AEN62" ></A ><H2 >CONFIGURATION</H2 @@ -252,7 +254,7 @@ CLASS="COMMAND" DOMAIN\username. In some cases this separator character may cause problems as the '\' character has special meaning in unix shells. In that case you can use the winbind separator - option to specify an alternative sepataror character. Good + option to specify an alternative separator character. Good alternatives may be '/' (although that conflicts with the unix directory separator) or a '+ 'character. The '+' character appears to be the best choice for 100% @@ -276,7 +278,7 @@ CLASS="COMMAND" ><P >The winbind uid parameter specifies the range of user ids that are allocated by the winbindd daemon. - This range of ids should have no existing local or nis users + This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise. </P ><P >Default: <B @@ -296,7 +298,7 @@ CLASS="COMMAND" ><P >The winbind gid parameter specifies the range of group ids that are allocated by the winbindd daemon. - This range of group ids should have no existing local or nis + This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise.</P ><P >Default: <B @@ -319,7 +321,7 @@ CLASS="COMMAND" seconds the winbindd daemon will cache user and group information before querying a Windows NT server again. When a item in the cache is older than this time winbindd will ask the domain - controller for the sequence number of the servers account database. + controller for the sequence number of the server's account database. If the sequence number has not changed then the cached item is marked as valid for a further <TT CLASS="PARAMETER" @@ -375,7 +377,10 @@ CLASS="COMMAND" ><EM >Warning:</EM > Turning off user enumeration - may cause some programs to behave oddly. For example, the finger + may cause some programs to behave oddly. For example, the <B +CLASS="COMMAND" +>finger</B +> program relies on having access to the full user list when searching for matching usernames. </P ><P @@ -479,7 +484,7 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN152" +NAME="AEN144" ></A ><H2 >EXAMPLE SETUP</H2 @@ -563,12 +568,13 @@ CLASS="COMMAND" >The next step is to join the domain. To do that use the <B CLASS="COMMAND" ->samedit</B +>smbpasswd</B > program like this: </P ><P ><B CLASS="COMMAND" ->samedit -S '*' -W DOMAIN -UAdministrator</B +>smbpasswd -j DOMAIN -r PDC -U + Administrator</B ></P ><P >The username after the <TT @@ -576,20 +582,10 @@ CLASS="PARAMETER" ><I >-U</I ></TT -> can be any Domain - user that has administrator priviliges on the machine. Next from - within <B -CLASS="COMMAND" ->samedit</B ->, run the command: </P -><P -><B -CLASS="COMMAND" ->createuser MACHINE$ -j DOMAIN -L</B -></P -><P ->This assumes your domain is called "DOMAIN" and your Samba - workstation is called "MACHINE". </P +> can be any + Domain user that has administrator privileges on the machine. + Substitute your domain name for "DOMAIN" and the name of your PDC + for "PDC".</P ><P >Next copy <TT CLASS="FILENAME" @@ -620,7 +616,10 @@ CLASS="FILENAME" >/lib/libnss_winbind.so.1</TT >.</P ><P ->Finally, setup a smb.conf containing directives like the +>Finally, setup a <TT +CLASS="FILENAME" +>smb.conf</TT +> containing directives like the following: </P ><P ><TABLE @@ -663,10 +662,10 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN194" +NAME="AEN183" ></A ><H2 ->Notes</H2 +>NOTES</H2 ><P >The following notes are useful when configuring and running <B @@ -697,10 +696,8 @@ CLASS="COMMAND" >winbindd</B > nsswitch module read an environment variable named <TT -CLASS="PARAMETER" -><I -> $WINBINDD_DOMAIN</I -></TT +CLASS="ENVAR" +> $WINBINDD_DOMAIN</TT >. If this variable contains a comma separated list of Windows NT domain names, then winbindd will only resolve users and groups within those Windows NT domains. </P @@ -723,10 +720,10 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN210" +NAME="AEN199" ></A ><H2 ->Signals</H2 +>SIGNALS</H2 ><P >The following signals can be used to manipulate the <B @@ -774,10 +771,10 @@ CLASS="COMMAND" ><DIV CLASS="REFSECT1" ><A -NAME="AEN227" +NAME="AEN216" ></A ><H2 ->Files</H2 +>FILES</H2 ><P ></P ><DIV @@ -826,9 +823,11 @@ CLASS="FILENAME" >Storage for the Windows NT rid to UNIX user/group id mapping. The lock directory is specified when Samba is initially compiled using the <TT -CLASS="FILENAME" ->--with-lockdir</TT -> option. +CLASS="PARAMETER" +><I +>--with-lockdir</I +></TT +> option. This directory is by default <TT CLASS="FILENAME" >/usr/local/samba/var/locks @@ -848,19 +847,18 @@ CLASS="FILENAME" ><DIV CLASS="REFSECT1" ><A -NAME="AEN256" +NAME="AEN245" ></A ><H2 >VERSION</H2 ><P ->This man page is correct for version 2.2 of - the Samba suite. winbindd is however not available in - stable release of Samba as of yet.</P +>This man page is correct for version 2.2 of + the Samba suite.</P ></DIV ><DIV CLASS="REFSECT1" ><A -NAME="AEN259" +NAME="AEN248" ></A ><H2 >SEE ALSO</H2 @@ -888,7 +886,7 @@ TARGET="_top" ><DIV CLASS="REFSECT1" ><A -NAME="AEN266" +NAME="AEN255" ></A ><H2 >AUTHOR</H2 |