From: Herbert Xu <herbert@gondor.apana.org.au>
To: Binoy Jayan <binoy.jayan@linaro.org>
Cc: Milan Broz <gmazyland@gmail.com>, Oded <oded.golombek@arm.com>,
Ofir <Ofir.Drang@arm.com>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com, Shaohua Li <shli@kernel.org>,
linux-raid@vger.kernel.org, Rajendra <rnayak@codeaurora.org>
Subject: Re: [RFC PATCH v2] crypto: Add IV generation algorithms
Date: Fri, 30 Dec 2016 18:27:23 +0800 [thread overview]
Message-ID: <20161230102723.GA15713@gondor.apana.org.au> (raw)
In-Reply-To: <CAHv-k_9SynECq7qDbrW59=LsV_WNj+9Ffa=6tATyNKOt36he6Q@mail.gmail.com>
On Thu, Dec 29, 2016 at 02:53:25PM +0530, Binoy Jayan wrote:
>
> When we keep these in dm-crypt and if more than one key is used
> (it is actually more than one parts of the original key),
> there are more than one cipher instance created - one for each
> unique part of the key. Since the crypto requests are modelled
> to go through the template ciphers in the order:
>
> "essiv -> cbc -> aes"
>
> a particular cipher instance of the IV (essiv in this example) is
> responsible to encrypt an entire bigger block. If this bigger block
> is to be later split into 512 bytes blocks and then encrypted using
> the other cipher instance depending on the following formula:
>
> key_index = sector & (key_count - 1)
This is just a matter of structuring the key for the IV generator.
The IV generator's key in this case should be a combination of the
key to the underlying CBC plus the set of all keys for the IV
generator itself. It should then allocate the required number of
tfms as is currently done by crypt_alloc_tfms in dm-crypt.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2016-12-30 10:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-13 8:49 [RFC PATCH v2] IV Generation algorithms for dm-crypt Binoy Jayan
2016-12-13 8:49 ` [RFC PATCH v2] crypto: Add IV generation algorithms Binoy Jayan
2016-12-13 10:01 ` Milan Broz
2016-12-14 6:09 ` Binoy Jayan
2016-12-16 5:55 ` Binoy Jayan
2016-12-22 8:55 ` Herbert Xu
2016-12-22 10:55 ` Binoy Jayan
2016-12-23 7:51 ` Herbert Xu
2016-12-29 9:23 ` Binoy Jayan
2016-12-30 10:27 ` Herbert Xu [this message]
2017-01-02 6:46 ` Binoy Jayan
2017-01-02 6:53 ` Herbert Xu
2017-01-02 7:05 ` Binoy Jayan
2017-01-05 6:06 ` Binoy Jayan
2017-01-03 14:23 ` Gilad Ben-Yossef
2017-01-04 5:20 ` Binoy Jayan
2017-01-11 14:55 ` Ondrej Mosnáček
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=20161230102723.GA15713@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=Ofir.Drang@arm.com \
--cc=agk@redhat.com \
--cc=arnd@arndb.de \
--cc=binoy.jayan@linaro.org \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=dm-devel@redhat.com \
--cc=gmazyland@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=oded.golombek@arm.com \
--cc=rnayak@codeaurora.org \
--cc=shli@kernel.org \
--cc=snitzer@redhat.com \
/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
all inboxes | Powered by JetHome®