All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: selinux@tycho.nsa.gov, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [SEPOL] Remove defrole from sepol
Date: Wed, 23 Nov 2005 11:38:56 -0500	[thread overview]
Message-ID: <43849B20.3090500@tresys.com> (raw)
In-Reply-To: <43848B72.1010603@cornell.edu>

Ivan Gyurdiev wrote:
> I'm starting to question the need for this interface at all... it's an 
> interface for a very narrow user base - genhomedircon... which is 
> probably a mistake. I would prefer genhomedircon to find its way into 
> libsemanage, which is its only user (does it have another one?). 
the semanage tool Dan is writing could use it, to determine if a level 
should be set, or it could just rely on getting an error back if you try 
to set a level and it is a non mls system.


> there would be no reason for an external interface for default roles and 
> hacks to move genhomedircon before one lock is released, and after the 
> other is released, and things like that would not be necessary. 
genhomedircon is a reader, it is using resources outside of the module 
store and is not confined to the sandbox. I don't know that it should be 
inside the transaction.

> Genhomedircon encapsulates an implementation detail of user/seuser 
> updates. Is there another reason for it being outside libsemanage, other 
> than python being easy to work with?
>
Mainly that its already done and works. We really do have higher 
priority things than reimplementing genhomedircon in C to put in 
libsemanage.

--
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.

  reply	other threads:[~2005-11-23 16:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-19  5:50 [SEPOL] Remove defrole from sepol Ivan Gyurdiev
2005-11-21 12:37 ` Ivan Gyurdiev
2005-11-23 11:28 ` Ivan Gyurdiev
2005-11-23 15:32 ` Ivan Gyurdiev
2005-11-23 16:38   ` Joshua Brindle [this message]
2005-11-23 19:52     ` Ivan Gyurdiev
2005-11-23 19:46       ` Joshua Brindle
2005-11-23 20:22         ` Ivan Gyurdiev
2005-11-23 20:57           ` Ivan Gyurdiev
2005-11-23 21:40             ` Joshua Brindle
2005-11-23 21:58       ` Joshua Brindle
2005-11-23 22:35         ` Ivan Gyurdiev
2005-11-25 15:46           ` Joshua Brindle
2005-11-28 19:27 ` Stephen Smalley
2005-11-28 21:22   ` Ivan Gyurdiev

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=43849B20.3090500@tresys.com \
    --to=jbrindle@tresys.com \
    --cc=ivg2@cornell.edu \
    --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.