> Isn't it possible to prohibit chroot() if the current process is already
> chroot()ed?
There's not really much point IMHO. The whole point of chroot()
is increasing security: the last thing you want to do when you
have performed a chroot() is to hang around as superuser.
This isn't really kernel-related btw - could this subject be
dropped please?
Michiel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu