Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Stephan Mueller <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH] crypto: add key wrapping block chaining mode
Date: Thu, 23 Apr 2015 15:42:19 +0200	[thread overview]
Message-ID: <2261126.vD1ovnGobO@myon.chronox.de> (raw)
In-Reply-To: <20150423025558.GA17870@gondor.apana.org.au>

Am Donnerstag, 23. April 2015, 10:55:58 schrieb Herbert Xu:

Hi Herbert,

> On Thu, Apr 23, 2015 at 04:51:56AM +0200, Stephan Mueller wrote:
> > Encrypt input: IV, plaintext
> > 
> > Encrypt output: processed IV, ciphertext
> > 
> > Decrypt input: processed IV, ciphertext, IV to use for compare operation
> > 
> > Decrypt output: plaintext
> 
> Actually it is
> 
> Decrypt input: processed IV, ciphertext
> Decrypt output: IV, plaintext
> 
> > How do you propose I send 2 IVs to blkcipher?
> 
> As I suggested earlier, you can use the currently unused givdecrypt
> interface for the fixed IV case as specified in the RFC.  The giv
> interfaces provide space for two IVs.
> 
> If givdecrypt fails the comparison, then you can return EBADMSG
> and zap the decrypted key.
> 
> For the normal decrypt path, just return the IV and plaintet.

The conversion to blkcipher is done and the math still works. As CBC or others 
it is a blkcipher and not an ablkcipher.

Now, shall I kind of re-implement the chainiv ablkcipher wrapper into an IV 
handler that just helps my code? That will be a lot of code for a simple 
memcmp.

-- 
Ciao
Stephan

  reply	other threads:[~2015-04-23 13:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22  4:36 [PATCH] crypto: add key wrapping block chaining mode Stephan Mueller
2015-04-22  5:48 ` Herbert Xu
2015-04-22 12:44   ` Stephan Mueller
2015-04-23  1:39     ` Herbert Xu
2015-04-23  1:40       ` Stephan Mueller
2015-04-22  5:53 ` Herbert Xu
2015-04-22  6:13   ` Herbert Xu
2015-04-22 12:23     ` Stephan Mueller
2015-04-22 14:11       ` Stephan Mueller
2015-04-23  1:37         ` Herbert Xu
2015-04-23  1:33       ` Herbert Xu
2015-04-23  1:39         ` Stephan Mueller
2015-04-23  1:46           ` Herbert Xu
2015-04-23  1:58             ` Stephan Mueller
2015-04-23  2:03               ` Herbert Xu
2015-04-23  2:51             ` Stephan Mueller
2015-04-23  2:55               ` Herbert Xu
2015-04-23 13:42                 ` Stephan Mueller [this message]
2015-04-23 23:21                   ` Herbert Xu
2015-04-24  0:22                     ` Stephan Mueller
2015-04-24  0:24                       ` Herbert Xu
2015-04-22  6:06 ` Herbert Xu

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=2261126.vD1ovnGobO@myon.chronox.de \
    --to=smueller@chronox.de \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox