linux-kernel - Re: [GIT PULL] security: keys fixes for v4.14-rc3

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: <alpine.LRH.2.21.1709290852340.19449@namei.org>
Date:   Fri, 29 Sep 2017 08:53:28 +1000 (AEST)
From:   James Morris <jmorris@...ei.org>
To:     "Jason A. Donenfeld" <Jason@...c4.com>
cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        David Howells <dhowells@...hat.com>,
        Eric Biggers <ebiggers@...gle.com>,
        linux-security-module@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        Andy Lutomirski <luto@...capital.net>
Subject: Re: [GIT PULL] security: keys fixes for v4.14-rc3

On Fri, 29 Sep 2017, Jason A. Donenfeld wrote:

> On Fri, Sep 29, 2017 at 12:33 AM, James Morris <jmorris@...ei.org> wrote:
> > Generally speaking, we likely need to improve the amount of crypto review
> > for kernel crypto users including keys (I'll post a note separately to
> > ksummit-discuss).
> 
> Indeed.
> 
> I won't be at kernel summit, regrettably, but I do intend to
> methodically work through the kernel reviewing the various crypto
> [mis]uses in places. I also have some larger plans regarding reworking
> a few aspects of the crypto API, that I'll start a discussion with
> Herbert about during the next several months. (I'm CCing Andy because
> this is something the two of us have also discussed.)
> 
> So, expect some more things like this patch to gradually be rolling
> your way, along with maybe larger overall changes. If you wind up
> discussing this in any substantial way at the summit this year, please
> do try to loop me in at some point.

Absolutely.  This is important work and great to hear!

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