source: vendor/current/docs/manpages/ntlm_auth.1@ 988

Last change on this file since 988 was 988, checked in by Silvan Scherrer, 9 years ago

Samba Server: update vendor to version 4.4.3

File size: 10.7 KB
Line 
1'\" t
2.\" Title: ntlm_auth
3.\" Author: [see the "AUTHOR" section]
4.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
5.\" Date: 05/02/2016
6.\" Manual: User Commands
7.\" Source: Samba 4.4
8.\" Language: English
9.\"
10.TH "NTLM_AUTH" "1" "05/02/2016" "Samba 4\&.4" "User Commands"
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"
31ntlm_auth \- tool to allow external access to Winbind\*(Aqs NTLM authentication function
32.SH "SYNOPSIS"
33.HP \w'\ 'u
34ntlm_auth
35.SH "DESCRIPTION"
36.PP
37This tool is part of the
38\fBsamba\fR(7)
39suite\&.
40.PP
41ntlm_auth
42is a helper utility that authenticates users using NT/LM authentication\&. It returns 0 if the users is authenticated successfully and 1 if access was denied\&. ntlm_auth uses winbind to access the user and authentication data for a domain\&. This utility is only intended to be used by other programs (currently
43Squid
44and
45mod_ntlm_winbind)
46.SH "OPERATIONAL REQUIREMENTS"
47.PP
48The
49\fBwinbindd\fR(8)
50daemon must be operational for many of these commands to function\&.
51.PP
52Some of these commands also require access to the directory
53winbindd_privileged
54in
55$LOCKDIR\&. This should be done either by running this command as root or providing group access to the
56winbindd_privileged
57directory\&. For security reasons, this directory should not be world\-accessable\&.
58.SH "OPTIONS"
59.PP
60\-\-helper\-protocol=PROTO
61.RS 4
62Operate as a stdio\-based helper\&. Valid helper protocols are:
63.PP
64squid\-2\&.4\-basic
65.RS 4
66Server\-side helper for use with Squid 2\&.4\*(Aqs basic (plaintext) authentication\&.
67.RE
68.PP
69squid\-2\&.5\-basic
70.RS 4
71Server\-side helper for use with Squid 2\&.5\*(Aqs basic (plaintext) authentication\&.
72.RE
73.PP
74squid\-2\&.5\-ntlmssp
75.RS 4
76Server\-side helper for use with Squid 2\&.5\*(Aqs NTLMSSP authentication\&.
77.sp
78Requires access to the directory
79winbindd_privileged
80in
81$LOCKDIR\&. The protocol used is described here:
82http://devel\&.squid\-cache\&.org/ntlm/squid_helper_protocol\&.html\&. This protocol has been extended to allow the NTLMSSP Negotiate packet to be included as an argument to the
83YR
84command\&. (Thus avoiding loss of information in the protocol exchange)\&.
85.RE
86.PP
87ntlmssp\-client\-1
88.RS 4
89Client\-side helper for use with arbitrary external programs that may wish to use Samba\*(Aqs NTLMSSP authentication knowledge\&.
90.sp
91This helper is a client, and as such may be run by any user\&. The protocol used is effectively the reverse of the previous protocol\&. A
92YR
93command (without any arguments) starts the authentication exchange\&.
94.RE
95.PP
96gss\-spnego
97.RS 4
98Server\-side helper that implements GSS\-SPNEGO\&. This uses a protocol that is almost the same as
99squid\-2\&.5\-ntlmssp, but has some subtle differences that are undocumented outside the source at this stage\&.
100.sp
101Requires access to the directory
102winbindd_privileged
103in
104$LOCKDIR\&.
105.RE
106.PP
107gss\-spnego\-client
108.RS 4
109Client\-side helper that implements GSS\-SPNEGO\&. This also uses a protocol similar to the above helpers, but is currently undocumented\&.
110.RE
111.PP
112ntlm\-server\-1
113.RS 4
114Server\-side helper protocol, intended for use by a RADIUS server or the \*(Aqwinbind\*(Aq plugin for pppd, for the provision of MSCHAP and MSCHAPv2 authentication\&.
115.sp
116This protocol consists of lines in the form:
117Parameter: value
118and
119Parameter:: Base64\-encode value\&. The presence of a single period
120\&.
121indicates that one side has finished supplying data to the other\&. (Which in turn could cause the helper to authenticate the user)\&.
122.sp
123Currently implemented parameters from the external program to the helper are:
124.PP
125Username
126.RS 4
127The username, expected to be in Samba\*(Aqs
128\m[blue]\fBunix charset\fR\m[]\&.
129.PP
130Examples:
131.RS 4
132Username: bob
133.sp
134Username:: Ym9i
135.RE
136.RE
137.PP
138NT\-Domain
139.RS 4
140The user\*(Aqs domain, expected to be in Samba\*(Aqs
141\m[blue]\fBunix charset\fR\m[]\&.
142.PP
143Examples:
144.RS 4
145NT\-Domain: WORKGROUP
146.sp
147NT\-Domain:: V09SS0dST1VQ
148.RE
149.RE
150.PP
151Full\-Username
152.RS 4
153The fully qualified username, expected to be in Samba\*(Aqs
154\m[blue]\fBunix charset\fR\m[]
155and qualified with the
156\m[blue]\fBwinbind separator\fR\m[]\&.
157.PP
158Examples:
159.RS 4
160Full\-Username: WORKGROUP\ebob
161.sp
162Full\-Username:: V09SS0dST1VQYm9i
163.RE
164.RE
165.PP
166LANMAN\-Challenge
167.RS 4
168The 8 byte
169LANMAN Challenge
170value, generated randomly by the server, or (in cases such as MSCHAPv2) generated in some way by both the server and the client\&.
171.PP
172Examples:
173.RS 4
174LANMAN\-Challenge: 0102030405060708
175.RE
176.RE
177.PP
178LANMAN\-Response
179.RS 4
180The 24 byte
181LANMAN Response
182value, calculated from the user\*(Aqs password and the supplied
183LANMAN Challenge\&. Typically, this is provided over the network by a client wishing to authenticate\&.
184.PP
185Examples:
186.RS 4
187LANMAN\-Response: 0102030405060708090A0B0C0D0E0F101112131415161718
188.RE
189.RE
190.PP
191NT\-Response
192.RS 4
193The >= 24 byte
194NT Response
195calculated from the user\*(Aqs password and the supplied
196LANMAN Challenge\&. Typically, this is provided over the network by a client wishing to authenticate\&.
197.PP
198Examples:
199.RS 4
200NT\-Response: 0102030405060708090A0B0C0D0E0F10111213141516171
201.RE
202.RE
203.PP
204Password
205.RS 4
206The user\*(Aqs password\&. This would be provided by a network client, if the helper is being used in a legacy situation that exposes plaintext passwords in this way\&.
207.PP
208Examples:
209.RS 4
210Password: samba2
211.sp
212Password:: c2FtYmEy
213.RE
214.RE
215.PP
216Request\-User\-Session\-Key
217.RS 4
218Upon successful authenticaiton, return the user session key associated with the login\&.
219.PP
220Examples:
221.RS 4
222Request\-User\-Session\-Key: Yes
223.RE
224.RE
225.PP
226Request\-LanMan\-Session\-Key
227.RS 4
228Upon successful authenticaiton, return the LANMAN session key associated with the login\&.
229.PP
230Examples:
231.RS 4
232Request\-LanMan\-Session\-Key: Yes