[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Alternative user management approach
--- Russell Coker <russell@xxxxxxxxxxxx> wrote:
> The group-name thing could become fun if we have
> multiple names for the same
> GID (it's not recommended but it works at the
> moment) and the GID is the
> primary group for some users. The Unix user-name is
> unambiguous as we start
> with the name for every operation AFAIK.
>
> > How does all this work with MLS ranges?
>
> How does it cause problems with MLS?
Maybe it doesn't. On the other hand, can you
explain how it might work if you have a user
(I'll call him Barney today) who is cleared
to Secret in compartment A17 and B43? Do we
have to have a seperate role for Secret,A17
and Secret,B32 or do we need SELinux users
Barney,Unclassified
Barney,Secret
Barney,Secret,A17
Barnet,Secret,B43
Barney,Secret,A17,B43
I could see arguments put forth for either
of these schemes as well as a number of others.
Just as multiple groups can muddy the waters
so to can clearance ranges result in issues of
attribute permutation.
> > Do we have a new file which associates uids to
> user roles?
>
> Unix account names not UIDs. I think a mapping file
> is the only way.
Names not numbers, definitly.
Casey Schaufler
casey@xxxxxxxxxxxxxxxx
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.
This mailing list archive is a service of Copilot Consulting.