linux-kernel - Re: [NET]: Mark Paul Moore as maintainer of labelled networking.

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] [day] [month] [year] [list]

Message-Id: <200708281448.15537.paul.moore@hp.com>
Date:	Tue, 28 Aug 2007 14:48:14 -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 12:45:50 pm Joe Perches wrote:
> On Tue, 2007-08-28 at 08:46 -0400, Paul Moore wrote:
> > If having both a labeled networking and NetLabel maintainer entry is a
> > problem then how about the patch below?
>
> I don't think it is.
>
> > -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
>
> My preference would be for something like:
>
>         NETLABEL and CIPSO
>         P:	Paul Moore
>         M:	paul.moore@...com
>         W:	http://netlabel.sf.net
>         L:	netdev@...r.kernel.org
>         S:	Maintained
>         F:	Documentation/netlabel/
>         F:	include/net/netlabel.h
>         F:	net/netlabel/
>
>         Labeled IPsec and SECMARK
>         P:	Paul Moore
>         M:	paul.moore@...com
>         L:	netdev@...r.kernel.org
>         S:	Supported
>         F:	include/linux/netfilter/*SECMARK*
>         F:	net/netfilter/*SECMARK*
>
> I would like to add appropriate file patterns for each
> block.  Also, I'm not sure of the Supported/Maintained
> status of each block.

>From the little bit of the discussion that I saw a few weeks ago the idea of 
file patterns in the MAINTAINERS file didn't go over very well.  I still 
don't see the "F" field specified/described at the top of the file.

As long as it is not a problem to have two maintainer entries, I think James' 
patch (what it currently in-tree) is pretty good right now - it fits with the 
rest of the NETWORKING [*] entries and looks correct to me.

> The distinction is supposed to be:
>
>         Supported:	Someone is actually paid to look after this.
>         Maintained:	Someone actually looks after it.
>
> Could you please clarify those for me?

Sure.  HP is my current employer, i.e. they pay me, and both myself and HP 
have pledged to continue supporting NetLabel (see the patchset posting that 
was first accepted into the 2.6.19); I imagine this would fall under 
the "Supported" category as currently stated.  A few days ago I was asked, 
and agreed to, maintain all of the labeled networking code (in addition to 
NetLabel).  While it is extremely likely that HP will support this decision 
and allow me to work on all of the labeled networking infrastructure at work, 
it would be overstepping my role within the company to say that HP is 
pledging support for all of labeled networking.

I think the important thing here is that "someone is looking after this", 
whether or not they are actually paid to do so is not quite as important in 
my mind.  If you feel strongly about the distinction please let me know and I 
will update the status when/if it changes.

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