From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Neil Horman <nhorman@tuxdriver.com>,
Daniel Borkmann <dborkman@redhat.com>,
"'Quentin Gouchet'" <quentin.gouchet@gmail.com>,
"'LKML'" <linux-kernel@vger.kernel.org>,
ABI/API <linux-api@vger.kernel.org>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v10 0/2] crypto: AF_ALG: add AEAD and RNG support
Date: Wed, 14 Jan 2015 16:31:44 +0100 [thread overview]
Message-ID: <5006702.rWOQQ5L1VO@tachyon.chronox.de> (raw)
In-Reply-To: <20150114110011.GA18099@gondor.apana.org.au>
Am Mittwoch, 14. Januar 2015, 22:00:11 schrieb Herbert Xu:
Hi Herbert,
> On Wed, Jan 14, 2015 at 04:46:31AM -0500, Neil Horman wrote:
> > On Wed, Jan 14, 2015 at 04:52:29AM +0100, Stephan Mueller wrote:
> > > Hi,
> > >
> > > This patch set adds AEAD and RNG support to the AF_ALG interface
> > > exported by the kernel crypto API. By extending AF_ALG with AEAD and RNG
> > > support, all cipher types the kernel crypto API allows access to are
> > > now accessible from userspace.
> > >
> > > crypto/Kconfig | 9 +
> > > crypto/Makefile | 1 +
> > > crypto/algif_aead.c | 680
> > > ++++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed,
> > > 690 insertions(+)
> > > create mode 100644 crypto/algif_aead.c
> >
> > Where are the RNG bits?
>
> They've already been merged.
Please also see my change log for v7:
...
* RNG: patch dropped as it was applied
...
To ensure consistency, I did not change the intro part of my description.
>
> Cheers,
--
Ciao
Stephan
next prev parent reply other threads:[~2015-01-14 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 3:52 [PATCH v10 0/2] crypto: AF_ALG: add AEAD and RNG support Stephan Mueller
2015-01-14 3:53 ` [PATCH v10 1/2] crypto: AF_ALG: add AEAD support Stephan Mueller
2015-01-14 3:53 ` [PATCH v10 2/2] crypto: AF_ALG: enable AEAD interface compilation Stephan Mueller
2015-01-14 9:46 ` [PATCH v10 0/2] crypto: AF_ALG: add AEAD and RNG support Neil Horman
2015-01-14 11:00 ` Herbert Xu
2015-01-14 15:31 ` Stephan Mueller [this message]
2015-01-14 17:26 ` Neil Horman
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=5006702.rWOQQ5L1VO@tachyon.chronox.de \
--to=smueller@chronox.de \
--cc=dborkman@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-api@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=quentin.gouchet@gmail.com \
/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