From: Eric Biggers <ebiggers@kernel.org>
To: Dongsoo Lee <letrhee@nsr.re.kr>
Cc: 'Herbert Xu' <herbert@gondor.apana.org.au>,
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, 9 Jun 2023 19:14:50 -0700 [thread overview]
Message-ID: <20230610021450.GA872@sol.localdomain> (raw)
In-Reply-To: <005601d99ac9$954f0c70$bfed2550$@nsr.re.kr>
On Fri, Jun 09, 2023 at 08:57:36PM +0900, Dongsoo Lee wrote:
> Unfortunately, currently, vendors trying to supply Linux-based data-at-rest
> encryption products by utilizing the dm-crypt or the fscrypt modules to
> government agencies or public institutions in Korea are experiencing great
> difficulties.
Why are they having "great difficulties" when the kernel already supports two
other "KCMVP-approved block ciphers", ARIA and SEED? Why aren't they using
dm-crypt with ARIA or SEED?
> According to Korean regulations, the data transmitted and stored by
> government agencies and public institutions must be protected using KCMVP
> validated cryptographic modules.
And does LEA (or SEED or ARIA) support in Linux actually solve that problem?
Just adding support for these algorithms to Linux does not mean that Linux
automatically becomes a "KCMVP validated cryptographic module", right? Do you
have a complete plan that would actually solve the claimed problem?
- Eric
next prev parent reply other threads:[~2023-06-10 2:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 12:12 [PATCH v2 0/2] crypto: LEA block cipher implementation 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
2023-06-02 21:39 ` Eric Biggers
2023-06-09 11:57 ` Dongsoo Lee
2023-06-10 2:14 ` Eric Biggers [this message]
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=20230610021450.GA872@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=letrhee@gmail.com \
--cc=letrhee@nsr.re.kr \
--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