A
chroot on
Unix operating systems is an operation that changes the apparent disk
root directory for the current running process and its children. A program that is re-rooted to another directory cannot access or name files outside that directory, and the directory is called a "chroot
jail" or (less commonly) a "chroot prison". The term "chroot" may refer to the
chroot(2) system call or the
chroot(8) wrapper program.
History
The chroot system call was introduced during development of
Version 7 Unix in 1979, and also added to BSD by
Bill Joy on 18 March 1982 — 17 months before
4.2BSD was released — in order to test its installation and build system.
Uses
A chroot environment can be used to create and host a separate
virtualized copy of the software system. This can be useful for:
; Testing and development : A test environment can be set up in the chroot for software that would otherwise be too risky to deploy on a production system.
; Dependency control : Software can be developed, built and tested in a chroot populated only with its expected dependencies. This can prevent some kinds of linkage skew that can result from developers building projects with different sets of program libraries installed.
; Compatibility : Legacy software or software using a different
ABI must sometimes be run in a chroot because their supporting libraries or data files may otherwise clash in name or linkage with those of the host system.
; Recovery : Should a system be rendered unbootable, a chroot can be used to move back into the damaged environment after bootstrapping from an alternate root file system (such as from installation media, or a
Live CD).
; Privilege separation : Programs are allowed to carry open
file descriptors (for files,
pipelines and network connections) into the chroot, which can simplify jail design by making it unnecessary to leave working files inside the chroot directory. This also simplifies the common arrangement of running the potentially-vulnerable parts of a privileged program in a sandbox, in order to pre-emptively contain a security breach. Note that chroot is not necessarily enough to contain a process with root privileges.
Limitations
The chroot mechanism is not intended to defend against intentional tampering by privileged (root) users. On most systems, chroot contexts do not stack properly and chrooted programs with sufficient privileges may perform a
second chroot to break out. To mitigate the risk of this security weakness, chrooted programs should relinquish root privileges as soon as practical after chrooting, or other mechanisms - such as
FreeBSD Jails - should be used instead. Note that some systems, such as
FreeBSD, take precautions to prevent the second chroot attack.
On systems that support device nodes on ordinary filesystems, a chrooted root user can still create device nodes and mount the file systems on them; thus, the chroot mechanism is not intended by itself to be used to block low-level access to system devices by privileged users.
At startup, programs expect to find scratch space, configuration files, device nodes and shared libraries at certain preset locations. For a chrooted program to successfully start, the chroot directory must be populated with a minimum set of these files. This can make chroot difficult to use as a general sandboxing mechanism.
Only the root user can perform a chroot. This is intended to prevent users from putting a setuid program inside a specially-crafted chroot jail (for example, with a fake /etc/passwd and /etc/shadow file) that would fool it into a privilege escalation.
The chroot mechanism in itself also is not intended to restrict the use of resources like I/O, bandwidth, disk space or CPU time. Most Unixes are not completely file system-oriented and leave potentially disruptive functionality like networking and process control available through the system call interface to a chrooted program.
Some Unixes offer extensions of the chroot mechanism — broadly termed operating system-level virtualization — to address at least some of these limitations. These include:
Workload Partitions in AIX
Containers in Solaris
Linux-VServer, FreeVPS, and OpenVZ for Linux
Jails in FreeBSD
Sysjails in NetBSD and OpenBSD
DragonFly BSD jails in DragonFly BSD
Graphical Applications on chroot
It is possible to run graphical applications on a chrooted environment, using some methods:
Use xhost (or copy the secret from .Xauthority)
Use a nested X server like Xnest or the more modern Xephyr (or start a real X server from inside the jail)
Access the chroot via SSH using the X11 forwarding (ssh -X) feature
use openroot if your X server has been started with -nolisten tcp and if you do not run an ssh server.
using an X11 VNC server and connecting a VNC client outside the environment
Notable applications
The Postfix mail transfer agent operates as a pipeline of individually-chrooted helper programs.
Like 4.2BSD before it, the Debian and Ubuntu internal package-building farms use chroots extensively to catch unintentional build dependencies between packages. SUSE uses a similar method with its build program. Fedora, Red Hat, and various RPM-based distributions build all RPMs using a chroot tool such as mock.
Many FTP servers for POSIX systems use the chroot mechanism to sandbox untrusted FTP clients. This may be done by forking a process to handle an incoming connection, then chrooting the child (to avoid having to populate the chroot with libraries required for program startup).
If privilege separation is enabled, the
OpenSSH daemon will chroot an unprivileged helper process into an empty directory to handle pre-authentication network traffic for each client. The daemon can also sandbox SFTP and shell sessions in a chroot (from version 4.9p1 onwards).
References
openroot - an extended chroot with X11 access, /dev & /media automounting & more.
See also
List of Unix programs
Operating system-level virtualization
Category:Computer security procedures
Category:Free virtualization software
Category:Unix process and task management-related software
Category:Virtualization_software
