Carlos E. R. schreef op 11-04-16 12:18:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Monday, 2016-04-11 at 08:06 +0200, Per Jessen wrote:
Carlos E. R. wrote:
Say, a backup admin. In Linux it has to be root.
It's not that you can't do it on Linux, it's simply that noone has put any (or enough) effort into developing a framework for managing and delegating permissions and such. You can actually do quite a lot with sudo, but yes, it's cumbersome.
Well, the way I think about it, we would need privileged UIDs.
Think of a backup admin: he needs execute permissions on all directories, and read access on all files, and those permissions must be assigned by default to all new files and directories. In effect, he needs read access to all files owned by UID 0.
Nice thinking. In the Linux model you would need a root-user that has masked permissions. If the regular root has everything, you give a limited set (to everything) to the masked user. If then you needed something more fine-grained, you would create a mask that applies to the file system (hierarchy) in which case some trees might be completely inaccessible, others may have certain masked permissions, and so on. All filesystem operations would then consult this masking layer and inquire whether the current user has permission to do the certain thing that was requested.
Another, related, feature, is seen by the trick some do of creating another admin user with UID 0 besides root.
These are very basic access, they need, I think, a core redesign of how Linux/Unix work. Some kind of delegated/effective UID 0, without being it, not needing to alter the permissions of files.
Yeah a user that has masked permissions based on another user. That could even become a tree of users and then you have something that already closely resembles roles.
No, I do not know how to do it, or being more precise. :-(
Perhaps negative numbers, to flag that they are special. Then a structure listing what each of those UIDs can do. Like a list of directories to which they have superseding permissions.
Yes 1. an origin user 2. patterns to describe directory trees or locations 3. masks you can apply to those trees (or parts of them) Not unlike the way a firewall does it. For instance you could have origin user root. then you say a form of "deny all". then you select certain paths that the user must have access to. root has full access, so you create a mask of "-w" for instance if you don't want writing. the "deny all" really comes at the end (default chain). maybe a bit weird, but the masks are to take permissions away. However you could apply a full mask to any trees you do not define. I don't know. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org