[tahoe-dev] Warning or error when running Tahoe as root

[Greg Troxel]

Justin Stottlemyer <justin.h.stottlemyer at gmail.com> writes:

> Tahoe much like a web service should probably run in a semi protected
> environment as a non privileged user (aka nobody) in most instances. Not a
> knock to the OP, but I think this is a fairly standard Sys Admin task.
> While it may not be friendly to the newest of users, it isn't unfriendly.

That's all true, but when one installs packages of many things (as a
package for a 'distribution' or 'packaging system'), they come with
their own non-root users.  In pkgsrc, installing tahoe causes:

  tahoes:*:1023:1024:tahoe server:/nonexistent:/sbin/nologin

but I haven't set up /etc/rc.d/tahoes to read a config file of server
directories and optional associated uids and start them.


The other issue is that tahoe is a capability system and does not have a
notion of file ownership.  So that makes things a bit odd relative to
typical unix filesystems.  A big question is whether there should be
multiple users sharing a gateway or one gateway process per uid, with
restricted unix-domain sockets for access.  (I am thinking of
multi-user systems as the general case, since I find that "single-user
system" is something that rarely exists.)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20120811/a4baa519/attachment.pgp>