[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201026175231.GG858@sol.localdomain>
Date: Mon, 26 Oct 2020 10:52:31 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: Gilad Ben-Yossef <gilad@...yossef.com>
Cc: Herbert Xu <herbert@...dor.apana.org.au>,
"David S. Miller" <davem@...emloft.net>,
Alasdair Kergon <agk@...hat.com>,
Mike Snitzer <snitzer@...hat.com>, dm-devel@...hat.com,
Song Liu <song@...nel.org>, Ofir Drang <ofir.drang@....com>,
linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-raid@...r.kernel.org
Subject: Re: [PATCH 3/4] dm crypt: switch to EBOIV crypto API template
On Mon, Oct 26, 2020 at 03:04:46PM +0200, Gilad Ben-Yossef wrote:
> Replace the explicit EBOIV handling in the dm-crypt driver with calls
> into the crypto API, which now possesses the capability to perform
> this processing within the crypto subsystem.
>
> Signed-off-by: Gilad Ben-Yossef <gilad@...yossef.com>
>
> ---
> drivers/md/Kconfig | 1 +
> drivers/md/dm-crypt.c | 61 ++++++++++++++-----------------------------
> 2 files changed, 20 insertions(+), 42 deletions(-)
>
> diff --git a/drivers/md/Kconfig b/drivers/md/Kconfig
> index 30ba3573626c..ca6e56a72281 100644
> --- a/drivers/md/Kconfig
> +++ b/drivers/md/Kconfig
> @@ -273,6 +273,7 @@ config DM_CRYPT
> select CRYPTO
> select CRYPTO_CBC
> select CRYPTO_ESSIV
> + select CRYPTO_EBOIV
> help
> This device-mapper target allows you to create a device that
> transparently encrypts the data on it. You'll need to activate
Can CRYPTO_EBOIV please not be selected by default? If someone really wants
Bitlocker compatibility support, they can select this option themselves.
- Eric
Powered by blists - more mailing lists