From: Neil Horman <nhorman@tuxdriver.com>
To: Stephan Mueller <smueller@chronox.de>
Cc: "'Herbert Xu'" <herbert@gondor.apana.org.au>,
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 04:46:31 -0500 [thread overview]
Message-ID: <20150114094631.GB15294@localhost.localdomain> (raw)
In-Reply-To: <5489736.JvWhZNrmuD@tachyon.chronox.de>
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
>
> --
> 2.1.0
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Where are the RNG bits?
Neil
next prev parent reply other threads:[~2015-01-14 9:46 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 ` Neil Horman [this message]
2015-01-14 11:00 ` [PATCH v10 0/2] crypto: AF_ALG: add AEAD and RNG support Herbert Xu
2015-01-14 15:31 ` Stephan Mueller
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=20150114094631.GB15294@localhost.localdomain \
--to=nhorman@tuxdriver.com \
--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=quentin.gouchet@gmail.com \
--cc=smueller@chronox.de \
/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