[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230610021450.GA872@sol.localdomain>
Date: Fri, 9 Jun 2023 19:14:50 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: Dongsoo Lee <letrhee@....re.kr>
Cc: 'Herbert Xu' <herbert@...dor.apana.org.au>,
linux-crypto@...r.kernel.org, davem@...emloft.net,
linux-kernel@...r.kernel.org, letrhee@...il.com
Subject: Re: [PATCH v2 0/2] crypto: LEA block cipher implementation
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
Powered by blists - more mailing lists