From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: linux-crypto@vger.kernel.org, Dongsoo Lee <letrhee@nsr.re.kr>
Subject: [PATCH 2/2] fscrypt: document the LEA support
Date: Thu, 29 Jun 2023 23:48:11 -0700 [thread overview]
Message-ID: <20230630064811.22569-3-ebiggers@kernel.org> (raw)
In-Reply-To: <20230630064811.22569-1-ebiggers@kernel.org>
From: Eric Biggers <ebiggers@google.com>
Document the LEA encryption support in fscrypt.rst.
Signed-off-by: Eric Biggers <ebiggers@google.com>
---
Documentation/filesystems/fscrypt.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/filesystems/fscrypt.rst b/Documentation/filesystems/fscrypt.rst
index a624e92f2687f..84fbda668191e 100644
--- a/Documentation/filesystems/fscrypt.rst
+++ b/Documentation/filesystems/fscrypt.rst
@@ -343,6 +343,7 @@ Currently, the following pairs of encryption modes are supported:
- Adiantum for both contents and filenames
- AES-128-CBC-ESSIV for contents and AES-128-CTS-CBC for filenames
- SM4-XTS for contents and SM4-CTS-CBC for filenames
+- LEA-256-XTS for contents and LEA-256-CTS-CBC for filenames
Authenticated encryption modes are not currently supported because of
the difficulty of dealing with ciphertext expansion. Therefore,
@@ -382,6 +383,7 @@ accelerator such as CAAM or CESA that does not support XTS.
The remaining mode pairs are the "national pride ciphers":
- (SM4-XTS, SM4-CTS-CBC)
+- (LEA-256-XTS, LEA-256-CTS-CBC)
Generally speaking, these ciphers aren't "bad" per se, but they
receive limited security review compared to the usual choices such as
--
2.41.0
prev parent reply other threads:[~2023-06-30 6:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 6:48 [PATCH 0/2] fscrypt: update the encryption mode docs Eric Biggers
2023-06-30 6:48 ` [PATCH 1/2] fscrypt: improve the "Encryption modes and usage" section Eric Biggers
2023-06-30 6:48 ` Eric Biggers [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=20230630064811.22569-3-ebiggers@kernel.org \
--to=ebiggers@kernel.org \
--cc=letrhee@nsr.re.kr \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fscrypt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.