From: michael.opdenacker@rootcommit.com
To: openembedded-devel@lists.openembedded.org
Cc: Michael Opdenacker <michael.opdenacker@rootcommit.com>
Subject: [meta-oe][scarthgap][PATCH] kernel-hardening-checker: update 0.6.10.2 -> 0.6.17.1
Date: Wed, 22 Apr 2026 12:06:48 +0200 [thread overview]
Message-ID: <20260422100648.2644983-1-michael.opdenacker@rootcommit.com> (raw)
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
Following the update on master.
This version reports more hardening issues:
128 "failures" instead of 113 on the same kernel.
Signed-off-by: Michael Opdenacker <michael.opdenacker@rootcommit.com>
---
...checker_0.6.10.2.bb => kernel-hardening-checker_0.6.17.1.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-oe/recipes-security/kernel-hardening-checker/{kernel-hardening-checker_0.6.10.2.bb => kernel-hardening-checker_0.6.17.1.bb} (96%)
diff --git a/meta-oe/recipes-security/kernel-hardening-checker/kernel-hardening-checker_0.6.10.2.bb b/meta-oe/recipes-security/kernel-hardening-checker/kernel-hardening-checker_0.6.17.1.bb
similarity index 96%
rename from meta-oe/recipes-security/kernel-hardening-checker/kernel-hardening-checker_0.6.10.2.bb
rename to meta-oe/recipes-security/kernel-hardening-checker/kernel-hardening-checker_0.6.17.1.bb
index c0ae0f0d3c..b83790ccb7 100644
--- a/meta-oe/recipes-security/kernel-hardening-checker/kernel-hardening-checker_0.6.10.2.bb
+++ b/meta-oe/recipes-security/kernel-hardening-checker/kernel-hardening-checker_0.6.17.1.bb
@@ -16,7 +16,7 @@ SRC_URI = "git://github.com/a13xp0p0v/kernel-hardening-checker;protocol=https;br
file://0001-pyproject.toml-fix-up-license-information.patch \
file://0002-pyproject.toml-relax-setuptool-version-requirement.patch"
-SRCREV = "0ebece346f187e7d3589883cc1d194fcd1c3cda8"
+SRCREV = "afc376f2a935994793343cfeb05953583cc30191"
S = "${WORKDIR}/git"
reply other threads:[~2026-04-22 10:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260422100648.2644983-1-michael.opdenacker@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.