From: Daniel J Walsh <dwalsh@redhat.com>
To: Ivan Gyurdiev <ivg2@cornell.edu>
Cc: Joshua Brindle <jbrindle@tresys.com>,
selinux@tycho.nsa.gov, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [SEMANAGE] User extra data (part 1)
Date: Sat, 14 Jan 2006 00:26:44 -0500 [thread overview]
Message-ID: <43C88B94.8030804@redhat.com> (raw)
In-Reply-To: <43C6DF28.2080500@cornell.edu>
Ivan Gyurdiev wrote:
>
>>
>> I really don't want to export a whole slew of extra interfaces for
>> dealing with system level stuff so some of the options are
>>
>> 1) letting rpm/whatever be trusted to smash things in the store
>> (non-ideal)
>>
>> 2) Write an 'import' interface that tells semanage to grab all the
>> system files from somewhere and smash the ones in the store (sort of
>> hackish)
>>
>> 3) add user_extra.system to the policy package and smash it on base
>> policy upgrade (this is my favorite)
> I have no preference... Dan?
>
I really don't understand what you are trying to do here.
We are trying to build a mapping between SELinux User and default login
type? Correct? But there is a relationship between the default login
role and the type. SO I guess I have no preference. The current
policycoreutils is hacked to select user for user_u and staff for root
or staff_u in non targeted policy.
--
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:[~2006-01-14 5:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 4:57 [SEMANAGE] User extra data (part 1) Ivan Gyurdiev
2006-01-10 5:48 ` Ivan Gyurdiev
2006-01-13 13:50 ` Stephen Smalley
2006-01-10 15:37 ` Joshua Brindle
2006-01-12 22:58 ` Ivan Gyurdiev
2006-01-14 5:26 ` Daniel J Walsh [this message]
2006-01-14 6:39 ` 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=43C88B94.8030804@redhat.com \
--to=dwalsh@redhat.com \
--cc=ivg2@cornell.edu \
--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.