summaryrefslogtreecommitdiffstats
path: root/lib/libc
diff options
context:
space:
mode:
authorrwatson <rwatson@FreeBSD.org>2003-01-31 21:19:22 +0000
committerrwatson <rwatson@FreeBSD.org>2003-01-31 21:19:22 +0000
commitac892a92343b12afcb5039f4040af988c146ea43 (patch)
tree413a70347733b410a78c945e308fa8ab98804d28 /lib/libc
parentb1d44eed4c448fdf514cfa7a3c29806800026936 (diff)
downloadFreeBSD-src-ac892a92343b12afcb5039f4040af988c146ea43.zip
FreeBSD-src-ac892a92343b12afcb5039f4040af988c146ea43.tar.gz
Document a bug in our chroot(2) implementation: if access control
checks, including the "open directory" check or a MAC check fail, after the working directory of the process has been changed, then the cwd of the process will be left as the target directory rather than the original directory. At some point, this bug might be fixable by performing the directory change only after permission is granted for the change. In the mean time document it (it's been there for a while).
Diffstat (limited to 'lib/libc')
-rw-r--r--lib/libc/sys/chroot.26
1 files changed, 6 insertions, 0 deletions
diff --git a/lib/libc/sys/chroot.2 b/lib/libc/sys/chroot.2
index 148bcd5..b2c3b4e 100644
--- a/lib/libc/sys/chroot.2
+++ b/lib/libc/sys/chroot.2
@@ -137,3 +137,9 @@ The
.Fn chroot
system call appeared in
.Bx 4.2 .
+.Sh BUGS
+If the process is able to change its working directory to the target
+directory, but another access control check fails (such as a check for
+open directories, or a MAC check), it is possible that this system
+call may return an error, with the working directory of the process
+left changed.
OpenPOWER on IntegriCloud