From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
SELinux-dev@tresys.com, Joshua Brindle <jbrindle@tresys.com>,
SE Linux <selinux@tycho.nsa.gov>
Subject: Re: rawhide targeted vs. refpolicy rpm
Date: Tue, 15 Nov 2005 14:50:18 -0500 [thread overview]
Message-ID: <437A3BFA.1080901@cornell.edu> (raw)
In-Reply-To: <1132081420.28124.80.camel@moss-spartans.epoch.ncsc.mil>
>
>> Ok, so perhaps what we need is a new semanage policy component that
>> provides libsemanage with:
>> a) default role (or use default_contexts to determine), and
>> b) home directory type prefix for that role, which can be different from
>> the role prefix itself.
>>
>> And then have libsemanage export an interface to genhomedircon to obtain
>> the home directory type prefix for use in generating the file contexts
>> rather than using the role prefix itself.
>>
>
> Is there agreement on this direction? Is anyone working on this issue
> yet?
>
I am very confused..
1. The reason we designate a role as a "default" role is to get the
labeling prefix. If we already have the labeling prefix, why do we still
want to keep a "default" role around?
2. The labeling prefix has so far been tied to the user (map is
seuser->user->(fixed) role -> labeing prefix). Now you're saying the
login context should play a role in determining the labeling prefix? How
would this work? Which login context from default_contexts should be used?
3. Is there documentation on default_contexts, and how to work with it?
--
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-15 19:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BF9A263D.7FFA%csellers@tresys.com>
[not found] ` <4374BDEC.4050600@redhat.com>
[not found] ` <200511111717.16542.csellers@tresys.com>
[not found] ` <200511141041.49643.csellers@tresys.com>
[not found] ` <1131983537.5415.137.camel@moss-spartans.epoch.ncsc.mil>
2005-11-14 16:17 ` rawhide targeted vs. refpolicy rpm Daniel J Walsh
2005-11-14 16:51 ` Stephen Smalley
2005-11-14 18:23 ` Daniel J Walsh
2005-11-14 19:32 ` Stephen Smalley
2005-11-15 13:23 ` Stephen Smalley
2005-11-14 16:59 ` Joshua Brindle
2005-11-14 18:27 ` Daniel J Walsh
2005-11-14 19:37 ` Stephen Smalley
2005-11-15 11:17 ` Stephen Smalley
2005-11-15 13:40 ` Stephen Smalley
2005-11-15 14:44 ` Daniel J Walsh
2005-11-15 14:57 ` Stephen Smalley
2005-11-15 15:10 ` Stephen Smalley
2005-11-15 15:18 ` Stephen Smalley
2005-11-15 19:03 ` Stephen Smalley
2005-11-15 19:28 ` Joshua Brindle
2005-11-16 13:12 ` Stephen Smalley
2005-11-15 19:50 ` Ivan Gyurdiev [this message]
2005-11-16 13:11 ` Stephen Smalley
2005-11-16 13:42 ` Ivan Gyurdiev
2005-11-16 13:42 ` Stephen Smalley
2005-11-16 14:08 ` Ivan Gyurdiev
2005-11-16 14:14 ` Stephen Smalley
2005-11-16 14:27 ` Ivan Gyurdiev
2005-11-16 14:26 ` Stephen Smalley
2005-11-16 14:47 ` Ivan Gyurdiev
2005-11-16 14:53 ` Ivan Gyurdiev
2005-11-14 17:28 ` Ivan Gyurdiev
2005-11-14 18:09 ` I have modified Joshua's libsemanage-swigify patch to work better in my spec file Daniel J Walsh
2005-11-15 13:21 ` Stephen Smalley
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=437A3BFA.1080901@cornell.edu \
--to=ivg2@cornell.edu \
--cc=SELinux-dev@tresys.com \
--cc=dwalsh@redhat.com \
--cc=jbrindle@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.