tahoe-lafs/trac-2024-07-25

chroot support? #981

New issue

Open

opened 2010-03-05 08:12:01 +00:00 by ioerror · 1 comment

ioerror commented

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

Owner

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.

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.

tahoe-lafs added the

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

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

warner commented

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

Author

Owner

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.

tahoe-lafs added

and removed

labels 2010-03-25 00:37:17 +00:00

Sign in to join this conversation.

No labels

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#981

No description provided.