All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH v7 2/5] cipher: Return number of read bytes from asymmetric ops
Date: Mon, 20 Jun 2016 19:11:55 -0500	[thread overview]
Message-ID: <5768864B.3050304@gmail.com> (raw)
In-Reply-To: <20160620235340.30410-2-mathew.j.martineau@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 644 bytes --]

Hi Mat,

On 06/20/2016 06:53 PM, Mat Martineau wrote:
> When using asymmetric cipher operations, the data written to the
> output buffer might be shorter than the full buffer size. The number
> of bytes read is now returned from the asymmetric
> encrypt/decrypt/sign/verify functions. A negative error code is
> returned if the call fails.
> ---
>   ell/cipher.c | 43 +++++++++++++++++++++++--------------------
>   ell/cipher.h | 16 ++++++++--------
>   ell/tls.c    | 45 +++++++++++++++++++++++----------------------
>   3 files changed, 54 insertions(+), 50 deletions(-)
>

Patches 2-5 applied, thanks.

Regards,
-Denis


  reply	other threads:[~2016-06-21  0:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-20 23:53 [PATCH v7 1/5] tls: Check buffer bounds in tls_rsa_sign Mat Martineau
2016-06-20 23:53 ` [PATCH v7 2/5] cipher: Return number of read bytes from asymmetric ops Mat Martineau
2016-06-21  0:11   ` Denis Kenzior [this message]
2016-06-20 23:53 ` [PATCH v7 3/5] unit: Check asymmetric cipher result lengths Mat Martineau
2016-06-20 23:53 ` [PATCH v7 4/5] unit: Check decryption against known ciphertext Mat Martineau
2016-06-20 23:53 ` [PATCH v7 5/5] cipher: Use only one socket for asymmetric cipher Mat Martineau
2016-06-21  0:02 ` [PATCH v7 1/5] tls: Check buffer bounds in tls_rsa_sign Denis Kenzior

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=5768864B.3050304@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.