From a2876f9ded3b175390a8690892c1aeaedae02cfa Mon Sep 17 00:00:00 2001 From: Jeremy Allison Date: Sat, 2 Feb 2002 21:28:10 +0000 Subject: 2.2.3 now in sync. Jeremy. --- docs/htmldocs/Samba-HOWTO-Collection.html | 1014 ++++++++++++++++++++++------- docs/htmldocs/Samba-LDAP-HOWTO.html | 2 +- docs/htmldocs/UNIX_INSTALL.html | 18 +- docs/htmldocs/smbpasswd.8.html | 36 +- docs/htmldocs/winbind.html | 2 +- 5 files changed, 829 insertions(+), 243 deletions(-) (limited to 'docs/htmldocs') diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html index 870b0ec6e82..8009bb8b86f 100644 --- a/docs/htmldocs/Samba-HOWTO-Collection.html +++ b/docs/htmldocs/Samba-HOWTO-Collection.html @@ -668,155 +668,231 @@ HREF="#AEN1602" >
9. Storing Samba's User/Machine Account information in an LDAP DirectoryHow to a Purely Samba Controlled Domain
9.1. PurposePrerequisite Reading
9.2. IntroductionBackground
9.3. Supported LDAP ServersWhat qualifies a Domain Controller on the network?
9.3.1. How does a Workstation find its domain controller?
9.3.2. When is the PDC needed?
9.4. Schema and Relationship to the RFC 2307 posixAccountCan Samba be a Backup Domain Controller?
9.5. smb.conf LDAP parametersHow do I set up a Samba BDC?
9.5.1. How do I replicate the smbpasswd file?
9.6. 10. Storing Samba's User/Machine Account information in an LDAP Directory
10.1. Purpose
10.2. Introduction
10.3. Supported LDAP Servers
10.4. Schema and Relationship to the RFC 2307 posixAccount
10.5. Configuring Samba with LDAP
10.5.1. OpenLDAP configuration
10.5.2. Configuring Samba
10.6. Accounts and Groups management
10.7. Security and sambaAccount
9.7. 10.8. LDAP specials attributes for sambaAccounts
9.8. 10.9. Example LDIF Entries for a sambaAccount
9.9. 10.10. Comments
10. 11. Unified Logons between Windows NT and UNIX using Winbind
10.1. 11.1. Abstract
10.2. 11.2. Introduction
10.3. 11.3. What Winbind Provides
10.3.1. 11.3.1. Target Uses
10.4. 11.4. How Winbind Works
10.4.1. 11.4.1. Microsoft Remote Procedure Calls
10.4.2. 11.4.2. Name Service Switch
10.4.3. 11.4.3. Pluggable Authentication Modules
10.4.4. 11.4.4. User and Group ID Allocation
10.4.5. 11.4.5. Result Caching
10.5. 11.5. Installation and Configuration
10.5.1. 11.5.1. Introduction
10.5.2. 11.5.2. Requirements
10.5.3. 11.5.3. Testing Things Out
10.5.3.1. 11.5.3.1. Configure and compile SAMBA
10.5.3.2. 11.5.3.2. Configure nsswitch.conf
10.5.3.3. 11.5.3.3. Configure smb.conf
10.5.3.4. 11.5.3.4. Join the SAMBA server to the PDC domain
10.5.3.5. 11.5.3.5. Start up the winbindd daemon and test it!
10.5.3.6. 11.5.3.6. Fix the /etc/rc.d/init.d/smb startup files
10.5.3.7. 11.5.3.7. Configure Winbind and PAM
10.6. 11.6. Limitations
10.7. 11.7. Conclusion
11. 12. OS2 Client HOWTO
11.1. 12.1. FAQs
11.1.1. 12.1.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?
11.1.2. 12.1.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?
11.1.3. 12.1.3. Are there any other issues when OS/2 (any version) is used as a client?
11.1.4. 12.1.4. How do I get printer driver download working for OS/2 clients?
12. 13. HOWTO Access Samba source code via CVS
12.1. 13.1. Introduction
12.2. 13.2. CVS Access to samba.org
12.2.1. 13.2.1. Access via CVSweb
12.2.2. 13.2.2. Access via cvs
Index
1.6. Step 5: Starting the smbd and nmbd

