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  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:	Thu, 05 Jun 2014 23:26:09 -0400
From:	Mimi Zohar <>
To:	Dmitry Kasatkin <>
Cc:	Greg KH <>,
	"" <>,
	linux-security-module <>
Subject: Re: Change in security maintainer for a few weeks

On Thu, 2014-06-05 at 22:52 +0300, Dmitry Kasatkin wrote: 
> On 5 June 2014 21:30, Greg KH <> wrote:
> > Hi all,
> >
> > 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.
> >
> > I'll take his git tree on and push those to Linus for
> > 3.16-rc1, as those look like they have had proper testing in linux-next.
> >
> > But there only seems to be 14 patches in there.  Are there pending
> > patches that people have been sending and need to get in besides those?
> >
> > thanks,
> >
> Hi Greg,
> Mimi sent pull request to James last week without any response...
> But that is based on James' 3.14 tree..
> May be Mimi need to rebase and send pull request to you..

I'm really sorry Dmitry.  Unlike the SELinux patches, the integrity
patches didn't make it into linux-next.  Based on Paul's suggestion,
I'll request that the linux-integrity tree be added to the list of trees
that are pulled directly into linux-next, instead of waiting for it to
go in via the security tree.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists