mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul Moore" <paul.moore@hp.com>
To: Joe Perches <joe@perches.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: [NET]: Mark Paul Moore as maintainer of labelled networking.
Date: Tue, 28 Aug 2007 08:46:13 -0400	[thread overview]
Message-ID: <20070828130813.E6A1D39C199@ldl.fc.hp.com> (raw)
In-Reply-To: <1188283579.6062.12.camel@localhost>

On Tuesday, August 28 2007 2:46:19 am Joe Perches wrote:
> On Tue, 2007-08-28 at 00:01 +0000, Linux Kernel Mailing List wrote:
> > +NETWORKING [LABELED] (NetLabel, CIPSO, Labeled IPsec, SECMARK)
> > +P:	Paul Moore
> > +M:	paul.moore@hp.com
> > +L:	netdev@vger.kernel.org
> > +S:	Maintained
> > +
>
> Aren't there now 2 subsystems in MAINTAINERS for the same thing?
>
> NETLABEL
> P:	Paul Moore
> M:	paul.moore@hp.com
> W:	http://netlabel.sf.net
> L:	netdev@vger.kernel.org
> S:	Supported

Yes and no.  Labeled networking consists of several different subsystems
because the term "labeled networking" can often mean several different
things.  I'll spare everyone the gory details, but if you are interested in
more information check out the SELinux mailing list archives from the past
month; there has been a lot of discussion about the different types of
labeled networking and the requirements/goals of each.

NetLabel is just one subsystem that provides labeled networking
functionality (CIPSO is provided through the NetLabel subsystem), Labeled
IPsec and SECMARK also provide labeled networking functionality.  Originally
I wrote/supported/maintained just NetLabel but over the past weekend James
Morris asked me to look after all of the different labeled networking
subsystems ... for better or worse I agreed :)

If having both a labeled networking and NetLabel maintainer entry is a
problem then how about the patch below?

Index: linux-2.6_maintainers/MAINTAINERS
===================================================================
--- linux-2.6_maintainers.orig/MAINTAINERS
+++ linux-2.6_maintainers/MAINTAINERS
@@ -2609,13 +2609,6 @@ W:	http://www.netfilter.org/
 W:	http://www.iptables.org/
 S:	Supported
 
-NETLABEL
-P:	Paul Moore
-M:	paul.moore@hp.com
-W:	http://netlabel.sf.net
-L:	netdev@vger.kernel.org
-S:	Supported
-
 NETROM NETWORK LAYER
 P:	Ralf Baechle
 M:	ralf@linux-mips.org
@@ -2661,9 +2654,10 @@ L:	netdev@vger.kernel.org
 T:	git kernel.org:/pub/scm/linux/kernel/git/davem/net-2.6.git
 S:	Maintained
 
-NETWORKING [LABELED] (NetLabel, CIPSO, Labeled IPsec, SECMARK)
+NETWORKING [LABELED] (NetLabel/CIPSO, Labeled IPsec, SECMARK)
 P:	Paul Moore
 M:	paul.moore@hp.com
+W:	http://netlabel.sf.net (NetLabel/CIPSO)
 L:	netdev@vger.kernel.org
 S:	Maintained

-- 
paul moore
linux security @ hp


  reply	other threads:[~2007-08-28 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200708280001.l7S01Cxt004543@hera.kernel.org>
2007-08-28  6:46 ` Joe Perches
2007-08-28 12:46   ` Paul Moore [this message]
2007-08-28 16:45     ` Joe Perches
2007-08-28 18:48       ` 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=20070828130813.E6A1D39C199@ldl.fc.hp.com \
    --to=paul.moore@hp.com \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome