source: chapter06/changingowner.xml@ e6ab4b5

Last change on this file since e6ab4b5 was e6ab4b5, checked in by Manuel Canales Esparcia <manuel@…>, 19 years ago

Ported r7294 to r7325 from trunk to alphabetical branch.

git-svn-id: http://svn.linuxfromscratch.org/LFS/branches/alphabetical/BOOK@7333 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

  • Property mode set to 100644
File size: 1.9 KB
Line 
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN"
3 "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
6]>
7
8<sect1 id="ch-system-changingowner">
9 <?dbhtml filename="changingowner.html"?>
10
11 <title>Changing Ownership</title>
12
13 <para>Currently, the <filename class="directory">/tools</filename> directory
14 is owned by the user <systemitem class="username">lfs</systemitem>, a user
15 that exists only on the host system. Although the <filename
16 class="directory">/tools</filename> directory can be deleted once the LFS
17 system has been finished, it can be retained to build additional LFS systems.
18 If the <filename class="directory">/tools</filename> directory is kept as is,
19 the files are owned by a user ID without a corresponding account. This is
20 dangerous because a user account created later could get this same user ID
21 and would own the <filename class="directory">/tools</filename> directory
22 and all the files therein, thus exposing these files to possible malicious
23 manipulation.</para>
24
25 <para>To avoid this issue, add the <systemitem class="username">lfs</systemitem>
26 user to the new LFS system later when creating the
27 <filename>/etc/passwd</filename> file, taking care to assign it the same user
28 and group IDs as on the host system. Alternatively, assign the contents of
29 the <filename class="directory">/tools</filename> directory to user
30 <systemitem class="username">root</systemitem> by running the following
31 command:</para>
32
33<screen><userinput>chown -R 0:0 /tools</userinput></screen>
34
35 <para>The command uses <parameter>0:0</parameter> instead of
36 <parameter>root:root</parameter>, because <command>chown</command>
37 is unable to resolve the name <quote>root</quote> until the
38 <filename>passwd</filename> file has been created.</para>
39
40</sect1>
Note: See TracBrowser for help on using the repository browser.