From 673b0d84ba9591e07c0bdf0ee49d92eba10f502c Mon Sep 17 00:00:00 2001 From: Matthew Burgess Date: Mon, 3 May 2004 10:59:46 +0000 Subject: * Merged newxml into HEAD git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@3435 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689 --- chapter06/changingowner.xml | 36 ++++++++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 chapter06/changingowner.xml (limited to 'chapter06/changingowner.xml') diff --git a/chapter06/changingowner.xml b/chapter06/changingowner.xml new file mode 100644 index 000000000..cef15f8ba --- /dev/null +++ b/chapter06/changingowner.xml @@ -0,0 +1,36 @@ + + + %general-entities; +]> + +Changing ownership + + +Right now the /tools directory +is owned by the user lfs, a user that exists only on your +host system. Although you will probably want to delete the +/tools 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 +/tools 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 /tools +directory and all the files therein, thus exposing these files to possible +malicious manipulation. + +To avoid this issue, you could add the lfs user to +your new LFS system later on when creating the /etc/passwd +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 /tools directory to +user root by running the following command: + +chown -R 0:0 /tools + +The command uses 0:0 instead of root:root, +because chown is unable to resolve the name +root until the password file has been created. + + -- cgit v1.2.3-54-g00ecf