linux-kernel - Re: Change in security maintainer for a few weeks

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:	Fri, 6 Jun 2014 17:23:25 +0200
From:	"Serge E. Hallyn" <serge@...lyn.com>
To:	Casey Schaufler <casey@...aufler-ca.com>
Cc:	Serge Hallyn <serge.hallyn@...ntu.com>,
	Greg KH <gregkh@...uxfoundation.org>,
	Paul Moore <paul@...l-moore.com>,
	Jiri Kosina <jkosina@...e.cz>, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org,
	"Serge E. Hallyn" <serge@...onical.com>
Subject: Re: Change in security maintainer for a few weeks

Quoting Casey Schaufler (casey@...aufler-ca.com):
> On 6/5/2014 9:42 PM, Serge Hallyn wrote:
> > Quoting Greg KH (gregkh@...uxfoundation.org):
> >> On Thu, Jun 05, 2014 at 06:39:09PM -0400, Paul Moore wrote:
> >>> On Thursday, June 05, 2014 11:59:11 PM Jiri Kosina wrote:
> >>>> On Thu, 5 Jun 2014, Greg KH wrote:
> >>>>> James has had to step back from doing kernel work for a few weeks, so
> >>>>> I've offered to step up and handle the security patches to get shuttled
> >>>>> to Linus for merging for a while.
> >>>> As exactly this (working with active contributors to help co-maintain the
> >>>> subsystem) has been brought at the ksummit maling list, I am just curious
> >>>> whether noone else actively working in that area was willing to step up?
> >>>>
> >>>> 	$ ./scripts/get_maintainer.pl --git -f security/
> >>>> 	James Morris <james.l.morris@...cle.com> (supporter:SECURITY SUBSYSTEM)
> >>>>    ...
> >>>>
> >>>> If not, then I think this can be shown as a prime example why the problem
> >>>> of "non-substituability" of many maintainers is actually real.
> >>> Once several of us became aware that James was stepping away for a few weeks 
> >>> (I should mention this was not a planned absence and took most of us by 
> >>> surprise) we had a brief discussion off-list and several of us did offer to 
> >>> "step-up"; Serge had already created a repo and since he had pushed patches 
> >>> while James was away in the past it seemed a reasonable approach this time 
> >>> around.
> >> That's great, as the communication around this has not been very much
> >> (an non-existant on the subsystem mailing list) I was not aware of it.
> >>
> >> If Serge wants to do this, and as he has been the stand-in for James in
> >> the past, I have _no_ objection to this at all.
> >>
> >> Serge, feel free to resend your patches to Linus if he doesn't pick them
> >> up in a few days, with the information that you are doing this in
> >> James's absence for a while.
> > Will do (and wil cc: lsm).
> >
> >> So, that was easy, I don't have to do this at all, great.
> >>
> >> greg k-h
> 
> How can I verify that the pull James accepted from me is
> moving forward somehow? Or, if it isn't, where does it go now?

You can see it at
https://git.kernel.org/cgit/linux/kernel/git/sergeh/linux-security.git/log/security/smack?h=serge-next-1
As Greg suggested if Linus doesn't pull it in a few days I will resend
the pull request.
--
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/