4 |
- |
1 |
# -*- text -*-
|
|
|
2 |
#
|
|
|
3 |
# $Id$
|
|
|
4 |
|
|
|
5 |
# Microsoft CHAP authentication
|
|
|
6 |
#
|
|
|
7 |
# This module supports MS-CHAP and MS-CHAPv2 authentication.
|
|
|
8 |
# It also enforces the SMB-Account-Ctrl attribute.
|
|
|
9 |
#
|
|
|
10 |
mschap {
|
|
|
11 |
#
|
|
|
12 |
# If you are using /etc/smbpasswd, see the 'passwd'
|
|
|
13 |
# module for an example of how to use /etc/smbpasswd
|
|
|
14 |
|
|
|
15 |
# if use_mppe is not set to no mschap will
|
|
|
16 |
# add MS-CHAP-MPPE-Keys for MS-CHAPv1 and
|
|
|
17 |
# MS-MPPE-Recv-Key/MS-MPPE-Send-Key for MS-CHAPv2
|
|
|
18 |
#
|
|
|
19 |
# use_mppe = no
|
|
|
20 |
|
|
|
21 |
# if mppe is enabled require_encryption makes
|
|
|
22 |
# encryption moderate
|
|
|
23 |
#
|
|
|
24 |
# require_encryption = yes
|
|
|
25 |
|
|
|
26 |
# require_strong always requires 128 bit key
|
|
|
27 |
# encryption
|
|
|
28 |
#
|
|
|
29 |
# require_strong = yes
|
|
|
30 |
|
|
|
31 |
# Windows sends us a username in the form of
|
|
|
32 |
# DOMAIN\user, but sends the challenge response
|
|
|
33 |
# based on only the user portion. This hack
|
|
|
34 |
# corrects for that incorrect behavior.
|
|
|
35 |
#
|
|
|
36 |
# with_ntdomain_hack = no
|
|
|
37 |
|
|
|
38 |
# The module can perform authentication itself, OR
|
|
|
39 |
# use a Windows Domain Controller. This configuration
|
|
|
40 |
# directive tells the module to call the ntlm_auth
|
|
|
41 |
# program, which will do the authentication, and return
|
|
|
42 |
# the NT-Key. Note that you MUST have "winbindd" and
|
|
|
43 |
# "nmbd" running on the local machine for ntlm_auth
|
|
|
44 |
# to work. See the ntlm_auth program documentation
|
|
|
45 |
# for details.
|
|
|
46 |
#
|
|
|
47 |
# If ntlm_auth is configured below, then the mschap
|
|
|
48 |
# module will call ntlm_auth for every MS-CHAP
|
|
|
49 |
# authentication request. If there is a cleartext
|
|
|
50 |
# or NT hashed password available, you can set
|
|
|
51 |
# "MS-CHAP-Use-NTLM-Auth := No" in the control items,
|
|
|
52 |
# and the mschap module will do the authentication itself,
|
|
|
53 |
# without calling ntlm_auth.
|
|
|
54 |
#
|
|
|
55 |
# Be VERY careful when editing the following line!
|
|
|
56 |
#
|
|
|
57 |
# You can also try setting the user name as:
|
|
|
58 |
#
|
|
|
59 |
# ... --username=%{mschap:User-Name} ...
|
|
|
60 |
#
|
|
|
61 |
# In that case, the mschap module will look at the User-Name
|
|
|
62 |
# attribute, and do prefix/suffix checks in order to obtain
|
|
|
63 |
# the "best" user name for the request.
|
|
|
64 |
#
|
|
|
65 |
# ntlm_auth = "/path/to/ntlm_auth --request-nt-key --username=%{%{Stripped-User-Name}:-%{%{User-Name}:-None}} --challenge=%{%{mschap:Challenge}:-00} --nt-response=%{%{mschap:NT-Response}:-00}"
|
|
|
66 |
|
|
|
67 |
# For Apple Server, when running on the same machine as
|
|
|
68 |
# Open Directory. It has no effect on other systems.
|
|
|
69 |
#
|
|
|
70 |
# use_open_directory = yes
|
|
|
71 |
|
|
|
72 |
# On failure, set (or not) the MS-CHAP error code saying
|
|
|
73 |
# "retries allowed".
|
|
|
74 |
# allow_retry = yes
|
|
|
75 |
|
|
|
76 |
# An optional retry message.
|
|
|
77 |
# retry_msg = "Re-enter (or reset) the password"
|
|
|
78 |
}
|