All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ell@lists.01.org
Subject: Re: [PATCH v2 0/2] Cipher infrastructure
Date: Mon, 09 Feb 2015 09:40:25 -0600	[thread overview]
Message-ID: <54D8D4E9.3070506@gmail.com> (raw)
In-Reply-To: <1423226363-5025-1-git-send-email-tomasz.bursztyka@linux.intel.com>

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

Hi Tomasz,

On 02/06/2015 06:39 AM, Tomasz Bursztyka wrote:
> Hi,
>
> Looks like we need to re-inject the keys to the master socket (the one which
> is binded so the selected crypto) once before an operation type, so first encrypt
> and/or first decrypt.
> Now it seems to work. Should it handle an initialization vector?
>
> Tomasz Bursztyka (2):
>    cipher: Add a basic infrastructure for kernel based cipher operations
>    unit: Add unit test for the cipher infrastructure
>
>   Makefile.am        |  11 ++-
>   ell/cipher.c       | 221 +++++++++++++++++++++++++++++++++++++++++++++++++++++
>   ell/cipher.h       |  52 +++++++++++++
>   ell/ell.h          |   1 +
>   unit/test-cipher.c | 107 ++++++++++++++++++++++++++
>   5 files changed, 389 insertions(+), 3 deletions(-)
>   create mode 100644 ell/cipher.c
>   create mode 100644 ell/cipher.h
>   create mode 100644 unit/test-cipher.c
>

I went ahead and applied both patches, but I reworked the implementation 
afterward.  I tried to explain the reasoning in the commit message, let 
me know if I succeeded :)

Regards,
-Denis

  parent reply	other threads:[~2015-02-09 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 12:39 [PATCH v2 0/2] Cipher infrastructure Tomasz Bursztyka
2015-02-06 12:39 ` [PATCH 1/2] cipher: Add a basic infrastructure for kernel based cipher operations Tomasz Bursztyka
2015-02-06 12:39 ` [PATCH 2/2] unit: Add unit test for the cipher infrastructure Tomasz Bursztyka
2015-02-09 15:40 ` Denis Kenzior [this message]
2015-02-10  7:19   ` [PATCH v2 0/2] Cipher infrastructure Tomasz Bursztyka

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=54D8D4E9.3070506@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.