source: boot/common/changingowner.xml@ a5d799a

Last change on this file since a5d799a was 287d7b9, checked in by Jim Gifford <clfs@…>, 19 years ago

r1166@server (orig r1164): chris | 2006-02-10 22:07:07 -0800
Added -v to the rest of the temp-system pages, and various other text updates

  • Property mode set to 100644
File size: 2.5 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-boot-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 directory, <filename class="directory">/cross-tools</filename> directory, and
15 <filename class="directory">$LFS</filename> directory are owned
16 by the user <systemitem class="username">lfs</systemitem>,
17 a user that exists only on the host system. For security reasons, the
18 $LFS root directory and all of it subdirectories should be owned by
19 <systemitem class="username">root</systemitem>. Change the ownership for $LFS and its subdirectories by running these commands:</para>
20
21<screen><userinput>chown -v root:root ${LFS}
22chown -Rv root:root $LFS/{bin,boot,dev,etc,home,lib,media,mnt,opt,proc,root,sbin,srv,sys,tmp,usr,var}</userinput></screen>
23
24 <para os="b">The same issue also exists with <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>. Although these directories can be deleted once the
25 LFS system has been finished, they can be retained to build additional
26 LFS systems. If the <filename class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename>
27 directories are kept as is, the files are owned by a user ID without a
28 corresponding account. This is dangerous because a user account created
29 later could get this same user ID and would own the <filename
30 class="directory">/tools</filename> and <filename class="directory">/cross-tools</filename> directories and all the files therein,
31 thus exposing these files to possible malicious manipulation.</para>
32
33 <para os="c">To avoid this issue, add the <systemitem
34 class="username">lfs</systemitem> user to the new LFS system later when
35 creating the <filename>/etc/passwd</filename> file, taking care to assign
36 it the same user and group IDs as on the host system. Alternatively,
37 assign the contents of the <filename class="directory">/tools</filename>
38 and <filename class="directory">/cross-tools</filename> directories to user <systemitem class="username">root</systemitem> by running
39 the following commands:</para>
40
41<screen><userinput>chown -Rv root:root /tools
42chown -Rv root:root /cross-tools</userinput></screen>
43
44</sect1>
Note: See TracBrowser for help on using the repository browser.