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: Wed, 22 Apr 2015 14:23:04 +0200	[thread overview]
Message-ID: <5036814.6LNlN5eOjK@myon.chronox.de> (raw)
In-Reply-To: <20150422061354.GA8053@gondor.apana.org.au>

Am Mittwoch, 22. April 2015, 14:13:54 schrieb Herbert Xu:

Hi Herbert,

> On Wed, Apr 22, 2015 at 01:53:24PM +0800, Herbert Xu wrote:
> > On Wed, Apr 22, 2015 at 06:36:59AM +0200, Stephan Mueller wrote:
> > > The key wrapping is an authenticated encryption operation without
> > > associated data. Therefore, setting of AAD is permissible, but that data
> > > is not used by the cipher implementation.
> > 
> > In that case you should return an error if AAD is provided rather
> > than silently discarding them since by definition AEAD must include
> > the AAD in the integrity value.
> 
> In fact drop the AEAD altogether and just use ablkcipher.  The
> integrity value is then simply the output IV.

Initially I was playing with ablkcipher. But then I moved to AEAD because the 
ciphertext is longer than the plaintext.

Isn't it a basic assumption to ablkcipher is that the ciphertext is equal in 
size as the plaintext?

-- 
Ciao
Stephan

  reply	other threads:[~2015-04-22 12:24 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 [this message]
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
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=5036814.6LNlN5eOjK@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