[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHC9VhRL=Jsx8B1s-3qmVOXuRuRF2hTOi3uEnRiWra+7oQJvrg@mail.gmail.com>
Date: Wed, 14 May 2025 17:57:52 -0400
From: Paul Moore <paul@...l-moore.com>
To: Eric Biggers <ebiggers@...nel.org>
Cc: John Johansen <john.johansen@...onical.com>, 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 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.
--
paul-moore.com
Powered by blists - more mailing lists