source: vendor/3.6.23/docs/manpages/winbindd.8

Last change on this file was 860, checked in by Silvan Scherrer, 11 years ago

Samba 3.6: updated vendor to latest version

File size: 15.6 KB
Line 
1'\" t
2.\" Title: winbindd
3.\" Author: [see the "AUTHOR" section]
4.\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
5.\" Date: 09/18/2013
6.\" Manual: System Administration tools
7.\" Source: Samba 3.6
8.\" Language: English
9.\"
10.TH "WINBINDD" "8" "09/18/2013" "Samba 3\&.6" "System Administration tools"
11.\" -----------------------------------------------------------------
12.\" * Define some portability stuff
13.\" -----------------------------------------------------------------
14.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
15.\" http://bugs.debian.org/507673
16.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
17.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
18.ie \n(.g .ds Aq \(aq
19.el .ds Aq '
20.\" -----------------------------------------------------------------
21.\" * set default formatting
22.\" -----------------------------------------------------------------
23.\" disable hyphenation
24.nh
25.\" disable justification (adjust text to left margin only)
26.ad l
27.\" -----------------------------------------------------------------
28.\" * MAIN CONTENT STARTS HERE *
29.\" -----------------------------------------------------------------
30.SH "NAME"
31winbindd \- Name Service Switch daemon for resolving names from NT servers
32.SH "SYNOPSIS"
33.HP \w'\ 'u
34winbindd [\-D] [\-F] [\-S] [\-i] [\-d\ <debug\ level>] [\-s\ <smb\ config\ file>] [\-n]
35.SH "DESCRIPTION"
36.PP
37This program is part of the
38\fBsamba\fR(7)
39suite\&.
40.PP
41winbindd
42is a daemon that provides a number of services to the Name Service Switch capability found in most modern C libraries, to arbitrary applications via PAM and
43ntlm_auth
44and to Samba itself\&.
45.PP
46Even if winbind is not used for nsswitch, it still provides a service to
47smbd,
48ntlm_auth
49and the
50pam_winbind\&.so
51PAM module, by managing connections to domain controllers\&. In this configuration the
52\m[blue]\fBidmap config * : range\fR\m[]
53parameter is not required\&. (This is known as `netlogon proxy only mode\*(Aq\&.)
54.PP
55The 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 through the
56/etc/nsswitch\&.conf
57file\&. 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\&.
58.PP
59The service provided by
60winbindd
61is called `winbind\*(Aq 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\&.
62.PP
63The
64pam_winbind
65module supports the
66\fIauth\fR,
67\fIaccount\fR
68and
69\fIpassword\fR
70module\-types\&. It should be noted that the
71\fIaccount\fR
72module 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
73libnss_winbind
74library has been correctly installed, or an alternate source of names configured, this should always succeed\&.
75.PP
76The following nsswitch databases are implemented by the winbindd service:
77.PP
78hosts
79.RS 4
80This feature is only available on IRIX\&. User information traditionally stored in the
81hosts(5)
82file and used by
83gethostbyname(3)
84functions\&. Names are resolved through the WINS server or by broadcast\&.
85.RE
86.PP
87passwd
88.RS 4
89User information traditionally stored in the
90passwd(5)
91file and used by
92getpwent(3)
93functions\&.
94.RE
95.PP
96group
97.RS 4
98Group information traditionally stored in the
99group(5)
100file and used by
101getgrent(3)
102functions\&.
103.RE
104.PP
105For example, the following simple configuration in the
106/etc/nsswitch\&.conf
107file can be used to initially resolve user and group information from
108/etc/passwd
109and
110/etc/group
111and then from the Windows NT server\&.
112.sp
113.if n \{\
114.RS 4
115.\}
116.nf
117passwd: files winbind
118group: files winbind
119## only available on IRIX: use winbind to resolve hosts:
120# hosts: files dns winbind
121## All other NSS enabled systems should use libnss_wins\&.so like this:
122hosts: files dns wins
123
124.fi
125.if n \{\
126.RE
127.\}
128.PP
129The following simple configuration in the
130/etc/nsswitch\&.conf
131file can be used to initially resolve hostnames from
132/etc/hosts
133and then from the WINS server\&.
134.sp
135.if n \{\
136.RS 4
137.\}
138.nf
139hosts: files wins
140.fi
141.if n \{\
142.RE
143.\}
144.SH "OPTIONS"
145.PP
146\-D
147.RS 4
148If specified, this parameter causes the server to operate as a daemon\&. That is, it detaches itself and runs in the background on the appropriate port\&. This switch is assumed if
149winbindd
150is executed on the command line of a shell\&.
151.RE
152.PP
153\-F
154.RS 4
155If specified, this parameter causes the main
156winbindd
157process 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
158winbindd
159under process supervisors such as
160supervise
161and
162svscan
163from Daniel J\&. Bernstein\*(Aqs
164daemontools
165package, or the AIX process monitor\&.
166.RE
167.PP
168\-S
169.RS 4
170If specified, this parameter causes
171winbindd
172to log to standard output rather than a file\&.
173.RE
174.PP
175\-d|\-\-debuglevel=level
176.RS 4
177\fIlevel\fR
178is an integer from 0 to 10\&. The default value if this parameter is not specified is 0\&.
179.sp
180The 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\&.
181.sp
182Levels 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\&.
183.sp
184Note that specifying this parameter here will override the
185\m[blue]\fBlog level\fR\m[]
186parameter in the
187smb\&.conf
188file\&.
189.RE
190.PP
191\-V|\-\-version
192.RS 4
193Prints the program version number\&.
194.RE
195.PP
196\-s|\-\-configfile <configuration file>
197.RS 4
198The 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
199smb\&.conf
200for more information\&. The default configuration file name is determined at compile time\&.
201.RE
202.PP
203\-l|\-\-log\-basename=logdirectory
204.RS 4
205Base directory name for log/debug files\&. The extension
206\fB"\&.progname"\fR
207will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
208.RE
209.PP
210\-h|\-\-help
211.RS 4
212Print a summary of command line options\&.
213.RE
214.PP
215\-i
216.RS 4
217Tells
218winbindd
219to not become a daemon and detach from the current terminal\&. This option is used by developers when interactive debugging of
220winbindd
221is required\&.
222winbindd
223also logs to standard output, as if the
224\-S
225parameter had been given\&.
226.RE
227.PP
228\-n
229.RS 4
230Disable 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\*(Aqt respond\&.
231.RE
232.SH "NAME AND ID RESOLUTION"
233.PP
234Users 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
235winbindd
236performs\&.
237.PP
238As 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 and will be remembered\&.
239.PP
240WARNING: The SID to unix id database is the only location where the user and group mappings are stored by winbindd\&. If this store 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\&.
241.SH "CONFIGURATION"
242.PP
243Configuration of the
244winbindd
245daemon is done through configuration parameters in the
246\fBsmb.conf\fR(5)
247file\&. All parameters should be specified in the [global] section of smb\&.conf\&.
248.sp
249.RS 4
250.ie n \{\
251\h'-04'\(bu\h'+03'\c
252.\}
253.el \{\
254.sp -1
255.IP \(bu 2.3
256.\}
257
258\m[blue]\fBwinbind separator\fR\m[]
259.RE
260.sp
261.RS 4
262.ie n \{\
263\h'-04'\(bu\h'+03'\c
264.\}
265.el \{\
266.sp -1
267.IP \(bu 2.3
268.\}
269
270\m[blue]\fBidmap config * : range\fR\m[]
271.RE
272.sp
273.RS 4
274.ie n \{\
275\h'-04'\(bu\h'+03'\c
276.\}
277.el \{\
278.sp -1
279.IP \(bu 2.3
280.\}
281
282\m[blue]\fBidmap config * : backend\fR\m[]
283.RE
284.sp
285.RS 4
286.ie n \{\
287\h'-04'\(bu\h'+03'\c
288.\}
289.el \{\
290.sp -1
291.IP \(bu 2.3
292.\}
293
294\m[blue]\fBwinbind cache time\fR\m[]
295.RE
296.sp
297.RS 4
298.ie n \{\
299\h'-04'\(bu\h'+03'\c
300.\}
301.el \{\
302.sp -1
303.IP \(bu 2.3
304.\}
305
306\m[blue]\fBwinbind enum users\fR\m[]
307.RE
308.sp
309.RS 4
310.ie n \{\
311\h'-04'\(bu\h'+03'\c
312.\}
313.el \{\
314.sp -1
315.IP \(bu 2.3
316.\}
317
318\m[blue]\fBwinbind enum groups\fR\m[]
319.RE
320.sp
321.RS 4
322.ie n \{\
323\h'-04'\(bu\h'+03'\c
324.\}
325.el \{\
326.sp -1
327.IP \(bu 2.3
328.\}
329
330\m[blue]\fBtemplate homedir\fR\m[]
331.RE
332.sp
333.RS 4
334.ie n \{\
335\h'-04'\(bu\h'+03'\c
336.\}
337.el \{\
338.sp -1
339.IP \(bu 2.3
340.\}
341
342\m[blue]\fBtemplate shell\fR\m[]
343.RE
344.sp
345.RS 4
346.ie n \{\
347\h'-04'\(bu\h'+03'\c
348.\}
349.el \{\
350.sp -1
351.IP \(bu 2.3
352.\}
353
354\m[blue]\fBwinbind use default domain\fR\m[]
355.RE
356.sp
357.RS 4
358.ie n \{\
359\h'-04'\(bu\h'+03'\c
360.\}
361.el \{\
362.sp -1
363.IP \(bu 2.3
364.\}
365
366\m[blue]\fBwinbind: rpc only\fR\m[]
367Setting this parameter forces winbindd to use RPC instead of LDAP to retrieve information from Domain Controllers\&.
368.RE
369.SH "EXAMPLE SETUP"
370.PP
371To 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\&.
372.PP
373In
374/etc/nsswitch\&.conf
375put the following:
376.sp
377.if n \{\
378.RS 4
379.\}
380.nf
381passwd: files winbind
382group: files winbind
383.fi
384.if n \{\
385.RE
386.\}
387.PP
388In
389/etc/pam\&.d/*
390replace the
391\fI auth\fR
392lines with something like this:
393.sp
394.if n \{\
395.RS 4
396.\}
397.nf
398auth required /lib/security/pam_securetty\&.so
399auth required /lib/security/pam_nologin\&.so
400auth sufficient /lib/security/pam_winbind\&.so
401auth required /lib/security/pam_unix\&.so \e
402 use_first_pass shadow nullok
403.fi
404.if n \{\
405.RE
406.\}
407.sp
408.if n \{\
409.sp
410.\}
411.RS 4
412.it 1 an-trap
413.nr an-no-space-flag 1
414.nr an-break-flag 1
415.br
416.ps +1
417\fBNote\fR
418.ps -1
419.br
420.PP
421The PAM module pam_unix has recently replaced the module pam_pwdb\&. Some Linux systems use the module pam_unix2 in place of pam_unix\&.
422.sp .5v
423.RE
424.PP
425Note in particular the use of the
426\fIsufficient \fR
427keyword and the
428\fIuse_first_pass\fR
429keyword\&.
430.PP
431Now replace the account lines with this:
432.PP
433account required /lib/security/pam_winbind\&.so
434.PP
435The next step is to join the domain\&. To do that use the
436net
437program like this:
438.PP
439net join \-S PDC \-U Administrator
440.PP
441The username after the
442\fI\-U\fR
443can be any Domain user that has administrator privileges on the machine\&. Substitute the name or IP of your PDC for "PDC"\&.
444.PP
445Next copy
446libnss_winbind\&.so
447to
448/lib
449and
450pam_winbind\&.so
451to
452/lib/security\&. A symbolic link needs to be made from
453/lib/libnss_winbind\&.so
454to
455/lib/libnss_winbind\&.so\&.2\&. If you are using an older version of glibc then the target of the link should be
456/lib/libnss_winbind\&.so\&.1\&.
457.PP
458Finally, setup a
459\fBsmb.conf\fR(5)
460containing directives like the following:
461.sp
462.if n \{\
463.RS 4
464.\}
465.nf
466[global]
467 winbind separator = +
468 winbind cache time = 10
469 template shell = /bin/bash
470 template homedir = /home/%D/%U
471 idmap config * : range = 10000\-20000
472 workgroup = DOMAIN
473 security = domain
474 password server = *
475.fi
476.if n \{\
477.RE
478.\}
479.PP
480Now 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
481getent passwd
482and
483getent group
484to confirm the correct operation of winbindd\&.
485.SH "NOTES"
486.PP
487The following notes are useful when configuring and running
488winbindd:
489.PP
490\fBnmbd\fR(8)
491must be running on the local machine for
492winbindd
493to work\&.
494.PP
495PAM 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\&.
496.PP
497If more than one UNIX machine is running
498winbindd, 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
499\m[blue]\fBidmap config * : backend\fR\m[]
500is configured\&.
501.PP
502If the the Windows NT SID to UNIX user and group id mapping file is damaged or destroyed then the mappings will be lost\&.
503.SH "SIGNALS"
504.PP
505The following signals can be used to manipulate the
506winbindd
507daemon\&.
508.PP
509SIGHUP
510.RS 4
511Reload the
512\fBsmb.conf\fR(5)
513file 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\&.
514.RE
515.PP
516SIGUSR2
517.RS 4
518The SIGUSR2 signal will cause
519winbindd
520to write status information to the winbind log file\&.
521.sp
522Log files are stored in the filename specified by the log file parameter\&.
523.RE
524.SH "FILES"
525.PP
526/etc/nsswitch\&.conf(5)
527.RS 4
528Name service switch configuration file\&.
529.RE
530.PP
531/tmp/\&.winbindd/pipe
532.RS 4
533The UNIX pipe over which clients communicate with the
534winbindd
535program\&. For security reasons, the winbind client will only attempt to connect to the winbindd daemon if both the
536/tmp/\&.winbindd
537directory and
538/tmp/\&.winbindd/pipe
539file are owned by root\&.
540.RE
541.PP
542$LOCKDIR/winbindd_privileged/pipe
543.RS 4
544The UNIX pipe over which \*(Aqprivileged\*(Aq clients communicate with the
545winbindd
546program\&. For security reasons, access to some winbindd functions \- like those needed by the
547ntlm_auth
548utility \- is restricted\&. By default, only users in the \*(Aqroot\*(Aq group will get this access, however the administrator may change the group permissions on $LOCKDIR/winbindd_privileged to allow programs like \*(Aqsquid\*(Aq to use ntlm_auth\&. Note that the winbind client will only attempt to connect to the winbindd daemon if both the
549$LOCKDIR/winbindd_privileged
550directory and
551$LOCKDIR/winbindd_privileged/pipe
552file are owned by root\&.
553.RE
554.PP
555/lib/libnss_winbind\&.so\&.X
556.RS 4
557Implementation of name service switch library\&.
558.RE
559.PP
560$LOCKDIR/winbindd_idmap\&.tdb
561.RS 4
562Storage for the Windows NT rid to UNIX user/group id mapping\&. The lock directory is specified when Samba is initially compiled using the
563\fI\-\-with\-lockdir\fR
564option\&. This directory is by default
565/usr/local/samba/var/locks\&.
566.RE
567.PP
568$LOCKDIR/winbindd_cache\&.tdb
569.RS 4
570Storage for cached user and group information\&.
571.RE
572.SH "VERSION"
573.PP
574This man page is correct for version 3 of the Samba suite\&.
575.SH "SEE ALSO"
576.PP
577nsswitch\&.conf(5),
578\fBsamba\fR(7),
579\fBwbinfo\fR(1),
580\fBntlm_auth\fR(8),
581\fBsmb.conf\fR(5),
582\fBpam_winbind\fR(8)
583.SH "AUTHOR"
584.PP
585The 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\&.
586.PP
587wbinfo
588and
589winbindd
590were written by Tim Potter\&.
591.PP
592The 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\&.
Note: See TracBrowser for help on using the repository browser.