xref: /freebsd/lib/libsys/chroot.2 (revision b64c5a0ace59af62eff52bfe110a521dc73c937b)
1.\" Copyright (c) 1983, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. Neither the name of the University nor the names of its contributors
13.\"    may be used to endorse or promote products derived from this software
14.\"    without specific prior written permission.
15.\"
16.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
17.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
18.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
19.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
20.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
21.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
22.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
23.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
24.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
25.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
26.\" SUCH DAMAGE.
27.\"
28.Dd July 15, 2024
29.Dt CHROOT 2
30.Os
31.Sh NAME
32.Nm chroot ,
33.Nm fchroot
34.Nd change root directory
35.Sh LIBRARY
36.Lb libc
37.Sh SYNOPSIS
38.In unistd.h
39.Ft int
40.Fn chroot "const char *dirname"
41.Ft int
42.Fn fchroot "int fd"
43.Sh DESCRIPTION
44The
45.Fa dirname
46argument
47is the address of the pathname of a directory, terminated by an ASCII NUL.
48The
49.Fn chroot
50system call causes
51.Fa dirname
52to become the root directory,
53that is, the starting point for path searches of pathnames
54beginning with
55.Ql / .
56.Pp
57In order for a directory to become the root directory
58a process must have execute (search) access for that directory.
59.Pp
60It should be noted that
61.Fn chroot
62has no effect on the process's current directory.
63.Pp
64This call is restricted to the super-user.
65.Pp
66Depending on the setting of the
67.Ql kern.chroot_allow_open_directories
68sysctl variable, open filedescriptors which reference directories
69will make the
70.Fn chroot
71fail as follows:
72.Pp
73If
74.Ql kern.chroot_allow_open_directories
75is set to zero,
76.Fn chroot
77will always fail with
78.Er EPERM
79if there are any directories open.
80.Pp
81If
82.Ql kern.chroot_allow_open_directories
83is set to one (the default),
84.Fn chroot
85will fail with
86.Er EPERM
87if there are any directories open and the
88process is already subject to the
89.Fn chroot
90system call.
91.Pp
92Any other value for
93.Ql kern.chroot_allow_open_directories
94will bypass the check for open directories,
95mimicking the historic insecure behavior of
96.Fn chroot
97still present on other systems.
98.Pp
99The
100.Fn fchroot
101system call is identical to
102.Fn chroot
103except it takes a file descriptor instead of path.
104.Sh RETURN VALUES
105.Rv -std
106.Sh ERRORS
107The
108.Fn chroot
109system call
110will fail and the root directory will be unchanged if:
111.Bl -tag -width Er
112.It Bq Er ENOTDIR
113A component of the path name is not a directory.
114.It Bq Er EPERM
115The effective user ID is not the super-user, or one or more
116filedescriptors are open directories.
117.It Bq Er ENAMETOOLONG
118A component of a pathname exceeded 255 characters,
119or an entire path name exceeded 1023 characters.
120.It Bq Er ENOENT
121The named directory does not exist.
122.It Bq Er EACCES
123Search permission is denied for any component of the path name.
124.It Bq Er ELOOP
125Too many symbolic links were encountered in translating the pathname.
126.It Bq Er EFAULT
127The
128.Fa dirname
129argument
130points outside the process's allocated address space.
131.It Bq Er EIO
132An I/O error occurred while reading from or writing to the file system.
133.It Bq Er EINTEGRITY
134Corrupted data was detected while reading from the file system.
135.El
136.Pp
137The
138.Fn fchroot
139system call
140will fail and the root directory will be unchanged if:
141.Bl -tag -width Er
142.It Bq Er EACCES
143Search permission is denied for the directory referenced by the
144file descriptor.
145.It Bq Er EBADF
146The argument
147.Fa fd
148is not a valid file descriptor.
149.It Bq Er EIO
150An I/O error occurred while reading from or writing to the file system.
151.It Bq Er EINTEGRITY
152Corrupted data was detected while reading from the file system.
153.It Bq Er ENOTDIR
154The file descriptor does not reference a directory.
155.It Bq Er EPERM
156The effective user ID is not the super-user, or one or more
157filedescriptors are open directories.
158.El
159.Sh SEE ALSO
160.Xr chdir 2 ,
161.Xr jail 2
162.Sh HISTORY
163The
164.Fn chroot
165system call appeared in
166.At v7 .
167It was marked as
168.Dq legacy
169in
170.St -susv2 ,
171and was removed in subsequent standards.
172The
173.Fn fchroot
174system call first appeared in
175.Fx 15.0 .
176.Sh BUGS
177If the process is able to change its working directory to the target
178directory, but another access control check fails (such as a check for
179open directories, or a MAC check), it is possible that this system
180call may return an error, with the working directory of the process
181left changed.
182.Sh SECURITY CONSIDERATIONS
183The system has many hardcoded paths to files which it may load after
184the process starts.
185It is generally recommended to drop privileges immediately after a
186successful
187.Nm
188call,
189and restrict write access to a limited subtree of the
190.Nm
191root.
192For instance,
193setup the sandbox so that the sandboxed user will have no write
194access to any well-known system directories.
195.Pp
196For complete isolation from the rest of the system, use
197.Xr jail 2
198instead.
199