[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <bcd712e1-5894-4ffd-865a-d8de33aed1a6@canonical.com>
Date: Sat, 17 May 2025 00:46:45 -0700
From: John Johansen <john.johansen@...onical.com>
To: Paul Moore <paul@...l-moore.com>, Eric Biggers <ebiggers@...nel.org>
Cc: apparmor@...ts.ubuntu.com, 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/14/25 14:57, Paul Moore wrote:
> On Wed, May 14, 2025 at 12:22 AM Eric Biggers <ebiggers@...nel.org> 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?
>
> Something like this would need to go through the AppArmor tree. As a
> FYI, the AppArmor devs are fairly busy at the moment so it may take a
> bit for them to get around to this.
>
I am going to see how much of the backlog I can get through while traveling
replies might get batch because I will be mostly off line but hopefully
I can deal with most of it this weekend.
Powered by blists - more mailing lists