mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dongsoo Lee <letrhee@nsr.re.kr>
To: 'Herbert Xu' <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, davem@davemloft.net,
	linux-kernel@vger.kernel.org, letrhee@gmail.com
Subject: RE: [PATCH v2 0/2] crypto: LEA block cipher implementation
Date: Fri, 2 Jun 2023 15:05:16 +0900	[thread overview]
Message-ID: <008d01d99518$33db63f0$9b922bd0$@nsr.re.kr> (raw)
In-Reply-To: <ZHh1H3yKPU68J7Uv@gondor.apana.org.au>

>>
>> We expect that the first application of the patch would be disk
encryption on the Gooroom platform ('Gooroom' is a Korean word, meaning
'cloud') [3]. Currently, the Gooroom platform uses AES-XTS for disk
encryption. The main reason for submitting this patch is to make disk
encryption with LEA (e.g. LEA-XTS) available on there.
>
>We don't add kernel algorithms without an in-kernel user.  Is there an
existing in-kernel user that can use this as is or are you going to add one?
>
>Thanks,

Our current goal is to encrypt with LEA in a data-at-rest environment.

One option we are considering is utilizing the `dm-crypt` module for disk
encryption. The `dm-crypt` module can use various ciphers provided by the
Linux Crypto API. By specifying the `lea-xts-plain` option in the
`cryptsetup` tool, it can immediately work without further modification.

Additionally, we are exploring the possibility of using `blk-crypto` for
encryption. Currently, the ciphers available for `blk-crypto` are
AES-256-XTS, AES-128-CBC-ESSIV, Adiantum, and SM4-XTS. We would like to add
LEA-256-XTS to these.

( https://github.com/torvalds/linux/blob/master/block/blk-crypto.c#L21 )

Instead of disk encryption, it is also possible to use `fscrypt` to encrypt
the file system for data-at-rest environments. `fscrypt` currently supports
AES-256-XTS, AES-256-CTS-CBC, AES-128-CBC-ESSIV, AES-128-CTS-CBC, SM4-XTS,
SM4-CTS-CBC, Adiantum, and AES-256-HCTR2.

( https://github.com/torvalds/linux/blob/master/fs/crypto/keysetup.c#L16 )

The above are what we will do with LEA.

Thank you.

  reply	other threads:[~2023-06-02  6:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-25 12:12 Dongsoo Lee
2023-05-25 12:13 ` [PATCH v2 1/2] " Dongsoo Lee
2023-05-25 12:13 ` [PATCH v2 2/2] crypto: add LEA testmgr tests Dongsoo Lee
2023-06-01 10:38 ` [PATCH v2 0/2] crypto: LEA block cipher implementation Herbert Xu
2023-06-02  6:05   ` Dongsoo Lee [this message]
2023-06-02 21:39     ` Eric Biggers
2023-06-09 11:57       ` Dongsoo Lee
2023-06-10  2:14         ` Eric Biggers
2023-06-16  8:08           ` Dongsoo Lee

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='008d01d99518$33db63f0$9b922bd0$@nsr.re.kr' \
    --to=letrhee@nsr.re.kr \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=letrhee@gmail.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®