Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1673759
| From | Eric Biggers <ebiggers3@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v6 0/2] IV Generation algorithms for dm-crypt |
| Date | 2017-06-23 20:30 +0200 |
| Message-ID | <tVBvc-5CD-17@gated-at.bofh.it> (permalink) |
| References | <tV2e5-89c-11@gated-at.bofh.it> <tVrYS-8aL-23@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Jun 23, 2017 at 04:13:41PM +0800, Herbert Xu wrote: > Binoy Jayan <binoy.jayan@linaro.org> wrote: > > =============================================================================== > > dm-crypt optimization for larger block sizes > > =============================================================================== > > > > Currently, the iv generation algorithms are implemented in dm-crypt.c. The goal > > is to move these algorithms from the dm layer to the kernel crypto layer by > > implementing them as template ciphers so they can be used in relation with > > algorithms like aes, and with multiple modes like cbc, ecb etc. As part of this > > patchset, the iv-generation code is moved from the dm layer to the crypto layer > > and adapt the dm-layer to send a whole 'bio' (as defined in the block layer) > > at a time. Each bio contains the in memory representation of physically > > contiguous disk blocks. Since the bio itself may not be contiguous in main > > memory, the dm layer sets up a chained scatterlist of these blocks split into > > physically contiguous segments in memory so that DMA can be performed. > > There is currently a patch-set for fscrypt to add essiv support. It > would be interesting to know whether your implementation of essiv > can also be used in that patchset. That would confirm that we're on > the right track. > You can find the fscrypt patch at https://patchwork.kernel.org/patch/9795327/ Note that it's encrypting 4096-byte blocks, not 512-byte. Also, it's using AES-256 for the ESSIV tfm (since it uses a SHA-256 hash) but AES-128 for the "real" encryption. It's possible this is a mistake and it should be AES-128 for both. (If it is, it needs to be fixed before it's released in 4.13.) Eric
Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread
[PATCH v6 0/2] IV Generation algorithms for dm-crypt Binoy Jayan <binoy.jayan@linaro.org> - 2017-06-22 06:50 +0200
Re: [PATCH v6 0/2] IV Generation algorithms for dm-crypt Herbert Xu <herbert@gondor.apana.org.au> - 2017-06-23 10:20 +0200
Re: [PATCH v6 0/2] IV Generation algorithms for dm-crypt Eric Biggers <ebiggers3@gmail.com> - 2017-06-23 20:30 +0200
csiph-web