source: postlfs/security/mitkrb/mitkrb-config.xml@ ccca0bd

10.0 10.1 11.0 6.0 6.1 6.2 6.2.0 6.2.0-rc1 6.2.0-rc2 6.3 6.3-rc1 6.3-rc2 6.3-rc3 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 ken/refactor-virt krejzi/svn lazarus nosym perl-modules qt5new systemd-11177 systemd-13485 trunk v5_1 v5_1-pre1 xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since ccca0bd was ccca0bd, checked in by Tushar Teredesai <tushar@…>, 17 years ago

Updated to blfs-bootscripts-2004-05-15, added usb and kerberos init scripts

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@2164 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 6.8 KB
Line 
1<sect2>
2<title>Configuring <application><acronym>MIT</acronym> krb5</application></title>
3
4<sect3><title>Config files</title>
5<para><filename>/etc/krb5.conf</filename> and
6<filename>/var/lib/krb5kdc/kdc.conf</filename></para>
7</sect3>
8
9<sect3><title>Configuration Information</title>
10
11<sect4><title>Kerberos Configuration</title>
12
13<para>
14Create the Kerberos configuration file with the following command:
15</para>
16
17<screen><userinput><command>cat &gt; /etc/krb5.conf &lt;&lt; "EOF"</command>
18# Begin /etc/heimdal/krb5.conf
19
20[libdefaults]
21 default_realm = <replaceable>[LFS.ORG]</replaceable>
22 encrypt = true
23
24[realms]
25 <replaceable>[LFS.ORG]</replaceable> = {
26 kdc = <replaceable>[belgarath.lfs.org]</replaceable>
27 admin_server = <replaceable>[belgarath.lfs.org]</replaceable>
28 }
29
30[domain_realm]
31 .<replaceable>[lfs.org]</replaceable> = <replaceable>[LFS.ORG]</replaceable>
32
33[logging]
34 kdc = SYSLOG[:INFO[:AUTH]]
35 admin_server = SYSLOG[INFO[:AUTH]]
36 default = SYSLOG[[:SYS]]
37
38# End /etc/heimdal/krb5.conf
39<command>EOF</command></userinput></screen>
40
41<para>
42You will need to substitute your domain and proper hostname for the
43occurances of the belgarath and lfs.org names.
44</para>
45
46<para>
47<userinput>default_realm</userinput> should be the name of your domain changed to ALL CAPS.
48This isn't required, but both Heimdal and <acronym>MIT</acronym>
49recommend it.
50</para>
51
52<para>
53<userinput>encrypt = true</userinput> provides encryption of all traffic between kerberized
54clients and servers. It's not necessary and can be left off. If you
55leave it off, you can encrypt all traffic from the client to the server
56using a switch on the client program instead.
57</para>
58
59<para>
60The <userinput>[realms]</userinput> parameters tell the client programs where to look for the
61<acronym>KDC</acronym> authentication services.
62</para>
63
64<para>
65The <userinput>[domain_realm]</userinput> section maps a domain to a realm.
66</para>
67
68<para>
69Create the <acronym>KDC</acronym> database:
70</para>
71
72<screen><userinput><command>kdb5_util create -r <replaceable>[LFS.ORG]</replaceable> -s </command></userinput></screen>
73
74<para>
75Now we need to populate the database with principles (users). For now,
76just use your regular login name or root.
77</para>
78
79<screen><userinput><command>kadmin.local</command></userinput>
80<prompt>kadmin:</prompt><userinput><command>addprinc <replaceable>[loginname]</replaceable></command></userinput></screen>
81
82<para>
83The <acronym>KDC</acronym> server and any machine running kerberized
84server daemons must have a host key installed:
85</para>
86
87<screen><prompt>kadmin:</prompt><userinput><command>addprinc --random-key host/<replaceable>[belgarath.lfs.org]</replaceable></command></userinput></screen>
88
89<para>
90After choosing the defaults when prompted, you will have to export the
91data to a keytab file:
92</para>
93
94<screen><prompt>kadmin:</prompt><userinput><command>ktadd host/<replaceable>[belgarath.lfs.org]</replaceable></command></userinput></screen>
95
96<para>
97This should have created a file in
98<filename class="directory">/etc</filename> named
99<filename>krb5.keytab</filename> (Kerberos 5). This file should have 600
100(root rw only) permissions. Keeping the keytab files from public access
101is crucial to the overall security of the Kerberos installation.
102</para>
103
104<para>
105Eventually, you'll want to add server daemon principles to the database
106and extract them to the keytab file. You do this in the same way you
107created the host principles. Below is an example:
108</para>
109
110<screen><prompt>kadmin:</prompt><userinput><command>add --random-key ftp/<replaceable>[belgarath.lfs.org]</replaceable></command></userinput>
111<prompt>kadmin:</prompt><userinput><command>ktadd ftp/<replaceable>[belgarath.lfs.org]</replaceable></command></userinput></screen>
112
113<para>
114Exit the <command>kadmin</command> program (use <command>quit</command>
115or <command>exit</command>) and return back to the shell prompt. Start
116the <acronym>KDC</acronym> daemon manually, just to test out the
117installation:
118</para>
119
120<screen><userinput><command>/usr/sbin/krb5kdc &amp;</command></userinput></screen>
121
122<para>
123Attempt to get a ticket with the following command:
124</para>
125
126<screen><userinput><command>kinit <replaceable>[loginname]</replaceable></command></userinput></screen>
127
128<para>
129You will be prompted for the password you created. After you get your
130ticket, you can list it with the following command:
131</para>
132
133<screen><userinput><command>klist</command></userinput></screen>
134
135<para>
136Information about the ticket should be displayed on the screen.
137</para>
138
139<para>
140To test the functionality of the keytab file, issue the following
141command:
142</para>
143
144<screen><userinput><command>ktutil</command></userinput>
145<prompt>ktutil:</prompt><userinput>rkt /etc/krb5.keytab</userinput>
146<prompt>ktutil:</prompt><userinput>l</userinput></screen>
147
148<para>
149This should dump a list of the host principal, along with the encryption
150methods used to access the principal.
151</para>
152
153<para>
154At this point, if everything has been successful so far, you can feel
155fairly confident in the installation and configuration of the package.
156</para>
157
158<para>Install <filename>/etc/rc.d/init.d/kerberos</filename> init script
159included in the <xref linkend="intro-important-bootscripts"/>
160package.</para>
161
162<screen><userinput><command>make install-kerberos</command></userinput></screen>
163
164</sect4>
165
166<sect4><title>Using Kerberized Client Programs</title>
167
168<para>
169To use the kerberized client programs (<command>telnet</command>,
170<command>ftp</command>, <command>rsh</command>,
171<command>rcp</command>, <command>rlogin</command>), you first must get
172an authentication ticket. Use the <command>kinit</command> program to
173get the ticket. After you've acquired the ticket, you can use the
174kerberized programs to connect to any kerberized server on the network.
175You will not be prompted for authentication until your ticket expires
176(default is one day), unless you specify a different user as a command
177line argument to the program.
178</para>
179
180<para>
181The kerberized programs will connect to non kerberized daemons, warning
182you that authentication is not encrypted.</para></sect4>
183
184
185<sect4><title>Using Kerberized Server Programs</title>
186
187<para>Using kerberized server programs (<command>telnetd</command>,
188<command>kpropd</command>,
189<command>klogind</command> and <command>kshd</command>) requires two additional configuration steps.
190First the <filename>/etc/services</filename> file must be updated to
191include eklogin and krb5_prop. Second, the
192<filename>inetd.conf</filename> or <filename>xinetd.conf</filename> must
193be modified for each server that will be activated, usually replacing
194the server from <application>inetutils</application>.</para></sect4>
195
196<sect4><title>Additional Information</title>
197<para>
198For additional information consult <ulink
199url="http://web.mit.edu/kerberos/www/krb5-1.3/#documentation">Documentation
200for krb-&mitkrb-version;</ulink> on which the above instructions are based.
201</para>
202
203</sect4>
204
205</sect3>
206
207</sect2>
Note: See TracBrowser for help on using the repository browser.