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, 06 Jun 2014 08:08:11 -0700
From:	Casey Schaufler <casey@...aufler-ca.com>
To:	Serge Hallyn <serge.hallyn@...ntu.com>,
	Greg KH <gregkh@...uxfoundation.org>
CC:	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>,
	Casey Schaufler <casey@...aufler-ca.com>
Subject: Re: Change in security maintainer for a few weeks

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?


On Thu, 15 May 2014, Casey Schaufler wrote:

> The following changes since commit f64410ec665479d7b4b77b7519e814253ed0f686:
>
>   selinux: correctly label /proc inodes in use before the policy is loaded (2014-03-19 16:46:18 -0400)
>
> are available in the git repository at:
>
>   git://git.gitorious.org/smack-next/kernel.git smack-for-3.16
>
> for you to fetch changes up to ec554fa75ec94dcf47e52db9551755679c10235b:

Thanks, pulled.


-- James Morris <jmorris@...ei.org> 

> --
> To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

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