From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH v4 1/6] cipher: Update for current kernel akcipher interface
Date: Thu, 16 Jun 2016 18:17:24 -0500 [thread overview]
Message-ID: <57633384.7030402@gmail.com> (raw)
In-Reply-To: <20160615171823.20699-1-mathew.j.martineau@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
Hi Mat,
On 06/15/2016 12:18 PM, Mat Martineau wrote:
> There are some significant differences in the current iteration of
> kernel AF_ALG akcipher support:
> * Kernel handles padding
> * Kernel accepts DER-encoded certs as-is (no need to extract values)
> * Must explicitly set private or public key
> ---
> ell/cipher-private.h | 3 -
> ell/cipher.c | 305 +++++++++++++--------------------------------------
> ell/cipher.h | 3 +-
> ell/tls.c | 54 ++++-----
> 4 files changed, 101 insertions(+), 264 deletions(-)
>
Applied, thanks.
Regards,
-Denis
prev parent reply other threads:[~2016-06-16 23:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 17:18 [PATCH v4 1/6] cipher: Update for current kernel akcipher interface Mat Martineau
2016-06-15 17:18 ` [PATCH v4 2/6] unit: Update for akcipher changes Mat Martineau
2016-06-16 23:17 ` Denis Kenzior
2016-06-15 17:18 ` [PATCH v4 3/6] cipher: Return result length from asymmetric cipher Mat Martineau
2016-06-16 23:16 ` Denis Kenzior
2016-06-17 0:17 ` Mat Martineau
2016-06-17 1:30 ` Andrzej Zaborowski
2016-06-17 1:38 ` Denis Kenzior
2016-06-17 16:15 ` Mat Martineau
2016-06-15 17:18 ` [PATCH v4 4/6] unit: Check asymmetric cipher result lengths Mat Martineau
2016-06-15 17:18 ` [PATCH v4 5/6] unit: Check decryption against known ciphertext Mat Martineau
2016-06-15 17:18 ` [PATCH v4 6/6] cipher: Use only one socket for asymmetric cipher Mat Martineau
2016-06-16 23:17 ` Denis Kenzior [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=57633384.7030402@gmail.com \
--to=denkenz@gmail.com \
--cc=ell@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.