All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v2 2/2] Allow init scripts to create /run/mysqld and /run/dbus
Date: Tue, 7 Aug 2012 14:28:22 -0400	[thread overview]
Message-ID: <50215E46.5020507@tresys.com> (raw)
In-Reply-To: <1344362663.2306.9.camel@d30.localdomain>

On 08/07/12 14:04, Dominick Grift wrote:
> On Tue, 2012-08-07 at 19:59 +0200, Sven Vermeulen wrote:
>> On Tue, Aug 7, 2012 at 7:42 PM, Christopher J. PeBenito
>> <cpebenito@tresys.com> wrote:
>>>> So if an init script, named init script, application domain or user
>>>> does something like "mkdir /run/mysqld" then it automatically becomes
>>>> mysqld_var_run_t.
>>>
>>> Well I wouldn't go with the above because its way too broad, unnecessarily gives
>>> access to all domains, and breaks encapsulation.  But the idea might make more
>>> sense if we create a daemon pid file concept and allow initrc_t to create all daemon
>>> pid file dirs.  It would be similarly structured as your above examples.
>>
>> I generally agree, but there are probably many "corner cases". I
>> mentioned one for DHCP before (which needs it instead of initrc_t),
>> another one is in the pipeline (tor, gentoo bug #429486). I imagine
>> there are quite a few others as well.
>>
>> However, the "corner cases" don't have the downside of having three
>> different parties (initrc_t, var_run_t, <domain>_var_run_t) so can be
>> more easily updated:
>> files_pid_filetrans(tor_t, tor_var_run_t, dir, "tor") in tor.te
>> (assuming this is what the bug is about, haven't seen it in detail
>> yet).
>>
>> I'll try with daemonpidfile and see how far we get.
> 
> About initrc_t creating all these objects on /run and other tmpfs.
> 
> I think we should make that conditional.
> 
> Reasons:
> 
> Not all systems use /run (older systems probably don't have run)
> In systems with systemd, systemd-tmpfilesd takes care of creation of
> this content.
> 
> Although the initrc_t domain is considered trusted anyways. So i am not
> sure. Your input on this issue?

Its a valid point, but my current feeling is that its ok.  Just as you say, initrc_t is trusted.  If it is doing bad things, the system is in bad shape and extra directory creation perms in (/var)?/run is the least of your concerns.  If its a concern, we could always move to init script domains (eg httpd_initrc_t).  Thats a significant effort, but it would separate out a bunch of initrc_t's permissions.

-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  reply	other threads:[~2012-08-07 18:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 17:46 [refpolicy] [PATCH v2 0/2] More /run changes Sven Vermeulen
2012-07-31 17:46 ` [refpolicy] [PATCH v2 1/2] DHCP client's hooks create /run/dhcpc directory Sven Vermeulen
2012-08-07 17:22   ` Christopher J. PeBenito
2012-07-31 17:46 ` [refpolicy] [PATCH v2 2/2] Allow init scripts to create /run/mysqld and /run/dbus Sven Vermeulen
2012-08-07 17:20   ` Christopher J. PeBenito
2012-08-07 17:35     ` Sven Vermeulen
2012-08-07 17:42       ` Christopher J. PeBenito
2012-08-07 17:59         ` Sven Vermeulen
2012-08-07 18:04           ` Dominick Grift
2012-08-07 18:28             ` Christopher J. PeBenito [this message]
2012-08-10 17:28         ` Sven Vermeulen
2012-08-14 12:19           ` Christopher J. PeBenito

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=50215E46.5020507@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.