You must choose to start smbd and nmbd either +>You must choose to start smbd and nmbd either as daemons or from inetd. Don't try +>. Don't try to do both! Either you can put them in inetd.conf and have them started on demand +> and have them started on demand by inetd /etc/rc.local. See the man pages for details - on the command line options. Take particular care to read - the bit about what user you need to be in order to start +>. See the man pages for details + on the command line options. Take particular care to read + the bit about what user you need to be in order to start Samba. In many cases you must be root.

The main advantage of starting nmbd as a daemon is that they will - respond slightly more quickly to an initial connection - request. This is, however, unlikely to be a problem.

using the recommended daemon method + is that they will respond slightly more quickly to an initial connection + request.

Chapter 9. Storing Samba's User/Machine Account information in an LDAP DirectoryChapter 9. How to a Purely Samba Controlled Domain

9.1. Purpose9.1. Prerequisite Reading

Before you continue reading in this chapter, please make sure +that you are comfortable with configuring a Samba PDC +as described in the Samba-PDC-HOWTO.

9.2. Background

What is a Domain Controller? It is a machine that is able to answer +logon requests from workstations in a Windows NT Domain. Whenever a +user logs into a Windows NT Workstation, the workstation connects to a +Domain Controller and asks him whether the username and password the +user typed in is correct. The Domain Controller replies with a lot of +information about the user, for example the place where the users +profile is stored, the users full name of the user. All this +information is stored in the NT user database, the so-called SAM.

There are two kinds of Domain Controller in a NT 4 compatible Domain: +A Primary Domain Controller (PDC) and one or more Backup Domain +Controllers (BDC). The PDC contains the master copy of the +SAM. Whenever the SAM has to change, for example when a user changes +his password, this change has to be done on the PDC. A Backup Domain +Controller is a machine that maintains a read-only copy of the +SAM. This way it is able to reply to logon requests and authenticate +users in case the PDC is not available. During this time no changes to +the SAM are possible. Whenever changes to the SAM are done on the PDC, +all BDC receive the changes from the PDC.

Since version 2.2 Samba officially supports domain logons for all +current Windows Clients, including Windows 2000 and XP. This text +assumes the domain to be named SAMBA. To be able to act as a PDC, some +parameters in the [global]-section of the smb.conf have to be set:

workgroup = SAMBA
+domain master = yes
+domain logons = yes

Several other things like a [homes] and a [netlogon] share also may be +set along with settings for the profile path, the users home drive and +others. This will not be covered in this document.

9.3. What qualifies a Domain Controller on the network?

Every machine that is a Domain Controller for the domain SAMBA has to +register the NetBIOS group name SAMBA#1c with the WINS server and/or +by broadcast on the local network. The PDC also registers the unique +NetBIOS name SAMBA#1b with the WINS server. The name type #1b is +normally reserved for the domain master browser, a role that has +nothing to do with anything related to authentication, but the +Microsoft Domain implementation requires the domain master browser to +be on the same machine as the PDC.

9.3.1. How does a Workstation find its domain controller?

A NT workstation in the domain SAMBA that wants a local user to be +authenticated has to find the domain controller for SAMBA. It does +this by doing a NetBIOS name query for the group name SAMBA#1c. It +assumes that each of the machines it gets back from the queries is a +domain controller and can answer logon requests. To not open security +holes both the workstation and the selected (TODO: How is the DC +chosen) domain controller authenticate each other. After that the +workstation sends the user's credentials (his name and password) to +the domain controller, asking for approval.

9.3.2. When is the PDC needed?

