This is fairly bogus: it doesn't prevent the use of a module from a chrooted
env, but only loading the module from there. So all you need to do from
your chroot jail is to wait for some helpful soul to load the module you want
from some other process. Doesn't seem like a robust security feature.
It's maybe not bad in and of itself, but it's only potentially useful in some
contrived cases.
Stefan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu