chroot support? #981

New Issue

ioerror · 2010-03-05T08:12:01Z

ioerror commented

2010-03-05 08:12:01 +00:00

I'd like Tahoe to be forced chrooted after a certain run time (say, after start up as a storage node) - On a modern GRSec enabled Linux machine, it may provide a bit of defense in depth.

ioerror added the

labels 2010-03-05 08:12:01 +00:00

ioerror added this to the undecided milestone 2010-03-05 08:12:01 +00:00

warner commented

2010-03-10 20:05:51 +00:00

FYI, I think that after tahoe's Node.startService is called, it shouldn't be touching anything outside of its basedir. (by that point, all python libraries should have been imported, random files like /etc/mime.types should have been read, and the Tahoe code itself never touches anything outside the basedir). It will need continued access to /dev/urandom, of course.

twistd has a --chroot argument which is worth exploring. I don't know when exactly it gets invoked, but it's probably the Right Way to do it, so if it doesn't work with --chroot, I'd be happy to try to fix tahoe to make it work.

FYI, I *think* that after tahoe's `Node.startService` is called, it shouldn't be touching anything outside of its basedir. (by that point, all python libraries should have been imported, random files like /etc/mime.types should have been read, and the Tahoe code itself never touches anything outside the basedir). It will need continued access to /dev/urandom, of course. `twistd` has a `--chroot` argument which is worth exploring. I don't know when exactly it gets invoked, but it's probably the Right Way to do it, so if it doesn't work with `--chroot`, I'd be happy to try to fix tahoe to make it work.