Quote:
Originally Posted by dor
I wish to setup a secured multi user environment.
|
Can I ask why? What Real Life threats you must defend against?
Quote:
Originally Posted by dor
(..) users shouldn't be capable to see other users files/directories (task #1) nor spying on their communication (task #2).
|
As EricTRA already replied basic DAC rights keep unprivileged users from reading files they do not have rights to. Likewise unprivileged users homes in /home should by default be set to have octal 0700 access rights at creation time and users should have their umask set to 0027 through /etc/profile(.d/*).
Quote:
Originally Posted by dor
BUT, users sometimes wish to share files, so only we'll create one user account for that, with the following permissions on his /home directory: 0755 (to share files with ALL users, not only with the user's group)
|
That should be either ( users added to a common group; chgrp the directory and directory octal mode 1770 ) or using setfacl as EricTRA already replied. Before you turn down CLs (acl.bestbits.ac) do know they have been around for a long time and examples at
http://www.suse.de/~agruen/acl/linux-acls/online/ should help get you achieve what you need quickly. (There's even a GUI ACL editor called "Eiciel".)
Quote:
Originally Posted by dor
To prevent users from spying on others' communication (task #2) is pretty much simple: as long there's a single user connected, he couldn't spy on other user's communication because the other user is disconnected...
|
That kind of goes against your wish for having a "secured
multi-user environment" ;-p It also shows why I asked you for reasons because for instance an out-of-the-box basic GNU/Linux installation, or a SELinux-enabled targeted policy-running one, will allow any user to for instance list processes, network connections and open files. Applying more invasive measures, like running a GRSecurity-enabled kernel, can compartmentalize process space. The cost of running a GRSecurity-enabled kernel will only be high if your distribution does not provide GRSecurity-enabled kernels by default. What you want can be done without RBAC rules.
Quote:
Originally Posted by dor
Would you advice adding an additional level of security?
|
I would advice you to be verbose not about what you want but about what you really need. If you don't know what you need then start by drafting a list of services you offer, who you offer it to and what must be expected from you.