Whenever a user wants to change his password, this has to be done on +the PDC. To find the PDC, the workstation does a NetBIOS name query +for SAMBA#1b, assuming this machine maintains the master copy of the +SAM. The workstation contacts the PDC, both mutually authenticate and +the password change is done.

9.4. Can Samba be a Backup Domain Controller?

With version 2.2, no. The native NT SAM replication protocols have +not yet been fully implemented. The Samba Team is working on +understanding and implementing the protocols, but this work has not +been finished for version 2.2.

Can I get the benefits of a BDC with Samba? Yes. The main reason for +implementing a BDC is availability. If the PDC is a Samba machine, +a second Samba machine can be set up to +service logon requests whenever the PDC is down.

9.5. How do I set up a Samba BDC?

Several things have to be done:

  • The file private/MACHINE.SID identifies the domain. When a samba +server is first started, it is created on the fly and must never be +changed again. This file has to be the same on the PDC and the BDC, +so the MACHINE.SID has to be copied from the PDC to the BDC.

  • The Unix user database has to be synchronized from the PDC to the +BDC. This means that both the /etc/passwd and /etc/group have to be +replicated from the PDC to the BDC. This can be done manually +whenever changes are made, or the PDC is set up as a NIS master +server and the BDC as a NIS slave server. To set up the BDC as a +mere NIS client would not be enough, as the BDC would not be able to +access its user database in case of a PDC failure.

  • The Samba password database in the file private/smbpasswd has to be +replicated from the PDC to the BDC. This is a bit tricky, see the +next section.

  • Any netlogon share has to be replicated from the PDC to the +BDC. This can be done manually whenever login scripts are changed, +or it can be done automatically together with the smbpasswd +synchronization.

Finally, the BDC has to be found by the workstations. This can be done +by setting

workgroup = samba
+domain master = no
+domain logons = yes

in the [global]-section of the smb.conf of the BDC. This makes the BDC +only register the name SAMBA#1c with the WINS server. This is no +problem as the name SAMBA#1c is a NetBIOS group name that is meant to +be registered by more than one machine. The parameter 'domain master = +no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS +name is reserved for the Primary Domain Controller.

9.5.1. How do I replicate the smbpasswd file?

Replication of the smbpasswd file is sensitive. It has to be done +whenever changes to the SAM are made. Every user's password change is +done in the smbpasswd file and has to be replicated to the BDC. So +replicating the smbpasswd file very often is necessary.

As the smbpasswd file contains plain text password equivalents, it +must not be sent unencrypted over the wire. The best way to set up +smbpasswd replication from the PDC to the BDC is to use the utility +rsync. rsync can use ssh as a transport. ssh itself can be set up to +accept *only* rsync transfer without requiring the user to type a +password.

Chapter 10. Storing Samba's User/Machine Account information in an LDAP Directory

10.1. Purpose

This document describes how to use an LDAP directory for storing Samba user -account information normally stored in the smbpasswd(5) file. It is +account information traditionally stored in the smbpasswd(5) file. It is assumed that the reader already has a basic understanding of LDAP concepts and has a working directory server already installed. For more information on LDAP architectures and Directories, please refer to the following sites.

It may also be helpful to supplement the reading of the HOWTO with -the Two additional Samba resources which may prove to be helpful are

  • The Samba-PDC-LDAP-HOWTO -maintained by Ignacio Coupeau.

  • The NT migration scripts from IDEALX that are + geared to manage users and group in such a Samba-LDAP Domain Controller configuration. +

9.2. Introduction10.2. Introduction

Traditionally, when configuring

