Why chroot is not a security boundary

• A

  The process remains perfectly able to read files sitting outside the directory, simply by using absolute paths instead

• B

  chroot can be disabled by any process at will

• C

  It restricts only the file system view, leaving processes, network and kernel interfaces fully reachable

• D

  The directory must be writable, so the process can modify its own jail