Changeset d066924

Timestamp:

10/18/2002 06:08:39 PM (22 years ago)

Author:

Gerard Beekmans <gerard@…>

Branches:

10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc

Children:

ac68bd3

Parents:

1ae2ba4

Message:

reworded

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2179 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

File:

• chapter06/changingowner.xml (modified) (1 diff)

chapter06/changingowner.xml

@@ -3 +3 @@
 <?dbhtml filename="changingowner.html" dir="chapter06"?>
 
-<para>The first thing we'll do, now that we're <emphasis>root</emphasis>,
-is change the ownership of the files and directories installed in Chapter 5
-to root -- because when later we don't delete the
-<filename class="directory">/static</filename> directory and start adding
-new users, one of these users might end up owning the statically linked
-programs, which is not a good idea.</para>
+<para>Right now the /static directory is owned by the lfs user. However,
+this user account exists only on the host system. Although you may delete
+the <filename class="directory">/static</filename> directory once you have
+finished your LFS system, you might want to keep it around, e.g. for
+building more LFS systems. But if you keep the
+<filename class="directory">/static</filename> directory you will end up
+with files owned by a user id without a corresponding account. This is
+dangerous because a user account created later could get this user id and
+would suddenly own the <filename class="directory">/static</filename>
+directory and all of the files therein. This could open the
+<filename class="directory">/static</filename> directory to manipulation by
+an untrusted user.</para>
 
-<para>Run the following command to make root the owner of all the statically
-linked programs:</para>
+<para>To avoid this issue, you can add the
+<emphasis>lfs</emphasis> user to the new LFS system later when creating
+the <filename>/etc/passwd</filename> file, taking care to assign it the
+same user and group id. Alternatively, you can (and the book will assume
+you do) run the following command now, to assign the contents of the
+<filename class="directory">/static</filename> directory to user
+<emphasis>root</emphasis> by running the following command:</para>
 
 <para><screen><userinput>chown -R 0:0 /static</userinput></screen></para>
 
-<para>The command uses "0:0" instead of "root:root", because there is no way
-to resolve the name "root", as glibc hasn't been installed yet.</para>
+<para>The command uses "0:0" instead of "root:root", because chown is unable
+to resolve the name "root" until glibc has been installed.</para>
 
 </sect1>