All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Brindle <jbrindle@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Paul Moore <paul@paul-moore.com>,
	"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>,
	"method@manicmethod.com" <method@manicmethod.com>
Subject: Re: [PATCH system/core] add iptables secmark labeling script to startup
Date: Tue, 19 Jun 2012 12:29:00 +0000	[thread overview]
Message-ID: <1340109098.3801.9.camel@fedora> (raw)
In-Reply-To: <1340108654.18291.21.camel@moss-pluto.epoch.ncsc.mil>

On Tue, 2012-06-19 at 08:24 -0400, Stephen Smalley wrote:
> On Mon, 2012-06-18 at 11:23 -0400, Joshua Brindle wrote:
> > Paul Moore wrote:
> > > On Saturday, June 16, 2012 02:56:36 PM Joshua Brindle wrote:
> > >> Change-Id: I47100243b04d9629d44c8962eafeacabdcd0e6d2
> > >>
> > >> Signed-off-by: Joshua Brindle<jbrindle@tresys.com>
> > >> ---
> > >>   rootdir/init.rc |    4 ++++
> > >>   1 file changed, 4 insertions(+)
> > >>
> > >> diff --git a/rootdir/init.rc b/rootdir/init.rc
> > >> index 7131095..bd4bc81 100644
> > >> --- a/rootdir/init.rc
> > >> +++ b/rootdir/init.rc
> > >> @@ -372,6 +372,10 @@ service console /system/bin/sh
> > >>       user shell
> > >>       group log
> > >>
> > >> +service netlabels /system/bin/iptables-selinux.sh
> > >> +    class core
> > >> +    oneshot
> > >
> > > I don't know much about Android development or the boot process, but I wonder
> > > if it would make sense to either change the name of the service or the script
> > > it executes.  While the script seems aptly named for its current
> > > functionality, the service name might become a problem if an Android user ever
> > > needs to enable NetLabel support.
> > >
> > > I would suggest either changing the service name to reflect the
> > > secmark/iptables nature of the script or changing the name of the script to
> > > something more generic, e.g. selinux-network.sh, so that it is less awkward if
> > > the script grows at some point to contain secmark labeling rules, NetLabel
> > > configuration, labeled IPsec, etc.
> > >
> > 
> > That is fine. This script generally should just be the initial network state. I 
> > fully expect that VPN apps, etc would have to do runtime label changes, both 
> > using secmark and labeled ipsec.
> 
> Up to you but if you want the script to cover general selinux network
> configuration, you'll want to rename it and re-spin all of the userspace
> patches.  Or you can leave it specific to iptables and just change the
> name of the service in this one patch to fit that purpose.
> 


It makes sense to me to merge 1 service that does selinux network config
instead of trying to merge in one for every aspect of it. I'll respin
all the patches since other changes are necessary anyway. 



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2012-06-19 12:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16 18:56 [PATCH external/sepolicy] Add iptables script to policy Joshua Brindle
2012-06-16 18:56 ` [PATCH build] add iptables-selinux.sh to SELINUX_DEPENDS Joshua Brindle
2012-06-16 18:56 ` [PATCH system/core] add iptables secmark labeling script to startup Joshua Brindle
2012-06-18 15:18   ` Paul Moore
2012-06-18 15:23     ` Joshua Brindle
2012-06-19 12:24       ` Stephen Smalley
2012-06-19 12:29         ` Joshua Brindle [this message]
2012-06-16 18:56 ` [PATCH kernel/tegra] enable secmark labeling for SE Android network access controls Joshua Brindle
2012-06-19 13:26   ` Stephen Smalley
2012-06-19 14:11     ` Joshua Brindle
2012-06-19 14:25       ` Joshua Brindle
2012-06-16 18:56 ` [PATCH kernel/omap] " Joshua Brindle
2012-06-19 13:27   ` Stephen Smalley
2012-06-16 18:56 ` [PATCH kernel/goldfish] " Joshua Brindle
2012-06-19 12:01   ` Stephen Smalley
2012-06-19 19:38     ` Joshua Brindle
2012-06-18 15:25 ` [PATCH external/sepolicy] Add iptables script to policy Paul Moore
2012-06-19 12:22   ` Stephen Smalley

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=1340109098.3801.9.camel@fedora \
    --to=jbrindle@tresys.com \
    --cc=method@manicmethod.com \
    --cc=paul@paul-moore.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    /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.