As a result of these defeciencies, a more robust means of storing user attributes used by smbd was developed. The API which defines access to user accounts -is referred to as the samdb interface (previously this was called the passdb -API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support +is commonly referred to as the samdb interface (previously this was called the passdb +API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support for a samdb backend (e.g.

9.3. Supported LDAP Servers10.3. Supported LDAP Servers

The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP @@ -8078,8 +8423,8 @@ CLASS="SECT1" >

9.4. Schema and Relationship to the RFC 2307 posixAccount10.4. Schema and Relationship to the RFC 2307 posixAccount

Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in @@ -8104,7 +8449,7 @@ CLASS="PROGRAMLISTING" MAY ( cn $ lmPassword $ ntPassword $ pwdLastSet $ logonTime $ logoffTime $ kickoffTime $ pwdCanChange $ pwdMustChange $ acctFlags $ displayName $ smbHome $ homeDrive $ scriptPath $ profilePath $ - description $ userWorkstations $ primaryGroupID ))

10.5. Configuring Samba with LDAP

10.5.1. OpenLDAP configuration

To include support for the sambaAccount object in an OpenLDAP directory server, first copy the samba.schema file to slapd's configuration directory.

It is recommended that you maintain some indices on some of the most usefull attributes, +like in the following example, to speed up searches made on sambaAccount objectclasses +(and possibly posixAccount and posixGroup as well).

# Indices to maintain
+## required by OpenLDAP 2.0
+index objectclass   eq
+
+## support pb_getsampwnam()
+index uid           pres,eq
+## support pdb_getsambapwrid()
+index rid           eq
+
+## uncomment these if you are storing posixAccount and
+## posixGroup entries in the directory as well
+##index uidNumber     eq
+##index gidNumber     eq
+##index cn            eq
+##index memberUid     eq

9.5. smb.conf LDAP parameters

10.5.2. Configuring Samba

The following parameters are available in smb.conf only with ' to store the # passphrase in the secrets.tdb file. If the "ldap admin dn" values # changes, this password will need to be reset. - ldap admin dn = "cn=Manager,dc=samba,dc=org" + ldap admin dn = "cn=Samba Manager,ou=people,dc=samba,dc=org" # specify the LDAP server's hostname (defaults to locahost) ldap server = ahab.samba.org @@ -8328,13 +8722,39 @@ CLASS="REPLACEABLE" >

10.6. Accounts and Groups management

As users accounts are managed thru the sambaAccount objectclass, you should +modify you existing administration tools to deal with sambaAccount attributes.

Machines accounts are managed with the sambaAccount objectclass, just +like users accounts. However, it's up to you to stored thoses accounts +in a different tree of you LDAP namespace: you should use +"ou=Groups,dc=plainjoe,dc=org" to store groups and +"ou=People,dc=plainjoe,dc=org" to store users. Just configure your +NSS and PAM accordingly (usually, in the /etc/ldap.conf configuration +file).

In Samba release 2.2.3, the group management system is based on posix +groups. This meand that Samba make usage of the posixGroup objectclass. +For now, there is no NT-like group system management (global and local +groups).

9.6. Security and sambaAccount10.7. Security and sambaAccount

There are two important points to remember when discussing the security @@ -8359,7 +8779,12 @@ of sambaAccount entries in the directory.

These password hashes are clear text equivalents and can be used to impersonate -the user without deriving the original clear text strings.

ENCRYPTION chapter of the Samba-HOWTO-Collection.

To remedy the first security issue, the "ldap ssl" smb.conf parameter defaults to require an encrypted session (ldap ssl = off).

Note that the LDAPS protocol is deprecated in favor of the LDAPv3 StartTLS +extended operation. However, the OpenLDAP library still provides support for +the older method of securing communication between clients and servers.

The second security precaution is to prevent non-administrative users from harvesting password hashes from the directory. This can be done using the following ACL in 

## allow users to update their own password, but not to browse others
-access to attrs=userPassword,lmPassword,ntPassword
-     by self write
-     by * auth
## allow the "ldap admin dn" access, but deny everyone else +access to attrs=lmPassword,ntPassword + by dn="cn=Samba Admin,ou=people,dc=plainjoe,dc=org" write + by * none

You may of course, add in write access to administrative DN's as necessary.

9.7. 10.8. LDAP specials attributes for sambaAccounts

There are currently four sambaAccount attributes which map directly onto -smb.conf parameters.

The sambaAccount objectclass is composed of the following attributes:

  • smbHome -> "logon home"

    lmPassword: the LANMAN password 16-byte hash stored as a character + representation of a hexidecimal string.

  • ntPassword: the NT password hash 16-byte stored as a character + representation of a hexidecimal string.

  • pwdLastSet: The integer time in seconds since 1970 when the + lmPassword and ntPassword attributes were last set. +

  • acctFlags: string of 11 characters surrounded by square brackets [] + representing account flags such as U (user), W(workstation), X(no password expiration), and + D(disabled).

  • logonTime: Integer value currently unused

  • logoffTime: Integer value currently unused

  • kickoffTime: Integer value currently unused

  • pwdCanChange: Integer value currently unused

  • pwdMustChange: Integer value currently unused

  • homeDrive: specifies the drive letter to which to map the + UNC path specified by homeDirectory. The drive letter must be specified in the form "X:" + where X is the letter of the drive to map. Refer to the "logon drive" parameter in the + smb.conf(5) man page for more information.

  • scriptPath: The scriptPath property specifies the path of + the user's logon script, .CMD, .EXE, or .BAT file. The string can be null. The path + is relative to the netlogon share. Refer to the "logon script" parameter in the + smb.conf(5) man page for more information.

  • profilePath: specifies a path to the user's profile. + This value can be a null string, a local absolute path, or a UNC path. Refer to the + "logon path" parameter in the smb.conf(5) man page for more information.

  • smbHome: The homeDirectory property specifies the path of + the home directory for the user. The string can be null. If homeDrive is set and specifies + a drive letter, homeDirectory should be a UNC path. The path must be a network + UNC path of the form \\server\share\directory. This value can be a null string. + Refer to the "logon home" parameter in the smb.conf(5) man page for more information. +

  • profilePath -> "logon path"

    userWorkstation: character string value currently unused. +

  • homeDrive -> "logon drive"

    rid: the integer representation of the user's relative identifier + (RID).

  • scriptPath -> "logon script"

    primaryGroupID: the relative identifier (RID) of the primary group + of the user.

First of all, these parameters are only used when Samba is acting as a -PDC or a domain (refer to the The majority of these parameters are only used when Samba is acting as a PDC of +a domain (refer to the Samba-PDC-HOWTO -for details on how to configure Samba as a Primary Domain Controller). -Furthermore, these attributes are only stored with the sambaAccount entry if +> for details on +how to configure Samba as a Primary Domain Controller). The following four attributes +are only stored with the sambaAccount entry if the values are non-default values:

  • smbHome

  • scriptPath

  • logonPath

  • homeDrive

These attributes are only stored with the sambaAccount entry if the values are non-default values. For example, assume TASHTEGO has now been configured as a PDC and that logon home string is expanded to \\TASHTEGO\becky.

If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", +> string is expanded to \\TASHTEGO\becky. +If the smbHome attribute exists in the entry "uid=becky,ou=people,dc=samba,dc=org", this value is used. However, if this attribute does not exist, then the value of the

9.8. Example LDIF Entries for a sambaAccount10.9. Example LDIF Entries for a sambaAccount

The following is a working LDIF with the inclusion of the posixAccount objectclass:

9.9. Comments10.10. Comments

Please mail all comments regarding this HOWTO to

Chapter 10. Unified Logons between Windows NT and UNIX using WinbindChapter 11. Unified Logons between Windows NT and UNIX using Winbind

10.1. Abstract11.1. Abstract

Integration of UNIX and Microsoft Windows NT through @@ -8599,8 +9167,8 @@ CLASS="SECT1" >

10.2. Introduction11.2. Introduction

It is well known that UNIX and Microsoft Windows NT have @@ -8653,8 +9221,8 @@ CLASS="SECT1" >

10.3. What Winbind Provides11.3. What Winbind Provides

Winbind unifies UNIX and Windows NT account management by @@ -8695,8 +9263,8 @@ CLASS="SECT2" >

10.3.1. Target Uses11.3.1. Target Uses

Winbind is targeted at organizations that have an @@ -8719,8 +9287,8 @@ CLASS="SECT1" >

10.4. How Winbind Works11.4. How Winbind Works

The winbind system is designed around a client/server @@ -8739,8 +9307,8 @@ CLASS="SECT2" >

10.4.1. Microsoft Remote Procedure Calls11.4.1. Microsoft Remote Procedure Calls

Over the last two years, efforts have been underway @@ -8765,8 +9333,8 @@ CLASS="SECT2" >

10.4.2. Name Service Switch11.4.2. Name Service Switch

The Name Service Switch, or NSS, is a feature that is @@ -8845,8 +9413,8 @@ CLASS="SECT2" >

10.4.3. Pluggable Authentication Modules11.4.3. Pluggable Authentication Modules

Pluggable Authentication Modules, also known as PAM, @@ -8894,8 +9462,8 @@ CLASS="SECT2" >

10.4.4. User and Group ID Allocation11.4.4. User and Group ID Allocation

When a user or group is created under Windows NT @@ -8920,8 +9488,8 @@ CLASS="SECT2" >

10.4.5. Result Caching11.4.5. Result Caching

An active system can generate a lot of user and group @@ -8943,8 +9511,8 @@ CLASS="SECT1" >

10.5. Installation and Configuration11.5. Installation and Configuration

Many thanks to John Trostel

10.5.1. Introduction11.5.1. Introduction

This HOWTO describes the procedures used to get winbind up and @@ -9013,8 +9581,8 @@ CLASS="SECT2" >

10.5.2. Requirements11.5.2. Requirements

If you have a samba configuration file that you are currently @@ -9071,8 +9639,8 @@ CLASS="SECT2" >

10.5.3. Testing Things Out11.5.3. Testing Things Out

Before starting, it is probably best to kill off all the SAMBA @@ -9116,8 +9684,8 @@ CLASS="SECT3" >

10.5.3.1. Configure and compile SAMBA11.5.3.1. Configure and compile SAMBA

The configuration and compilation of SAMBA is pretty straightforward. @@ -9191,8 +9759,8 @@ CLASS="SECT3" >

10.5.3.2. Configure 11.5.3.2. Configure nsswitch.conf and the @@ -9281,8 +9849,8 @@ CLASS="SECT3" >

10.5.3.3. Configure smb.conf11.5.3.3. Configure smb.conf

Several parameters are needed in the smb.conf file to control @@ -9365,8 +9933,8 @@ CLASS="SECT3" >

10.5.3.4. Join the SAMBA server to the PDC domain11.5.3.4. Join the SAMBA server to the PDC domain

Enter the following command to make the SAMBA server join the @@ -9411,8 +9979,8 @@ CLASS="SECT3" >

10.5.3.5. Start up the winbindd daemon and test it!11.5.3.5. Start up the winbindd daemon and test it!

Eventually, you will want to modify your smb startup script to @@ -9481,7 +10049,7 @@ CEO+TsInternetUserObviously, I have named my domain 'CEO' and my winbindd +>winbind separator is '+'.

10.5.3.6. Fix the 11.5.3.6. Fix the /etc/rc.d/init.d/smb startup files

10.5.3.7. Configure Winbind and PAM11.5.3.7. Configure Winbind and PAM

If you have made it this far, you know that winbindd and samba are working @@ -9904,8 +10472,8 @@ CLASS="SECT1" >

10.6. Limitations11.6. Limitations

Winbind has a number of limitations in its current @@ -9945,8 +10513,8 @@ CLASS="SECT1" >

10.7. Conclusion11.7. Conclusion

The winbind system, through the use of the Name Service @@ -9962,23 +10530,23 @@ CLASS="CHAPTER" >

Chapter 11. OS2 Client HOWTOChapter 12. OS2 Client HOWTO

11.1. FAQs12.1. FAQs

11.1.1. How can I configure OS/2 Warp Connect or +NAME="AEN2258" +>12.1.1. How can I configure OS/2 Warp Connect or OS/2 Warp 4 as a client for Samba?

11.1.2. How can I configure OS/2 Warp 3 (not Connect), +NAME="AEN2273" +>12.1.2. How can I configure OS/2 Warp 3 (not Connect), OS/2 1.2, 1.3 or 2.x for Samba?

11.1.3. Are there any other issues when OS/2 (any version) +NAME="AEN2282" +>12.1.3. Are there any other issues when OS/2 (any version) is used as a client?

11.1.4. How do I get printer driver download working +NAME="AEN2286" +>12.1.4. How do I get printer driver download working for OS/2 clients?

Chapter 12. HOWTO Access Samba source code via CVSChapter 13. HOWTO Access Samba source code via CVS

12.1. Introduction13.1. Introduction

Samba is developed in an open environment. Developers use CVS @@ -10189,8 +10757,8 @@ CLASS="SECT1" >

12.2. CVS Access to samba.org13.2. CVS Access to samba.org

The machine samba.org runs a publicly accessible CVS @@ -10202,8 +10770,8 @@ CLASS="SECT2" >

12.2.1. Access via CVSweb13.2.1. Access via CVSweb

You can access the source code via your @@ -10223,8 +10791,8 @@ CLASS="SECT2" >

12.2.2. Access via cvs13.2.2. Access via cvs

You can also access the source code via a @@ -10329,7 +10897,7 @@ CLASS="COMMAND" >

Index

As a result of these defeciencies, a more robust means of storing user attributes used by smbd was developed. The API which defines access to user accounts is commonly referred to as the samdb interface (previously this was called the passdb -API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support +API, and is still so named in the CVS trees). In Samba 2.2.3, enabling support for a samdb backend (e.g. Step 5: Starting the smbd and nmbd

You must choose to start smbd and nmbd either +>You must choose to start smbd and nmbd either as daemons or from inetd. Don't try +>. Don't try to do both! Either you can put them in inetd.conf and have them started on demand +> and have them started on demand by inetd /etc/rc.local. See the man pages for details - on the command line options. Take particular care to read - the bit about what user you need to be in order to start +>. See the man pages for details + on the command line options. Take particular care to read + the bit about what user you need to be in order to start Samba. In many cases you must be root.

The main advantage of starting nmbd as a daemon is that they will - respond slightly more quickly to an initial connection - request. This is, however, unlikely to be a problem.

using the recommended daemon method + is that they will respond slightly more quickly to an initial connection + request.

smb.conf(5) man page.

This command can work both with and without the -U parameter.

When invoked with -U, that username (and optional password) are + used to contact the PDC (which must be specified with -r) to both + create a machine account, and to set a password on it.

Alternately, if -U is omitted, Samba will contact its PDC + and attempt to change the password on a pre-existing account.

In order to be used in this way, the Administrator for the Windows NT Domain must have used the program "Server Manager for Domains" to add the primary NetBIOS name of the Samba server @@ -445,9 +454,10 @@ CLASS="PARAMETER" >password server and change the machine account - password used to create the secure Domain communication. This - password is then stored by smbpasswd in a TDB, writeable only by root, - called

Either way, this password is then stored by smbpasswd in a TDB, + writeable only by root, called secrets.tdb

Note that even though the authentication is being done to the PDC all users accessing the Samba server must still - have a valid UNIX account on that machine.

winbindd(8) daemon can be used + to create UNIX accounts for NT users.

This option is only available when running smbpasswd as root.

In particular, this parameter specifies the username + used to create the machine account when invoked with -j

-h

This parameter is only available is Samba - has been configured to use the experiemental + has been configured to use the experimental --with-ldapsam

NOTES

VERSION

SEE ALSO

AUTHOR

Obviously, I have named my domain 'CEO' and my winbindd +>winbind separator is '+'.