All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Venkat Yekkirala <vyekkirala@TrustedCS.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Joshua Brindle <method@gentoo.org>,
	netdev@vger.kernel.org, selinux@tycho.nsa.gov,
	kmacmillan@mentalrootkit.com
Subject: Re: [PATCH 7/7] secid reconciliation-v03: Enforcement for SELinux
Date: Fri, 29 Sep 2006 16:09:15 -0400	[thread overview]
Message-ID: <451D7D6B.9010900@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609291557520.8199@d.namei>

James Morris wrote:
> On Fri, 29 Sep 2006, Paul Moore wrote:
>>>... or you get no CIPSO label (e.g. ICMP from intermediate router) ...
>>
>>If there is no packet label that NetLabel recognizes and NetLabel is
>>configured to allow unlabeled traffic then the NetLabel SID generated in
>>step #1 above would be 0.
> 
> 
> Well, conntrack will say that this packet is related to the connection 
> and CONNSECMARK will restore the secmark label to it (i.e. it'll have the 
> same secmark as the initial syn packet).  But, no CIPSO label.  I guess 
> this needs to be considered in any case, secmark or not.

Yep, I would categorize this case as 'external label not present,
internal label present'.  I believe the code as described would do the
right thing in allowing admins to control this, it's just up to how you
configure the system and what your policy dictates.

-- 
paul moore
linux security @ hp

--
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.

WARNING: multiple messages have this Message-ID (diff)
From: Paul Moore <paul.moore@hp.com>
To: James Morris <jmorris@namei.org>
Cc: Venkat Yekkirala <vyekkirala@TrustedCS.com>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Joshua Brindle <method@gentoo.org>,
	netdev@vger.kernel.org, selinux@tycho.nsa.gov,
	kmacmillan@mentalrootkit.com
Subject: Re: [PATCH 7/7] secid reconciliation-v03: Enforcement for SELinux
Date: Fri, 29 Sep 2006 16:09:15 -0400	[thread overview]
Message-ID: <451D7D6B.9010900@hp.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0609291557520.8199@d.namei>

James Morris wrote:
> On Fri, 29 Sep 2006, Paul Moore wrote:
>>>... or you get no CIPSO label (e.g. ICMP from intermediate router) ...
>>
>>If there is no packet label that NetLabel recognizes and NetLabel is
>>configured to allow unlabeled traffic then the NetLabel SID generated in
>>step #1 above would be 0.
> 
> 
> Well, conntrack will say that this packet is related to the connection 
> and CONNSECMARK will restore the secmark label to it (i.e. it'll have the 
> same secmark as the initial syn packet).  But, no CIPSO label.  I guess 
> this needs to be considered in any case, secmark or not.

Yep, I would categorize this case as 'external label not present,
internal label present'.  I believe the code as described would do the
right thing in allowing admins to control this, it's just up to how you
configure the system and what your policy dictates.

-- 
paul moore
linux security @ hp

  reply	other threads:[~2006-09-29 20:09 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-29 16:27 [PATCH 7/7] secid reconciliation-v03: Enforcement for SELinux Venkat Yekkirala
2006-09-29 16:27 ` Venkat Yekkirala
2006-09-29 16:31 ` Paul Moore
2006-09-29 16:31   ` Paul Moore
2006-09-29 16:50   ` James Morris
2006-09-29 16:50     ` James Morris
2006-09-29 17:32     ` James Morris
2006-09-29 17:32       ` James Morris
2006-09-29 17:50       ` Paul Moore
2006-09-29 17:50         ` Paul Moore
2006-09-29 17:43     ` Paul Moore
2006-09-29 17:43       ` Paul Moore
2006-09-29 18:41       ` James Morris
2006-09-29 18:41         ` James Morris
2006-09-29 19:06         ` Paul Moore
2006-09-29 19:06           ` Paul Moore
2006-09-29 19:33           ` James Morris
2006-09-29 19:33             ` James Morris
2006-09-29 19:51             ` Paul Moore
2006-09-29 19:51               ` Paul Moore
2006-09-29 20:04               ` James Morris
2006-09-29 20:04                 ` James Morris
2006-09-29 20:09                 ` Paul Moore [this message]
2006-09-29 20:09                   ` Paul Moore
  -- strict thread matches above, loose matches on Subject: below --
2006-10-01 21:30 Venkat Yekkirala
2006-10-01 21:30 ` Venkat Yekkirala
2006-09-29 22:10 Venkat Yekkirala
2006-09-29 22:10 ` Venkat Yekkirala
2006-09-29 21:54 Venkat Yekkirala
2006-09-29 21:54 ` Venkat Yekkirala
2006-09-29 18:50 Venkat Yekkirala
2006-09-29 18:50 ` Venkat Yekkirala
2006-09-29 19:13 ` Paul Moore
2006-09-29 19:13   ` Paul Moore
2006-09-29 17:27 Venkat Yekkirala
2006-09-29 17:27 ` Venkat Yekkirala
2006-09-29 17:38 ` Paul Moore
2006-09-29 17:38   ` Paul Moore
2006-09-29 16:22 Venkat Yekkirala
2006-09-29 16:22 ` Venkat Yekkirala
2006-09-29 16:17 Venkat Yekkirala
2006-09-29 16:17 ` Venkat Yekkirala
2006-09-29 16:09 Venkat Yekkirala
2006-09-29 16:09 ` Venkat Yekkirala
2006-09-29 16:13 ` Paul Moore
2006-09-29 16:13   ` Paul Moore
2006-09-29  2:33 Venkat Yekkirala
2006-09-29  2:33 ` Venkat Yekkirala
2006-09-29  3:52 ` Joshua Brindle
2006-09-29  3:52   ` Joshua Brindle
2006-09-29 12:59   ` Stephen Smalley
2006-09-29 12:59     ` Stephen Smalley
2006-09-29 14:00     ` Joshua Brindle
2006-09-29 14:00       ` Joshua Brindle
2006-09-29 14:28       ` Stephen Smalley
2006-09-29 14:28         ` Stephen Smalley
2006-09-29 14:33         ` James Morris
2006-09-29 14:33           ` James Morris
2006-09-29 14:39           ` Stephen Smalley
2006-09-29 14:39             ` Stephen Smalley
2006-09-29 16:06             ` Paul Moore
2006-09-29 16:06               ` Paul Moore
2006-09-29 16:10               ` James Morris
2006-09-29 16:10                 ` James Morris
2006-09-29 16:15                 ` Paul Moore
2006-09-29 16:15                   ` Paul Moore
2006-09-29 16:39 ` Paul Moore
2006-09-29 16:39   ` Paul Moore

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=451D7D6B.9010900@hp.com \
    --to=paul.moore@hp.com \
    --cc=jmorris@namei.org \
    --cc=kmacmillan@mentalrootkit.com \
    --cc=method@gentoo.org \
    --cc=netdev@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=vyekkirala@TrustedCS.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.