gronod/lfs
1
0
Fork 0
mirror of https://git.linuxfromscratch.org/lfs.git synced 2025-03-06 06:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

Applied Zack's ownership patch which fixes bug #510 which was originall patched and submitted by Alex Groenewoud

Browse Source 
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2607 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
Gerard Beekmans 2003-05-13 07:31:22 +00:00
parent 9c713f35af
commit b74e415582
2 changed files with 21 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
chapter01/changelog.xml
View File

@ -74,6 +74,9 @@
</itemizedlist>
</para></listitem>
<listitem><para>May 12th, 2003 [winkie]: Applied "Changing ownership"
patch to polish the text. Closes bug #511.</para></listitem>
<listitem><para>May 12th, 2003 [winkie]: Applied "Configuring system
components" patch to polish the text. Closes bug #510.</para></listitem>

37
chapter06/changingowner.xml
View File

@ -2,26 +2,25 @@
<title>Changing ownership</title>
<?dbhtml filename="changingowner.html" dir="chapter06"?>
<para>Right now the /stage1 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">/stage1</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">/stage1</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">/stage1</filename>
directory and all of the files therein. This could open the
<filename class="directory">/stage1</filename> directory to manipulation by
an untrusted user.</para>
<para>Right now the <filename class="directory">/stage1</filename> directory
is owned by the user <emphasis>lfs</emphasis>, a user that exists only on your
host system. Although you will probably want to delete the
<filename class="directory">/stage1</filename> directory once you have
finished your LFS system, you may want to keep it around, for example to
build more LFS systems. But if you keep the
<filename class="directory">/stage1</filename> directory as it is, you end up
with files owned by a user ID without a corresponding account. This is
dangerous because a user account created later on could get this same user ID
and would suddenly own the <filename class="directory">/stage1</filename>
directory and all the files therein, thus exposing these files to possible
malicious manipulation.</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">/stage1</filename> directory to user
<emphasis>root</emphasis> by running the following command:</para>
<para>To avoid this issue, you could add the <emphasis>lfs</emphasis> user to
your new LFS system later on when creating the <filename>/etc/passwd</filename>
file, taking care to assign it the same user and group IDs as on your host
system. Alternatively, you can (and the book assumes you do) assign the
contents of the <filename class="directory">/stage1</filename> directory to
user <emphasis>root</emphasis> by running the following command:</para>
<para><screen><userinput>chown -R 0:0 /stage1</userinput></screen></para>