From: James Morris <jmorris@namei.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
David Howells <dhowells@redhat.com>,
Eric Biggers <ebiggers@google.com>,
linux-security-module@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [GIT PULL] security: keys fixes for v4.14-rc3
Date: Fri, 29 Sep 2017 08:53:28 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1709290852340.19449@namei.org> (raw)
In-Reply-To: <CAHmME9oRwa+Oi=wa0MT3vRagZL6FTTzxwvE3NBO13_yxg4Kznw@mail.gmail.com>
On Fri, 29 Sep 2017, Jason A. Donenfeld wrote:
> On Fri, Sep 29, 2017 at 12:33 AM, James Morris <jmorris@namei.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@namei.org>
prev parent reply other threads:[~2017-09-28 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-28 22:33 James Morris
2017-09-28 22:39 ` Jason A. Donenfeld
2017-09-28 22:53 ` James Morris [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.21.1709290852340.19449@namei.org \
--to=jmorris@namei.org \
--cc=Jason@zx2c4.com \
--cc=dhowells@redhat.com \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®