From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: selinux@tycho.nsa.gov, Karl MacMillan <kmacmillan@tresys.com>,
Joshua Brindle <jbrindle@tresys.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [ SEMANAGE ] Add a few direct dbases to handle
Date: Sat, 15 Oct 2005 07:38:46 -0400 [thread overview]
Message-ID: <4350EA46.4000506@cornell.edu> (raw)
In-Reply-To: <4350E962.5080606@cornell.edu>
>
> By "backend-independent record code" I mean, being able to add a user,
> and not care where the user is stored.. being able to loop over the
> seuser mappings, and not care whether the data is coming from LDAP or
> the seusers file, because all I want to do is load it into policy.
Well, we wouldn't be loading the seusers into policy, but that's not
important - the point is... backend separation.
An example that makes sense would be looping over the seusers to find
the ones that would be affected, if, say, I revoked the staff_r role, or
changed some other policy thing that would affect seusers.
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2005-10-15 11:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-14 18:16 [ SEMANAGE ] Add a few direct dbases to handle Ivan Gyurdiev
2005-10-14 18:39 ` [ SEMANAGE ] Bugfix previous patches Ivan Gyurdiev
2005-10-14 20:08 ` Stephen Smalley
2005-10-14 20:20 ` [ SEMANAGE ] Add a few direct dbases to handle Joshua Brindle
2005-10-14 20:40 ` Ivan Gyurdiev
2005-10-14 20:45 ` Ivan Gyurdiev
2005-10-14 20:39 ` Joshua Brindle
2005-10-14 20:59 ` Ivan Gyurdiev
2005-10-14 21:06 ` Joshua Brindle
2005-10-14 21:40 ` Ivan Gyurdiev
2005-10-15 11:34 ` Ivan Gyurdiev
2005-10-15 11:38 ` Ivan Gyurdiev [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4350EA46.4000506@cornell.edu \
--to=ivg2@cornell.edu \
--cc=jbrindle@tresys.com \
--cc=kmacmillan@tresys.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.