From: Paul Moore <paul@paul-moore.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: John Johansen <john.johansen@canonical.com>,
apparmor@lists.ubuntu.com,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [PATCH] apparmor: use SHA-256 library API instead of crypto_shash API
Date: Wed, 14 May 2025 17:57:52 -0400 [thread overview]
Message-ID: <CAHC9VhRL=Jsx8B1s-3qmVOXuRuRF2hTOi3uEnRiWra+7oQJvrg@mail.gmail.com> (raw)
In-Reply-To: <20250514042147.GA2073@sol>
On Wed, May 14, 2025 at 12:22 AM Eric Biggers <ebiggers@kernel.org> wrote:
> On Mon, Apr 28, 2025 at 12:04:30PM -0700, Eric Biggers wrote:
> > From: Eric Biggers <ebiggers@google.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@google.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
next prev parent reply other threads:[~2025-05-14 21:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 19:04 [PATCH] apparmor: use SHA-256 library API instead of crypto_shash API Eric Biggers
2025-05-14 4:21 ` Eric Biggers
2025-05-14 21:57 ` Paul Moore [this message]
2025-05-17 7:46 ` John Johansen
2025-05-17 7:43 ` John Johansen
2025-06-12 19:11 ` Eric Biggers
2025-06-22 21:16 ` John Johansen
2025-06-27 3:59 ` Eric Biggers
2025-06-27 6:14 ` John Johansen
2025-06-30 16:29 ` Eric Biggers
2025-05-17 7:42 ` John Johansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHC9VhRL=Jsx8B1s-3qmVOXuRuRF2hTOi3uEnRiWra+7oQJvrg@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=apparmor@lists.ubuntu.com \
--cc=ebiggers@kernel.org \
--cc=john.johansen@canonical.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).