All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Paul Moore <paul@paul-moore.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	SELinux Mail List <selinux@tycho.nsa.gov>
Subject: Re: RFC: packet checks always on option
Date: Tue, 15 May 2012 09:24:20 -0400	[thread overview]
Message-ID: <4FB25904.5020401@tresys.com> (raw)
In-Reply-To: <12617452.LZMSpbtozB@sifl>

On 05/14/12 17:15, Paul Moore wrote:
> On Monday, May 14, 2012 01:17:30 PM Stephen Smalley wrote:
>> Didn't the old behavior lead to the undesirable result that refpolicy
>> allows every domain (or at least every domain that does networking) to
>> send/recv unlabeled packets, such that you cannot effectively employ
>> SECMARK unless you first modify and rebuild your entire policy to take
>> away the unlabeled packet access?  Whereas with the new behavior one
>> could drop those rules and then when someone does enable SECMARK, they
>> get to fully define the allowable network traffic?
> 
> Yep.

Not any worse than with the old networking checks.  Refpolicy has netif_t and node_t access for every networking domain too.  If you fully define your SECMARK rules, then there wouldn't be any unlabeled_t packets.  Similarly, if you fully described everything with netifcons and nodecons, you wouldn't get checks on netif_t and node_t.  My argument is for the people that care about this and would likely be modifying their policy to strip out the unlabeled packet access anyway.
  
>> I'm not adverse to making it optional/configurable, but I think a policy
>> capability is how you should do it.  That is what they are for, and they
>> are supposed to provide a more explicit mechanism than either the
>> handle_unknown logic or the old compat_net logic ...
> 
> *If* we decide to go this route, I agree, policy capabilities seem to be the 
> best fit.
> 
> However, as I said earlier in my emails to Chris, I'm still not certain this 
> actually accomplishes anything useful.

I don't understand how you can say this doesn't accomplish anything useful.  You don't want an *option* for changing the behavior of an enabled mechanism (SECMARK), and then in another email you're suggesting adding an additional mechanism (labeled ipsec/netlabel), which would otherwise be unused (assuming you're turning it on just to handle the situations I'm mentioning).

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

--
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-05-15 13:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 16:58 RFC: packet checks always on option Christopher J. PeBenito
2012-05-10 20:02 ` Paul Moore
2012-05-14 12:52   ` Christopher J. PeBenito
2012-05-14 15:35     ` Paul Moore
2012-05-14 16:42       ` Chad Hanson
2012-05-14 20:54         ` Paul Moore
2012-05-14 17:17 ` Stephen Smalley
2012-05-14 17:22   ` Stephen Smalley
2012-05-14 21:15   ` Paul Moore
2012-05-15 13:24     ` Christopher J. PeBenito [this message]
2012-05-15 14:13       ` Paul Moore
2012-05-15 14:47         ` Christopher J. PeBenito
2012-05-15 15:04           ` Paul Moore
2012-05-15 15:46             ` Christopher J. PeBenito
2012-05-15 18:45               ` Paul Moore
2012-05-17 14:06                 ` david caplan
2012-05-17 14:42                   ` Paul Moore
2012-05-17 15:31                     ` david caplan
2012-05-17 16:51                       ` Paul Moore
2012-05-16  2:18           ` Daniel J Walsh

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=4FB25904.5020401@tresys.com \
    --to=cpebenito@tresys.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.