1 | <?xml version="1.0" encoding="ISO-8859-1"?> |
---|
2 | <!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" |
---|
3 | "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [ |
---|
4 | <!ENTITY % general-entities SYSTEM "../../general.ent"> |
---|
5 | %general-entities; |
---|
6 | ]> |
---|
7 | |
---|
8 | <sect1 id="ch-chroot-changingowner"> |
---|
9 | <?dbhtml filename="changingowner.html"?> |
---|
10 | |
---|
11 | <title>Changing Ownership</title> |
---|
12 | |
---|
13 | <para os="a">Currently, the <filename class="directory">/tools</filename> |
---|
14 | and <filename class="directory">/cross-tools</filename> directories |
---|
15 | are owned by the user <emphasis>clfs</emphasis>, a user that |
---|
16 | exists only on the host system. Although <filename |
---|
17 | class="directory">/tools</filename> and <filename |
---|
18 | class="directory">/cross-tools</filename> can be deleted once the CLFS |
---|
19 | system has been finished, they can be retained to build |
---|
20 | additional CLFS systems. If the <filename class="directory">/tools</filename> |
---|
21 | and <filename class="directory">/cross-tools</filename> directories are |
---|
22 | kept as is, the files are owned by a user ID without a corresponding |
---|
23 | account. This is dangerous because a user account created later could |
---|
24 | get this same user ID and would own these directories and all the files |
---|
25 | therein, thus exposing those files to possible malicious manipulation.</para> |
---|
26 | |
---|
27 | <para os="b">One possible fix for this issue might be to add the |
---|
28 | <systemitem class="username">clfs</systemitem> user to the new CLFS system |
---|
29 | later when creating the <filename>/etc/passwd</filename> file, taking care |
---|
30 | to assign it the same user and group IDs as on the host system. Alternatively, |
---|
31 | assign the contents of the <filename class="directory">/tools</filename> |
---|
32 | and <filename class="directory">/cross-tools</filename> directories to |
---|
33 | user <systemitem class="username">root</systemitem> by running the |
---|
34 | following commands:</para> |
---|
35 | |
---|
36 | <screen os="c"><userinput>chown -Rv 0:0 /tools |
---|
37 | chown -Rv 0:0 /cross-tools</userinput></screen> |
---|
38 | |
---|
39 | <para os="d">The commands use <parameter>0:0</parameter> instead of |
---|
40 | <parameter>root:root</parameter>, because <command>chown</command> |
---|
41 | is unable to resolve the name <quote>root</quote> until the |
---|
42 | <filename>passwd</filename> file has been created.</para> |
---|
43 | |
---|
44 | </sect1> |
---|