Changeset b74e415 for chapter06/changingowner.xml
- Timestamp:
- 05/13/2003 07:31:22 AM (21 years ago)
- 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, 12.2, 12.2-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, 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/loongarch-12.2, xry111/mips64el, xry111/multilib, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
- Children:
- 4a7a683
- Parents:
- 9c713f35
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
chapter06/changingowner.xml
r9c713f35 rb74e415 3 3 <?dbhtml filename="changingowner.html" dir="chapter06"?> 4 4 5 <para>Right now the /stage1 directory is owned by the lfs user. However,6 this user account exists only on the host system. Although you may delete 7 the <filename class="directory">/stage1</filename> directory once you have8 finished your LFS system, you might want to keep it around, e.g. for 9 building more LFS systems. But if you keep the 10 <filename class="directory">/stage1</filename> directory you will end up 11 with files owned by a user id without a corresponding account. This is 12 dangerous because a user account created later could get this user id and 13 would suddenly own the <filename class="directory">/stage1</filename> 14 directory and all of the files therein. This could open the 15 <filename class="directory">/stage1</filename> directory to manipulation by 16 an untrusted user.</para>5 <para>Right now the <filename class="directory">/stage1</filename> directory 6 is owned by the user <emphasis>lfs</emphasis>, a user that exists only on your 7 host system. Although you will probably want to delete the 8 <filename class="directory">/stage1</filename> directory once you have 9 finished your LFS system, you may want to keep it around, for example to 10 build more LFS systems. But if you keep the 11 <filename class="directory">/stage1</filename> directory as it is, you end up 12 with files owned by a user ID without a corresponding account. This is 13 dangerous because a user account created later on could get this same user ID 14 and would suddenly own the <filename class="directory">/stage1</filename> 15 directory and all the files therein, thus exposing these files to possible 16 malicious manipulation.</para> 17 17 18 <para>To avoid this issue, you can add the 19 <emphasis>lfs</emphasis> user to the new LFS system later when creating 20 the <filename>/etc/passwd</filename> file, taking care to assign it the 21 same user and group id. Alternatively, you can (and the book will assume 22 you do) run the following command now, to assign the contents of the 23 <filename class="directory">/stage1</filename> directory to user 24 <emphasis>root</emphasis> by running the following command:</para> 18 <para>To avoid this issue, you could add the <emphasis>lfs</emphasis> user to 19 your new LFS system later on when creating the <filename>/etc/passwd</filename> 20 file, taking care to assign it the same user and group IDs as on your host 21 system. Alternatively, you can (and the book assumes you do) assign the 22 contents of the <filename class="directory">/stage1</filename> directory to 23 user <emphasis>root</emphasis> by running the following command:</para> 25 24 26 25 <para><screen><userinput>chown -R 0:0 /stage1</userinput></screen></para>
Note:
See TracChangeset
for help on using the changeset viewer.