blob: a98fe14e31ab2fb4ae7eb1c5ecabcba32dcf944a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
|
<chapter id="ADS">
<chapterinfo>
<author>
<firstname>Andrew</firstname><surname>Tridgell</surname>
</author>
<pubdate>2002</pubdate>
</chapterinfo>
<title>Samba as a ADS domain member</title>
<para>
This is a rough guide to setting up Samba 3.0 with kerberos authentication against a
Windows2000 KDC.
</para>
<sect1>
<title>Setup your <filename>smb.conf</filename></title>
<para>You must use at least the following 3 options in smb.conf:</para>
<para><programlisting>
realm = YOUR.KERBEROS.REALM
security = ADS
encrypt passwords = yes
</programlisting></para>
<para>
In case samba can't figure out your ads server using your realm name, use the
<command>ads server</command> option in <filename>smb.conf</filename>:
<programlisting>
ads server = your.kerberos.server
</programlisting>
</para>
<para>You do *not* need a smbpasswd file, and older clients will
be authenticated as if "security = domain", although it won't do any harm
and allows you to have local users not in the domain.
I expect that the above required options will change soon when we get better
active directory integration.</para>
</sect1>
<sect1>
<title>Setup your <filename>/etc/krb5.conf</filename></title>
<para>The minimal configuration for krb5.conf is:</para>
<para><programlisting>
[realms]
YOUR.KERBEROS.REALM = {
kdc = your.kerberos.server
}
</programlisting></para>
<para>Test your config by doing a "kinit USERNAME@REALM" and making sure that
your password is accepted by the Win2000 KDC. </para>
<para>NOTE: The realm must be uppercase. </para>
<para>
You also must ensure that you can do a reverse DNS lookup on the IP
address of your KDC. Also, the name that this reverse lookup maps to
must either be the netbios name of the KDC (ie. the hostname with no
domain attached) or it can alternatively be the netbios name
followed by the realm.
</para>
<para>
The easiest way to ensure you get this right is to add a /etc/hosts
entry mapping the IP address of your KDC to its netbios name. If you
don't get this right then you will get a "local error" when you try
to join the realm.
</para>
<para>
If all you want is kerberos support in smbclient then you can skip
straight to step 5 now. Step 3 is only needed if you want kerberos
support for smbd and winbindd.
</para>
</sect1>
<sect1>
<title>Create the computer account</title>
<para>
As a user that has write permission on the Samba private directory
(usually root) run:
<command>net ads join</command>
</para>
<sect2>
<title>Possible errors</title>
<para>
<variablelist>
<varlistentry><term>"ADS support not compiled in"</term>
<listitem><para>Samba must be reconfigured (remove config.cache) and recompiled (make clean all install) after the kerberos libs and headers are installed.</para></listitem></varlistentry>
</variablelist>
</para>
</sect2>
</sect1>
<sect1>
<title>Test your server setup</title>
<para>
On a Windows 2000 client try <command>net use * \\server\share</command>. You should
be logged in with kerberos without needing to know a password. If
this fails then run <command>klist tickets</command>. Did you get a ticket for the
server? Does it have an encoding type of DES-CBC-MD5 ?
</para>
</sect1>
<sect1>
<title>Testing with smbclient</title>
<para>
On your Samba server try to login to a Win2000 server or your Samba
server using smbclient and kerberos. Use smbclient as usual, but
specify the -k option to choose kerberos authentication.
</para>
</sect1>
<sect1>
<title>Notes</title>
<para>You must change administrator password at least once after DC
install, to create the right encoding types</para>
<para>w2k doesn't seem to create the _kerberos._udp and _ldap._tcp in
their defaults DNS setup. Maybe fixed in service packs?</para>
</sect1>
</chapter>
|
