All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul.moore@hp.com>
To: "David P. Quigley" <dpquigl@tycho.nsa.gov>
Cc: Casey Schaufler <casey@schaufler-ca.com>,
	Daniel J Walsh <dwalsh@redhat.com>,
	Paul Nuzzi <pjnuzzi@tycho.ncsc.mil>,
	russell@coker.com.au, selinux@tycho.nsa.gov,
	LSM <linux-security-module@vger.kernel.org>
Subject: Re: [PATCH] Dynamic port labeling V2
Date: Thu, 3 Dec 2009 17:43:42 -0500	[thread overview]
Message-ID: <200912031743.42195.paul.moore@hp.com> (raw)
In-Reply-To: <1259856069.8497.56.camel@moss-terrapins.epoch.ncsc.mil>

On Thursday 03 December 2009 11:01:09 am David P. Quigley wrote:
> On Wed, 2009-12-02 at 19:37 -0800, Casey Schaufler wrote:
> > Now I'm glad the notion has been considered, and I can understand
> > if it seems like too much work or if you just don't see it as a good
> > idea.
> >
> > How about making it a part of the labeled networking code then?
> > That would seem to be a more focused approach that would also,
> > and perhaps better, address the generality concern.
> 
> I'd consider talking to Paul Moore about it and getting his input then
> as I'm just a filesystem guy :)

Okay, I stopped following this thread closely several messages ago but I saw 
"labeled networking" then my name so I figured I should probably say something 
constructive :) [NOTE: I did actually review the first set of patches to 
ensure they flushed the SELinux port caches, which they did - good job]

Anyway, I digress ... labeling network ports isn't really labeled networking 
in the sense that labeled networking tends to be about communicating security 
label information across the network.  While I won't close the door on this 
completely, I will say that someone is going to have to make a very persuasive 
argument as to why port labeling belongs in the labeled networking code ... 
and also preferably how you would establish a LSM agnostic method of labeling 
ports.

Good luck with that last bit :) 

-- 
paul moore
linux @ 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.

  reply	other threads:[~2009-12-03 22:43 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 21:27 [PATCH] Dynamic port labeling V2 Paul Nuzzi
2009-11-30 21:27 ` Paul Nuzzi
2009-12-01  4:52 ` Casey Schaufler
2009-12-01  4:52   ` Casey Schaufler
2009-12-01 15:06   ` David P. Quigley
2009-12-01 15:06     ` David P. Quigley
2009-12-01 15:29     ` Paul Nuzzi
2009-12-01 15:29       ` Paul Nuzzi
2009-12-02  2:38       ` Casey Schaufler
2009-12-02  2:38         ` Casey Schaufler
2009-12-01 17:50     ` Russell Coker
2009-12-01 19:14       ` Paul Nuzzi
2009-12-01 22:45         ` Daniel J Walsh
2009-12-01 23:07           ` David P. Quigley
2009-12-02  5:43             ` Casey Schaufler
2009-12-02 21:52               ` David P. Quigley
2009-12-03  3:37                 ` Casey Schaufler
2009-12-03 16:01                   ` David P. Quigley
2009-12-03 22:43                     ` Paul Moore [this message]
2009-12-04  2:32                     ` Casey Schaufler
2009-12-01 23:03       ` David P. Quigley
2009-12-03 19:31 ` Joshua Brindle
2009-12-03 19:31   ` Joshua Brindle
2009-12-04  0:12   ` Russell Coker
2009-12-04  0:12     ` Russell Coker
2009-12-04 14:30   ` Paul Nuzzi
2009-12-04 14:30     ` Paul Nuzzi
2009-12-04 16:03     ` Joshua Brindle
2009-12-04 16:03       ` Joshua Brindle
2009-12-07 17:21       ` Paul Nuzzi
2009-12-07 17:21         ` Paul Nuzzi
2009-12-18 15:38         ` Joshua Brindle
2009-12-18 15:38           ` Joshua Brindle
2009-12-18  5:33       ` Kyle Moffett
2009-12-18  5:33         ` Kyle Moffett
2009-12-18 18:46         ` Paul Moore
2009-12-18 18:46           ` 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=200912031743.42195.paul.moore@hp.com \
    --to=paul.moore@hp.com \
    --cc=casey@schaufler-ca.com \
    --cc=dpquigl@tycho.nsa.gov \
    --cc=dwalsh@redhat.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=pjnuzzi@tycho.ncsc.mil \
    --cc=russell@coker.com.au \
    --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.