I can't believe this guy works for redhat. > you are no safer inside a chroot than relying on system permissions to keep a user in check But how may systems l

I can't believe this guy works for redhat. > you are no safer inside a chroot than relying on system permissions to keep a user in check But how may systems lock down every executable in /bin and /usr/bin? Chroot is about denying an attacker a hackers toolkit when they get access. It's not just about hacking the current system, but the network. No gcc? No netcat or ssh or netstat? Or even bash? The first thing hackers look for is what tools are available on the system, and denying them any is a form of security. This had been known for decades.