From 5be3c46719248e8daa8a0ad856246b4efb1a3cfb Mon Sep 17 00:00:00 2001 From: KaraZajac Date: Sun, 17 May 2026 02:24:06 -0400 Subject: [PATCH] =?UTF-8?q?CONTRIBUTING:=20fix=20stale=20IAMROOT=5FEXPLOIT?= =?UTF-8?q?=5FOK=20=E2=86=92=20SKELETONKEY=5FEXPLOIT=5FOK?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Two references missed during the IAMROOT → SKELETONKEY rename in v0.4.0. The enum value in core/module.h is SKELETONKEY_EXPLOIT_OK. --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a7b7e51..5046974 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -48,7 +48,7 @@ Use any existing module as a template. Lightest-weight reference: Mandatory: - Detect short-circuits cleanly on patched kernels (we test this) - `--i-know` gate on exploit -- Honest scope: `IAMROOT_EXPLOIT_OK` only after empirical root, +- Honest scope: `SKELETONKEY_EXPLOIT_OK` only after empirical root, otherwise `EXPLOIT_FAIL` with diagnostic - `NOTICE.md` crediting the original CVE reporter + PoC author @@ -72,7 +72,7 @@ vulnerable. ## What we don't accept -- Untested code paths claiming `IAMROOT_EXPLOIT_OK` +- Untested code paths claiming `SKELETONKEY_EXPLOIT_OK` - Per-kernel offsets fabricated without verification - Modules without detection rules - 0day disclosures (responsible disclosure first; bundle here