From: Joshua Brindle <jbrindle@tresys.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Stephen Smalley <sds@tycho.nsa.gov>, SELinux@tycho.nsa.gov
Subject: Re: [ SEMANAGE ] Install seusers, rename some files
Date: Tue, 01 Nov 2005 16:02:23 -0500 [thread overview]
Message-ID: <4367D7DF.7080504@tresys.com> (raw)
In-Reply-To: <4367D674.4060004@cornell.edu>
Ivan Gyurdiev wrote:
> Ivan Gyurdiev wrote:
>
>>
>>> I'm not sure about this; at present, it has the side effect that a
>>> semodule -b base.pp will fail upon the attempt to copy seusers (because
>>> there isn't one in the sandbox presently, not even an empty stub).
>>
>> Yes, the seusers from /etc/selinux/strict/seusers have to get in the
>> sandbox somehow...
>> I'm not entirely sure how, but I think Tresys has indicated that
>> should occur through the APIs, rather than by copying it in.
>>
>> This is only necessary for migration...
>
> So, the question of what should be done about this still stands -
> Joshua? From the point of view of libsemanage, a commit with a missing
> seusers file should fail, because the store should hold the
> authoritative copy of this file, and it's an important file, so it seems
> like lack of it should be considered fatal...there should at least be a
> default entry?
>
This is really saying that libsemanage knows what libselinux needs,
which I'm not sure is appropriate, because libselinux might not be
looking in seuser at all for mappings, it could be looking in LDAP.
I don't think this is a fatal error during commit.
> How will the store be initialized? Seems like this should possibly be
> done in the libsemanage post script? Any callers of the library should
> already have the store be in good state for use.
>
>
This is a question we should be answering soon. There are a couple
options but because of time constraints on FC5 test 1 it will probably
be the base rpm putting stuff in there directly, at least for now. The
ideal way would be to bootstrap the whole thing through libsemanage but
there is bit of work to be done before this is possible.
--
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.
next prev parent reply other threads:[~2005-11-01 21:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 1:12 [ SEMANAGE ] Install seusers, rename some files Ivan Gyurdiev
2005-11-01 20:10 ` Stephen Smalley
2005-11-01 20:34 ` Ivan Gyurdiev
2005-11-01 20:41 ` Stephen Smalley
2005-11-01 21:12 ` Ivan Gyurdiev
2005-11-01 21:05 ` Joshua Brindle
2005-11-01 21:42 ` Ivan Gyurdiev
2005-11-01 21:40 ` Stephen Smalley
2005-11-01 21:08 ` Stephen Smalley
2005-11-01 21:11 ` Stephen Smalley
2005-11-01 21:31 ` Ivan Gyurdiev
2005-11-01 21:27 ` Stephen Smalley
2005-11-01 21:15 ` Ivan Gyurdiev
2005-11-01 20:56 ` Ivan Gyurdiev
2005-11-01 21:02 ` Joshua Brindle [this message]
2005-11-01 21:10 ` Stephen Smalley
2005-11-01 21:20 ` Ivan Gyurdiev
2005-11-01 21:11 ` Joshua Brindle
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=4367D7DF.7080504@tresys.com \
--to=jbrindle@tresys.com \
--cc=SELinux@tycho.nsa.gov \
--cc=ivg2@cornell.edu \
--cc=sds@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.