[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4f37c07c-3a39-4c98-b9c4-13356f5a10dc@canonical.com>
Date: Sat, 17 May 2025 00:43:30 -0700
From: John Johansen <john.johansen@...onical.com>
To: Eric Biggers <ebiggers@...nel.org>, apparmor@...ts.ubuntu.com
Cc: linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org
Subject: Re: [PATCH] apparmor: use SHA-256 library API instead of crypto_shash
API
On 5/13/25 21:21, Eric Biggers wrote:
> On Mon, Apr 28, 2025 at 12:04:30PM -0700, Eric Biggers wrote:
>> From: Eric Biggers <ebiggers@...gle.com>
>>
>> This user of SHA-256 does not support any other algorithm, so the
>> crypto_shash abstraction provides no value. Just use the SHA-256
>> library API instead, which is much simpler and easier to use.
>>
>> Signed-off-by: Eric Biggers <ebiggers@...gle.com>
>> ---
>>
>> This patch is targeting the apparmor tree for 6.16.
>>
>> security/apparmor/Kconfig | 3 +-
>> security/apparmor/crypto.c | 85 ++++++--------------------------------
>> 2 files changed, 13 insertions(+), 75 deletions(-)
>
> Any interest in taking this patch through the apparmor or security trees?
>
I can take it through my tree
Powered by blists - more mailing lists