Date: Mon, 17 May 2004 09:56:57 -0400 From: Richard Coleman <richardcoleman@mindspring.com> To: "David E. Meier" <dev@eth0.ch> Cc: freebsd-security@freebsd.org Subject: Re: Multi-User Security Message-ID: <40A8C4A9.2000705@mindspring.com> In-Reply-To: <4985.217.162.71.141.1084795720.squirrel@serv04.inetworx.ch> References: <4985.217.162.71.141.1084795720.squirrel@serv04.inetworx.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
David E. Meier wrote: > Hello list. > > I would like to get your opinion on what is a safe multi-user environment. > The scenario: > > We would like to offer to some customers of ours some sort of network > backup/archive. They would put daily or weekly backups from their local > machine on our server using rsync and SSH. Therefore, they all have a user > account on our server. However, we must ensure that they would absolutely > not be able to access any data of each other at all. > > What is the "best and safest" way to do so? Regular UNIX permission > settings? File system ACL's? User jails? Restricting commands in their > path environment? Or would it even make sense to encrypt the file system? > How would some of the solutions affect data backups/restore on our side? > > Any comment on this is welcome. Thanks. Dave. Using a chroot or a jail is the way to go if possible. If you can't use that, then unix permissions or ACL's is the next bet. Restricting commands is the most fragile solution since in many cases it can be subverted. Encrypting the data is also useful if you have the horsepower. Richard Coleman richardcoleman@mindspring.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40A8C4A9.2000705>