netdev - Re: IPSEC maintainership...

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]

Message-Id: <20121016.021435.220828722592000976.davem@davemloft.net>
Date:	Tue, 16 Oct 2012 02:14:35 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	steffen.klassert@...unet.com
Cc:	netdev@...r.kernel.org, herbert@...dor.apana.org.au
Subject: Re: IPSEC maintainership...

From: Steffen Klassert <steffen.klassert@...unet.com>
Date: Tue, 16 Oct 2012 08:11:54 +0200

> On Mon, Oct 15, 2012 at 01:38:33PM -0400, David Miller wrote:
>> 
>> Steffen, after some discussions with Herbert we'd like to formally
>> recognize your outstanding contributions to the IPSEC stack over
>> the past few years by listing you explicitly as a maintainer as
>> per the patch below.
>> 
>> Let us know if you are OK with this.
> 
> I'm absolutely OK with this, of course :)
> 
> Being one of the maintainers, I'd like to run our automated IPsec
> tests on incomming paches before they get applied. So I'd think
> about a workflow and propose something if you are OK with that.

If you want you can maintainer an IPSEC GIT tree, where you apply any
submitted IPSEC changes.

Once you are satisfied with their quality and they pass your tests,
you simply send me a formal GIT pull request just like any other
networking subsystem (netfilter, wireless, etc.) currently does.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html