Re: RC separation of duty

From: ao@morpork.shnet.org (A. Ott)
Subject: Re: RC separation of duty
Date: 30 Oct 1999 14:17:00 +0200

Next Article (by Subject): Re: RC separation of duty "Paul D. Robertson"
Previous Article (by Subject): Re: RC separation of duty ao@morpork.shnet.org (A. Ott)
Top of Thread: RC separation of duty ao@morpork.shnet.org (A. Ott)
Next in Thread: Re: RC separation of duty "Paul D. Robertson"
Articles sorted by: [Date] [Author] [Subject]

********* ***************** ********** ****  *****   ***** ************
  To subject Re: RC separation of duty
  proberts@clark.net (Paul D. Robertson)  wrote:
********** ******************** ******  ********  ******* *************

> On 29 Oct 1999, A. Ott wrote:
> >   Admin (may read everything). This is kept, works as before and keeps
> >   things simple for beginners.
>
> This is very good.

It is essential. RSBAC is complicated enough.

> > - New role vector assign_roles:
> >   Which roles a user in this role may read and assign to users and
> >   processes (process only, if MODIFY_ATTRIBUTE is allowed), and which
>
> I'm going to be a very contented person :)
> > - These new vectors may only be changed by old style Role Admins. If you
> >   set them at the beginning, and then remove all Role Admins, this
> >   separation is forever fixed (well, unless booting Maint kernel).
>
> This is *exactly* what I was hoping for.

You asked for a separation scheme, which could be fixed at a point. I have  
a big dislike for omnipotent superusers. So I mixed it all up in my mind  
and developed the current scheme. I am glad I met your needs. :)

> > So you could reboot with new version, reset old admin_type to none for all
> > roles and thus get your current administration settings fixed.
>
> Is this the Oct 19 version of 1.0.9a on the Web site, or is it elsewhere
> that we should be looking?

No, it is not yet finished. Pre1 contains the new ACL group management.

This stuff will be in 1.0.9a-pre2, which won't come out before end of next  
week, maybe significantly later. I am still working on the admin tools,  
will be away several days next week, and then there will be some testing  
time.

The RC admin tools need a bigger overhaul to meet the ACL tool standards  
and allow the administration menues to work with the changes. When I am  
content with RC, pre2 will be pushed out to give you testing stuff.

Other pre2 goodies:
- At last, the log tells which module(s) made the final decision.
- 2.2.13 support is included.

For pre3, I will add USER target default ACLs and at last ACL menues.  
These must wait until the background is finished. I hope this is the last  
to do for the 1.0.9a release.

Other feature candidates:
- Really secure delete. Vadim, do you need it in 1.0.9a?
- Process/program based logging. To allow detailed examination of the  
behaviour of a program, e.g. to find necessary right settings. Might be  
reduced to a process flag and a special sys_exec_logged() syscall.

> [p.s. The Web article should be available on Monday, I'll post to this
> list when it's up at the site.]

Good!

Amon.

--

-
To unsubscribe from the rsbac list, send a mail to
majordomo@morpork.shnet.org with
unsubscribe rsbac
as single line in the body.

Go to Compuniverse LWGate Home Page.