Changeset da7d5fc for BOOK/chroot/common


Ignore:
Timestamp:
Apr 17, 2014, 11:30:22 PM (11 years ago)
Author:
Chris Staub <chris@…>
Branches:
clfs-3.0.0-systemd, clfs-3.0.0-sysvinit, master, systemd, sysvinit
Children:
7e47edf
Parents:
f3c06b3
Message:

Updates to changin ownership page

File:
1 edited

Legend:

Unmodified
Added
Removed

  • BOOK/chroot/common/changingowner.xml

    rf3c06b3 rda7d5fc  
    1111  <title>Changing Ownership</title>
    1212
    13     <note>
    14       <para>This step is not optional as some of the binaries in
    15       <filename class="directory">/tools</filename> are set u+s.
    16       Leaving the permissions as is could cause some commands,
    17       <command>mount</command> in particular, to fail later.</para>
    18     </note>
    19 
    2013    <para os="a">Currently, the <filename class="directory">/tools</filename>
    2114    and <filename class="directory">/cross-tools</filename> directories
    2215    are owned by the user <emphasis>clfs</emphasis>, a user that
    23     exists only on the host system. Although the <filename
     16    exists only on the host system. Although <filename
    2417    class="directory">/tools</filename> and <filename
    25     class="directory">/cross-tools</filename> directories can be deleted
    26     once the CLFS system has been finished, they can be retained to build
     18    class="directory">/cross-tools</filename> can be deleted once the CLFS
     19    system has been finished, they can be retained to build
    2720    additional CLFS systems. If the <filename class="directory">/tools</filename>
    2821    and <filename class="directory">/cross-tools</filename> directories are
    2922    kept as is, the files are owned by a user ID without a corresponding
    3023    account. This is dangerous because a user account created later could
    31     get this same user ID and would own the <filename
    32     class="directory">/tools</filename> directory and all the files therein,
    33     thus exposing these files to possible malicious manipulation.</para>
     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>
    3426
    35     <para os="b">To avoid this issue, add the <systemitem
    36     class="username">clfs</systemitem> user to the new CLFS system later when
    37     creating the <filename>/etc/passwd</filename> file, taking care to assign
    38     it the same user and group IDs as on the host system. Alternatively,
     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,
    3931    assign the contents of the <filename class="directory">/tools</filename>
    4032    and <filename class="directory">/cross-tools</filename> directories to
Note: See TracChangeset for help on using the changeset viewer.