On 24.05.2012 11:25, Andreas Jaeger wrote:
Let's start a new thread to look a bit more at different roles.
I saw these two proposals:
Stefan Seyfried proposed a machine use case:
Having a few "presets" with the most common use cases, best accompanied with a short description is still a good idea IMHO. Maybe stuff like:
* "Admin configured server": you need the root password for all changes
-> basically like in good old times before polkit and friends: you'll
need to "su -" and then use yast or whatever to change stuff.
* "User configured laptop": you are allowed to connect to WiFi networks,> connect printers and install package updates with your user account. For adding software repositories and installing additional software, you'll need the root passowrd.
* "third preset": I have no idea what a third preset could be
Hans Witvliet seems to suggest user roles:
Shouldnt be too hard for the YaST-guru's Sort of matrix.
In the end your security model has three options: 1) For home-users (or general: single responsibility) end user is allowed to do all. (what Linus wanted) 2) the old-fashioned way, where you need to be root for everything 3) above mentoned proposal, where the privilige for any particular part is assigned to a specific group, and where the utmost highest admin, can assign those priviliges to any user.
Fits nice in "the least privilige" model, easier to maintain security in a large organiation.
I think that we need different settings for different users - even on the same machine. So, some kind of roles. I like the idea of having some configuration module for special purposes and also the idea of role-based administration - just fear it might be difficult to do.
AFAICS SELinux appears to be capable of implementing RBAC with MAC though it seems though that not even Redhat seems to makes use of that by default. Offering that with preconfigured roles for common tasks seems like a massive undertaking, extending YaST to assign roles to users in the user management modules is probably the easiest part.
So, my call for help again: Please give some proposals on what kind of roles/scenarios we want to offer - and be as precise on the different roles/scenarios as possible.
If you want to have a look at an existing implementation and its preconfigured roles, have a look at http://docs.oracle.com/cd/E19963-01/html/821-1456/rbacref-26.html . (Note that these are strictly speaking not roles but preconfigured "rights profiles" for common use cases consisting of capabilities which can be assigned either directly to users or to role accounts which users can assume after authentication.) -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org