From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Do we need to keep "aliased" interfaces?
Date: Mon, 2 Jun 2014 11:12:44 -0400 [thread overview]
Message-ID: <538C946C.30601@tresys.com> (raw)
In-Reply-To: <1401447241.7153.3.camel@x220.localdomain>
On 05/30/2014 06:54 AM, Dominick Grift wrote:
> On Fri, 2014-05-30 at 12:48 +0200, Sven Vermeulen wrote:
>
>>
>> But are prefix domains still something we want to work on? I thought that
>> proper desktop confinement is better done using the user-based access
>> control constraints.
>
> I will leave that decision to you and others
>
> My opinion though:
> UBAC does not deal with the fact that we need to be able to tell selinux
> when a confined domain needs to execute an file in a calling user domain
> (or another confined domain type derived from the calling user domain)
The preference would be to keep a common domain and separate it with UBAC except for the cases, as Dominick states, have type transition problems. Su and sudo are examples where the domains are essentially equivalent, but they have derived types so the default transition is back to the calling domain on shell exec().
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-06-02 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 16:57 [refpolicy] Do we need to keep "aliased" interfaces? Sven Vermeulen
2014-05-30 10:29 ` Dominick Grift
2014-05-30 10:48 ` Sven Vermeulen
2014-05-30 10:54 ` Dominick Grift
2014-06-02 15:12 ` Christopher J. PeBenito [this message]
2014-05-30 11:01 ` Dominick Grift
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=538C946C.30601@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/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.