[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YKLhc6HX9+JunQ/X@gmail.com>
Date: Mon, 17 May 2021 14:34:43 -0700
From: Eric Biggers <ebiggers@...nel.org>
To: "Chang S. Bae" <chang.seok.bae@...el.com>
Cc: tglx@...utronix.de, mingo@...nel.org, bp@...e.de, luto@...nel.org,
x86@...nel.org, herbert@...dor.apana.org.au,
dan.j.williams@...el.com, dave.hansen@...el.com,
ravi.v.shankar@...el.com, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2 10/11] crypto: x86/aes-kl - Support AES algorithm
using Key Locker instructions
On Fri, May 14, 2021 at 01:15:07PM -0700, Chang S. Bae wrote:
>
> Included are methods for ECB, CBC, CTR, and XTS modes. They are not
> compatible with other implementations as referencing an encrypted form
> only.
Your code uses the standard algorithm names like cbc(aes), which implies that it
is compatible with the standard cbc(aes). So which is it -- compatible or not
compatible -- and if it isn't compatible, what is the expected use case?
- Eric
Powered by blists - more mailing lists