1 .\"Generated by db2man.xsl. Don't modify this, modify the source.
10 .de Sp \" Vertical space (when we can't use .PP)
16 .ie \\n(.$>=3 .ne \\$3
20 .TH "WINBINDD" 8 "" "" ""
22 winbindd - Name Service Switch daemon for resolving names from NT servers
25 \fBwinbindd\fR [-F] [-S] [-i] [-Y] [-d <debug level>] [-s <smb config file>] [-n]
28 This program is part of the
33 is a daemon that provides a number of services to the Name Service Switch capability found in most modern C libraries, to arbitary applications via PAM and
37 Even if winbind is not used for nsswitch, it still provides a service to
42 PAM module, by managing connections to domain controllers. In this configuraiton the
44 idmap gid parameters are not required. (This is known as `netlogon proxy only mode'.)
46 The Name Service Switch allows user and system information to be obtained from different databases services such as NIS or DNS. The exact behaviour can be configured throught the
47 \fI/etc/nsswitch.conf\fR
48 file. Users and groups are allocated as they are resolved to a range of user and group ids specified by the administrator of the Samba system.
50 The service provided by
52 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.
61 module-types. It should be noted that the
63 module simply performs a getpwnam() to verify that the system can obtain a uid for the user, as the domain controller has already performed access control. If the
65 library has been correctly installed, or an alternate source of names configured, this should always succeed.
67 The following nsswitch databases are implemented by the winbindd service:
70 This feature is only available on IRIX. User information traditionally stored in the
73 \fBgethostbyname(3)\fR
74 functions. Names are resolved through the WINS server or by broadcast.
77 User information traditionally stored in the
84 Group information traditionally stored in the
90 For example, the following simple configuration in the
91 \fI/etc/nsswitch.conf\fR
92 file can be used to initially resolve user and group information from
96 and then from the Windows NT server.
101 passwd: files winbind
103 ## only available on IRIX; Linux users should us libnss_wins.so
104 hosts: files dns winbind
108 The following simple configuration in the
109 \fI/etc/nsswitch.conf\fR
110 file can be used to initially resolve hostnames from
112 and then from the WINS server.
120 If specified, this parameter causes the main
122 process to not daemonize, i.e. double-fork and disassociate with the terminal. Child processes are still created as normal to service each connection request, but the main process does not exit. This operation mode is suitable for running
124 under process supervisors such as
128 from Daniel J. Bernstein's
130 package, or the AIX process monitor.
133 If specified, this parameter causes
135 to log to standard output rather than a file.
138 Prints the program version number.
140 -s <configuration file>
141 The file specified contains the configuration details required by the server. 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. See
143 for more information. The default configuration file name is determined at compile time.
145 -d|--debuglevel=level
147 is an integer from 0 to 10. The default value if this parameter is not specified is zero.
149 The higher this value, the more detail will be logged to the log files about the activities of the server. At level 0, only critical errors and serious warnings will be logged. Level 1 is a reasonable level for day-to-day running - it generates a small amount of information about operations carried out.
151 Levels above 1 will generate considerable amounts of log 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.
153 Note that specifying this parameter here will override the
159 -l|--logfile=logdirectory
160 Base directory name for log/debug files. The extension
162 will be appended (e.g. log.smbclient, log.smbd, etc...). The log file is never removed by the client.
165 Print a summary of command line options.
170 to not become a daemon and detach from the current terminal. This option is used by developers when interactive debugging of
174 also logs to standard output, as if the
176 parameter had been given.
179 Disable caching. This means winbindd will always have to wait for a response from the domain controller before it can respond to a client and this thus makes things slower. The results will however be more accurate, since results from the cache might not be up-to-date. This might also temporarily hang winbindd if the DC doesn't respond.
182 Single daemon mode. This means winbindd will run as a single process (the mode of operation in Samba 2.2). Winbindd's default behavior is to launch a child process that is responsible for updating expired cache entries.
183 .SH "NAME AND ID RESOLUTION"
185 Users and groups on a Windows NT server are assigned a security id (SID) which is globally unique when the user or group is created. To convert the Windows NT user or group into a unix user or group, a mapping between SIDs and unix user and group ids is required. This is one of the jobs that
189 As winbindd users and groups are resolved from a server, user and group ids are allocated from a specified range. This is done on a first come, first served basis, although all existing users and groups will be mapped as soon as a client performs a user or group enumeration command. The allocated unix ids are stored in a database file under the Samba lock directory and will be remembered.
191 WARNING: The SID to unix id database is the only location where the user and group mappings are stored by winbindd. If this file is deleted or corrupted, there is no way for winbindd to determine which user and group ids correspond to Windows NT user and group rids.
197 for options for sharing this database, such as via LDAP.
202 daemon is done through configuration parameters in the
204 file. All parameters should be specified in the [global] section of smb.conf.
244 winbind use default domain
247 To setup winbindd for user and group lookups plus authentication from a domain controller use something like the following setup. This was tested on an early Red Hat Linux box.
250 \fI/etc/nsswitch.conf\fR
256 passwd: files winbind
265 lines with something like this:
270 auth required /lib/security/pam_securetty.so
271 auth required /lib/security/pam_nologin.so
272 auth sufficient /lib/security/pam_winbind.so
273 auth required /lib/security/pam_unix.so \
274 use_first_pass shadow nullok
279 .nr an-no-space-flag 1
284 The PAM module pam_unix has recently replaced the module pam_pwdb. Some Linux systems use the module pam_unix2 in place of pam_unix.
286 Note in particular the use of the
292 Now replace the account lines with this:
294 \fBaccount required /lib/security/pam_winbind.so \fR
296 The next step is to join the domain. To do that use the
300 \fBnet join -S PDC -U Administrator\fR
302 The username after the
304 can be any Domain user that has administrator privileges on the machine. Substitute the name or IP of your PDC for "PDC".
307 \fIlibnss_winbind.so\fR
311 \fIpam_winbind.so \fR
313 \fI/lib/security\fR. A symbolic link needs to be made from
314 \fI/lib/libnss_winbind.so\fR
316 \fI/lib/libnss_winbind.so.2\fR. If you are using an older version of glibc then the target of the link should be
317 \fI/lib/libnss_winbind.so.1\fR.
321 containing directives like the following:
327 winbind separator = +
328 winbind cache time = 10
329 template shell = /bin/bash
330 template homedir = /home/%D/%U
331 idmap uid = 10000-20000
332 idmap gid = 10000-20000
339 Now start winbindd and you should find that your user and group database is expanded to include your NT users and groups, and that you can login to your unix box as a domain user, using the DOMAIN+user syntax for the username. You may wish to use the commands
343 to confirm the correct operation of winbindd.
346 The following notes are useful when configuring and running
350 must be running on the local machine for
354 PAM is really easy to misconfigure. Make sure you know what you are doing when modifying PAM configuration files. It is possible to set up PAM such that you can no longer log into your system.
356 If more than one UNIX machine is running
357 \fBwinbindd\fR, then in general the user and groups ids allocated by winbindd will not be the same. The user and group ids will only be valid for the local machine, unless a shared
361 If the the Windows NT SID to UNIX user and group id mapping file is damaged or destroyed then the mappings will be lost.
364 The following signals can be used to manipulate the
371 file and apply any parameter changes to the running version of winbindd. This signal also clears any cached user and group information. The list of other domains trusted by winbindd is also reloaded.
374 The SIGUSR2 signal will cause
376 to write status information to the winbind log file.
378 Log files are stored in the filename specified by the log file parameter.
381 \fI/etc/nsswitch.conf(5)\fR
382 Name service switch configuration file.
385 The UNIX pipe over which clients communicate with the
387 program. For security reasons, the winbind client will only attempt to connect to the winbindd daemon if both the
390 \fI/tmp/.winbindd/pipe\fR
391 file are owned by root.
393 $LOCKDIR/winbindd_privileged/pipe
394 The UNIX pipe over which 'privileged' clients communicate with the
396 program. For security reasons, access to some winbindd functions - like those needed by the
398 utility - is restricted. By default, only users in the 'root' group will get this access, however the administrator may change the group permissions on $LOCKDIR/winbindd_privileged to allow programs like 'squid' to use ntlm_auth. Note that the winbind client will only attempt to connect to the winbindd daemon if both the
399 \fI$LOCKDIR/winbindd_privileged\fR
401 \fI$LOCKDIR/winbindd_privileged/pipe\fR
402 file are owned by root.
404 /lib/libnss_winbind.so.X
405 Implementation of name service switch library.
407 $LOCKDIR/winbindd_idmap.tdb
408 Storage for the Windows NT rid to UNIX user/group id mapping. The lock directory is specified when Samba is initially compiled using the
410 option. This directory is by default
411 \fI/usr/local/samba/var/locks \fR.
413 $LOCKDIR/winbindd_cache.tdb
414 Storage for cached user and group information.
417 This man page is correct for version 3.0 of the Samba suite.
420 \fInsswitch.conf(5)\fR,
428 The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed.
433 were written by Tim Potter.
435 The conversion to DocBook for Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.