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 1/1] Allow udev to launch init scripts (f.i. on	network module load)
Date: Wed, 16 Feb 2011 09:28:10 -0500	[thread overview]
Message-ID: <4D5BDEFA.5070301@tresys.com> (raw)
In-Reply-To: <20110214185107.GB13533@siphos.be>

On 02/14/11 13:51, Sven Vermeulen wrote:
> On Mon, Feb 14, 2011 at 08:41:54AM -0500, Christopher J. PeBenito wrote:
>>> In Gentoo (the patch only includes the line in a distro_gentoo section), the
>>> (default installed) 90-network.rules calls the /etc/init.d/net.<interface>
>>> init script when a network subsystem is added or removed.
>>
>> I believe he is saying that the scripts should be labeled, not that 
>> you're missing a description (though thats important too).
> 
> Well, the /etc/init.d/net.<interface> scripts are symlinks to a script
> labelled initrc_exec_t as one would imagine from an init script. udev itself
> (running in udev_t domain) calls a wrapper script net.sh (labelled bin_t). 
> 
> You'd rather see this wrapper script be labelled something like
> udev_net_exec_t which transitions to udev_net_t which then calls the
> net.<interface> script (initrc_exec_t) which transitions to initrc_t ?

Making something like network_initrc_exec_t and labeling all the basic
networking scripts with it, and then transitioning to initrc_t is what
we mean.

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

      reply	other threads:[~2011-02-16 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 18:20 [refpolicy] [PATCH 1/1] Allow udev to launch init scripts (f.i. on network module load) Sven Vermeulen
2011-02-02 18:23 ` Daniel J Walsh
2011-02-02 18:38   ` Sven Vermeulen
2011-02-14 13:41     ` Christopher J. PeBenito
2011-02-14 18:51       ` Sven Vermeulen
2011-02-16 14:28         ` Christopher J. PeBenito [this message]

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=4D5BDEFA.5070301@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.