Re: modules dependencies

From: Amon Ott <ao@rsbac.org>
Subject: Re: modules dependencies
Date: Tue, 11 Jul 2000 16:50:44 +0200

Next Article (by Subject): my first install (2.4.0-test12) "john huttley"
Previous Article (by Subject): modules dependencies "Rockee W. Shi"
Top of Thread: modules dependencies "Rockee W. Shi"
Articles sorted by: [Date] [Author] [Subject]

On Die, 11 Jul 2000 Rockee W. Shi wrote:
> The file 'models.htm' says: "This module(AUTH) can be seen as a support
> module for all others."
> 
> Are there dependencies among RSBAC modules? If yes, what are they?
> 
> Can RSBAC run if we exclude the AUTH module in compile time?

All modules can work independently from each other. However, a module can extend
the functionality of another. E.g., if you compile in RC, ACL can additionally
use RC roles for ACLs.

AUTH does not lead to extensions to other modules, but it controls user IDs
effectively. There is no point in access control without proper authentication.
And there is no proper authentication, if any root process can deliberately
choose another user ID.

So, if you want to work without AUTH, you can do that, but I won't recommend
it. You might consider turning on Role Protection in the other modules. This
way, you can at least protect the Security Officer account against root.

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

Go to Compuniverse LWGate Home Page.