shadowpwd-inst.xml 4.6 KB

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