From: sds@tycho.nsa.gov (Stephen Smalley)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Transition unconfined users to dpkg_t domain
Date: Fri, 10 Jan 2014 12:37:08 -0500 [thread overview]
Message-ID: <52D02FC4.7030109@tycho.nsa.gov> (raw)
In-Reply-To: <20140110182732.3c6f298a@soldur.bigon.be>
On 01/10/2014 12:27 PM, Laurent Bigonville wrote:
> Le Fri, 10 Jan 2014 09:51:17 -0500,
> Stephen Smalley <sds@tycho.nsa.gov> a ?crit :
>
>> On 01/10/2014 06:47 AM, Laurent Bigonville wrote:
>>> Le Thu, 09 Jan 2014 15:32:03 -0500,
>>> Stephen Smalley <sds@tycho.nsa.gov> a ?crit :
>>>
>>>> On 01/09/2014 03:26 PM, Daniel J Walsh wrote:
>>>>>
>>>>> 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.
>>>
>>> Does that means that rpm and dpkg are supposed to work even if the
>>> files in /etc/selinux/<my_current_policy> are missing?
>>>
>>> With dpkg (that use the rpm_execcon-like function) I'm getting the
>>> following error in that case:
>>> cannot get security labeling handle: No such file or directory
>>
>> I think they always set down a pre-generated file_contexts file just
>> for that purpose, but otherwise weren't guaranteed any other config
>> files. But that was all the original rpm selinux integration; I don't
>> know the current state of things.
>
> Thanks.
>
> About my initial issue with dpkg exiting if it cannot transition to
> "dpkg_script_t" from unconfined users. How do you think this should be
> solved? People doesn't like the transition of unconfined domains to
> confined ones (I agree with this), so you think this should be fixed in
> the code (setexecfilecon() or dpkg) or this could achieved in an other
> way in the policy?
What's wrong with transitioning from unconfined to confined? Going from
more-privileged to less-privileged is the common (and safe) case, e.g.
init -> daemon, login -> user, etc. It is confined -> unconfined
transitions that are unsafe.
next prev parent reply other threads:[~2014-01-10 17:37 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
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 [this message]
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=52D02FC4.7030109@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.