1 | <sect2><title> </title><para> </para></sect2>
|
---|
2 |
|
---|
3 | <sect2>
|
---|
4 | <title>Installation of Shadow</title>
|
---|
5 |
|
---|
6 | <para>The <userinput>login</userinput>, <userinput>getty</userinput> and
|
---|
7 | <userinput>init</userinput> programs (and some others) maintain a number
|
---|
8 | of logfiles to record who are and who were logged in to the system. These
|
---|
9 | programs, however, don't create these logfiles when they don't exist, so if
|
---|
10 | you want this logging to occur you will have to create the files yourself.
|
---|
11 | The Shadow package needs to detect these files in their proper place, so we
|
---|
12 | create them now, with their proper permissions:</para>
|
---|
13 |
|
---|
14 | <screen><userinput>touch /var/run/utmp /var/log/{btmp,lastlog,wtmp}
|
---|
15 | chmod 644 /var/run/utmp /var/log/{btmp,lastlog,wtmp}</userinput></screen>
|
---|
16 |
|
---|
17 | <para>The <filename>/var/run/utmp</filename> file lists the users that are
|
---|
18 | currently logged in, the <filename>/var/log/wtmp</filename> file who
|
---|
19 | <emphasis>were</emphasis> logged in and when.
|
---|
20 | The <filename>/var/log/lastlog</filename> file shows for each user when he
|
---|
21 | or she last logged in, and the <filename>/var/log/btmp</filename> lists the
|
---|
22 | bad login attempts.</para>
|
---|
23 |
|
---|
24 | <para>Shadow hard-wires the path to the <userinput>passwd</userinput> binary
|
---|
25 | within the binary itself, but does this the wrong way. If a
|
---|
26 | <userinput>passwd</userinput> binary is not present before installing Shadow,
|
---|
27 | the package incorrectly assumes it is going to be located at
|
---|
28 | <filename>/bin/passwd</filename>, but then installs it in
|
---|
29 | <filename>/usr/bin/passwd</filename>. This will lead to errors about not finding
|
---|
30 | <filename>/bin/passwd</filename>. To work around this bug, create a dummy
|
---|
31 | <filename>passwd</filename> file, so that it gets hard-wired properly:</para>
|
---|
32 |
|
---|
33 | <screen><userinput>touch /usr/bin/passwd</userinput></screen>
|
---|
34 |
|
---|
35 | <para>The current Shadow suite has a problem that causes in the
|
---|
36 | <userinput>newgrp</userinput> command to fail. The following patch (also
|
---|
37 | appearing in Shadow's CVS code) fixes this problem:</para>
|
---|
38 |
|
---|
39 | <screen><userinput>patch -Np1 -i ../&shadow-patch;</userinput></screen>
|
---|
40 |
|
---|
41 | <para>Now prepare Shadow for compilation:</para>
|
---|
42 |
|
---|
43 | <screen><userinput>./configure --prefix=/usr --libdir=/usr/lib --enable-shared</userinput></screen>
|
---|
44 |
|
---|
45 | <para>Compile the package:</para>
|
---|
46 |
|
---|
47 | <screen><userinput>make</userinput></screen>
|
---|
48 |
|
---|
49 | <para>And install it:</para>
|
---|
50 |
|
---|
51 | <screen><userinput>make install</userinput></screen>
|
---|
52 |
|
---|
53 | <para>Shadow uses two files to configure authentication settings for the
|
---|
54 | system. Install these two config files:</para>
|
---|
55 |
|
---|
56 | <screen><userinput>cp etc/{limits,login.access} /etc</userinput></screen>
|
---|
57 |
|
---|
58 | <para>We want to change the password method to enable MD5 passwords which are
|
---|
59 | theoretically more secure than the default "crypt" method and also allow
|
---|
60 | password lengths greater than 8 characters. We also need to change the old
|
---|
61 | <filename class="directory">/var/spool/mail</filename> location for user
|
---|
62 | mailboxes to the current location at
|
---|
63 | <filename class="directory">/var/mail</filename>. We do this by changing the
|
---|
64 | relevant configuration file while copying it to its destination:</para>
|
---|
65 |
|
---|
66 | <screen><userinput>sed -e 's%/var/spool/mail%/var/mail%' \
|
---|
67 | -e 's%#MD5_CRYPT_ENAB.no%MD5_CRYPT_ENAB yes%' \
|
---|
68 | etc/login.defs.linux > /etc/login.defs</userinput></screen>
|
---|
69 |
|
---|
70 | <note><para>Be extra careful when typing all of the above. It is probably safer
|
---|
71 | to cut-and-paste it rather than try and type it all in.</para></note>
|
---|
72 |
|
---|
73 | <para>According to the man page of <userinput>vipw</userinput>, a
|
---|
74 | <userinput>vigr</userinput> program should exist too. Since the installation
|
---|
75 | procedure doesn't create this program, create a symlink manually:</para>
|
---|
76 |
|
---|
77 | <screen><userinput>ln -s vipw /usr/sbin/vigr</userinput></screen>
|
---|
78 |
|
---|
79 | <para>As the <filename>/bin/vipw</filename> symlink is redundant (and even
|
---|
80 | pointing to a non-existent file), remove it:</para>
|
---|
81 |
|
---|
82 | <screen><userinput>rm /bin/vipw</userinput></screen>
|
---|
83 |
|
---|
84 | <para>Now move the <userinput>sg</userinput> program to its proper place:</para>
|
---|
85 |
|
---|
86 | <screen><userinput>mv /bin/sg /usr/bin</userinput></screen>
|
---|
87 |
|
---|
88 | <para>And move Shadow's dynamic libraries to a more appropriate location:</para>
|
---|
89 |
|
---|
90 | <screen><userinput>mv /usr/lib/lib{shadow,misc}.so.0* /lib</userinput></screen>
|
---|
91 |
|
---|
92 | <para>As some packages expect to find the just-moved libraries in
|
---|
93 | <filename>/usr/lib</filename>, create the following symlinks:</para>
|
---|
94 |
|
---|
95 | <screen><userinput>ln -sf ../../lib/libshadow.so.0 /usr/lib/libshadow.so
|
---|
96 | ln -sf ../../lib/libmisc.so.0 /usr/lib/libmisc.so</userinput></screen>
|
---|
97 |
|
---|
98 | <para>Coreutils has already installed a <userinput>groups</userinput> program
|
---|
99 | in <filename>/usr/bin</filename>. If you wish, you can remove the one
|
---|
100 | installed by Shadow:</para>
|
---|
101 |
|
---|
102 | <screen><userinput>rm /bin/groups</userinput></screen>
|
---|
103 |
|
---|
104 | </sect2>
|
---|
105 |
|
---|