From: sds@tycho.nsa.gov (Stephen Smalley)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Transition unconfined users to dpkg_t domain
Date: Thu, 09 Jan 2014 15:32:03 -0500 [thread overview]
Message-ID: <52CF0743.4050305@tycho.nsa.gov> (raw)
In-Reply-To: <52CF05E6.7070904@redhat.com>
On 01/09/2014 03:26 PM, Daniel J Walsh wrote:
> On 01/09/2014 11:36 AM, Dominick Grift wrote:
>> On Thu, 2014-01-09 at 17:19 +0100, Laurent Bigonville wrote:
>
>>>
>>> Actually it's the same code as rpm currently uses.
>>>
>>> It looks at the fcontext of the script then uses secure_compute_create to
>>> see if a transition would occures. If it's the case it will make it
>>> transition to that context, otherwise it's indeed using a hardcoded
>>> context.
>
>> hard-coding configurable security identifiers is bad practice. I would not
>> look too much to Fedora.
>
>> In /etc/selinux there are config files that tell selinux aware programs
>> what context to use in what situations. Programs should consult those
>> config files, then use that information to determine whether to transition
>> or not, and where to.
>
>> Disclaimer: thats just my opinion
>
>> _______________________________________________ refpolicy mailing list
>> refpolicy at oss.tresys.com http://oss.tresys.com/mailman/listinfo/refpolicy
>
> It has been like that for years. Might have been a chicken and egg problem on
> initial install. RPM Now has better flexibility.
bootstrapping issue - needed to know the right domain prior to any
policy files being installed on the filesystem.
next prev parent reply other threads:[~2014-01-09 20:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 12:29 [refpolicy] Transition unconfined users to dpkg_t domain Laurent Bigonville
[not found] ` <CAPzO=NxbnkP-M-GJhDxW4w=5q7Q6xWgG=m3J1p09ETTs-HuzNw@mail.gmail.com>
[not found] ` <20140107181207.13f8826d@soldur.bigon.be>
2014-01-09 12:24 ` Laurent Bigonville
2014-01-09 13:46 ` Dominick Grift
2014-01-09 15:57 ` Laurent Bigonville
2014-01-09 16:12 ` Dominick Grift
2014-01-09 16:19 ` Laurent Bigonville
2014-01-09 16:36 ` Dominick Grift
2014-01-09 20:26 ` Daniel J Walsh
2014-01-09 20:32 ` Stephen Smalley [this message]
2014-01-10 11:47 ` Laurent Bigonville
2014-01-10 13:49 ` Daniel J Walsh
2014-01-10 14:51 ` Stephen Smalley
2014-01-10 14:59 ` Daniel J Walsh
2014-01-10 17:27 ` Laurent Bigonville
2014-01-10 17:37 ` Stephen Smalley
2014-01-10 18:39 ` Sven Vermeulen
2014-01-10 18:40 ` Stephen Smalley
2014-01-10 18:46 ` Sven Vermeulen
2014-01-10 19:19 ` Dominick Grift
2014-01-12 0:59 ` Russell Coker
2014-01-12 12:23 ` Dominick Grift
2014-01-13 12:35 ` Russell Coker
2014-01-10 18:52 ` Dominick Grift
2014-01-10 19:58 ` Stephen Smalley
2014-01-12 1:04 ` Russell Coker
2014-01-12 12:25 ` Dominick Grift
2014-01-12 12:20 ` Laurent Bigonville
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=52CF0743.4050305@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--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.