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: Fri, 01 May 2015 09:27:07 +0200 [thread overview]
Message-ID: <43350012.VMEhAijB9c@tauon> (raw)
In-Reply-To: <20150501032035.GA371@gondor.apana.org.au>
Am Freitag, 1. Mai 2015, 11:20:35 schrieb Herbert Xu:
Hi Herbert,
>On Tue, Apr 28, 2015 at 04:58:31AM +0200, Stephan Mueller wrote:
>> Hm, in case of dm-crypt, that is not really possible, because this is fully
>> driven by user space: libcryptsetup sets up a temporary dm-crypt container
>> for the LUKS header space. Then user space accesses the data it needs and
>> re- injects it into the kernel for the bulk encryption dm-crypt component.
>If both user-space and the kernel implements the same algorithm
>correctly why wouldn't it work?
User space does not use any ciphers to protect the key, that is the
interesting part. The LUKS header will be mapped by a dm-crypt mapping and
then read from user space to access the key. So, userspace does not en/decrypt
the data.
Ciao
Stephan
next prev parent reply other threads:[~2015-05-01 7:27 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 [this message]
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
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=43350012.VMEhAijB9c@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