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 v2] SP800-38F / RFC3394 key wrapping
Date: Mon, 11 May 2015 12:15:56 +0200	[thread overview]
Message-ID: <3967410.spMBXlI7nE@tauon> (raw)
In-Reply-To: <20150511094212.GA4224@gondor.apana.org.au>

Am Montag, 11. Mai 2015, 17:42:12 schrieb Herbert Xu:

Hi Herbert,

>On Fri, May 01, 2015 at 03:21:19PM +0200, Stephan Mueller wrote:
>> My idea would be to use keywrap in step 3.
>
>How is dm-crypt going to cope with the increase in ciphertext size?

The LUKS header is not fixed-size, so it would be able to handle the increased 
cipher text size.

But I think I should rather go back and write up the ideas that I have for key 
handling. Currently it seems that too many components in kernel and user space 
handle plaintext keys.

After writing that one up, I like to present it with an assoicated discussion 
of how to handle key wrapping considering that addition of it to the kernel 
crypto API is not possible at this point.

Thanks for your help.

Ciao
Stephan

      reply	other threads:[~2015-05-11 10:16 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-25 22:07 [PATCH v2] SP800-38F / RFC3394 key wrapping Stephan Mueller
2015-04-25 22:08 ` [PATCH v2] crypto: add key wrapping block chaining mode Stephan Mueller
2015-04-27  8:26   ` Herbert Xu
2015-04-27 14:34     ` Stephan Mueller
2015-04-28  1:10       ` Herbert Xu
2015-04-28  2:35         ` Stephan Mueller
2015-04-28  2:50           ` Herbert Xu
2015-04-27  8:29   ` Herbert Xu
2015-04-27 14:58     ` Stephan Mueller
2015-04-28  1:12       ` Herbert Xu
2015-04-28  1:09 ` [PATCH v2] SP800-38F / RFC3394 key wrapping Herbert Xu
2015-04-28  2:45   ` Stephan Mueller
2015-04-28  2:54     ` Herbert Xu
2015-04-28  2:58       ` Stephan Mueller
2015-05-01  3:20         ` Herbert Xu
2015-05-01  7:27           ` Stephan Mueller
2015-05-01  7:30             ` Herbert Xu
2015-05-01 13:21               ` Stephan Mueller
2015-05-11  9:42                 ` Herbert Xu
2015-05-11 10:15                   ` Stephan Mueller [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=3967410.spMBXlI7nE@tauon \
    --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