lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 28 Aug 2007 08:46:13 -0400
From:	"Paul Moore" <paul.moore@...com>
To:	Joe Perches <joe@...ches.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	netdev@...r.kernel.org
Subject: Re: [NET]: Mark Paul Moore as maintainer of labelled networking.

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@...com
> > +L:	netdev@...r.kernel.org
> > +S:	Maintained
> > +
>
> Aren't there now 2 subsystems in MAINTAINERS for the same thing?
>
> NETLABEL
> P:	Paul Moore
> M:	paul.moore@...com
> W:	http://netlabel.sf.net
> L:	netdev@...r.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@...com
-W:	http://netlabel.sf.net
-L:	netdev@...r.kernel.org
-S:	Supported
-
 NETROM NETWORK LAYER
 P:	Ralf Baechle
 M:	ralf@...ux-mips.org
@@ -2661,9 +2654,10 @@ L:	netdev@...r.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@...com
+W:	http://netlabel.sf.net (NetLabel/CIPSO)
 L:	netdev@...r.kernel.org
 S:	Maintained

-- 
paul moore
linux security @ hp

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