Files
SKELETONKEY/modules/_stubs/fragnesia_TBD/MODULE.md
T
leviathan 9593d90385
release / build (arm64) (push) Waiting to run
release / build (x86_64) (push) Waiting to run
release / release (push) Blocked by required conditions
rename: IAMROOT → SKELETONKEY across the entire project
Breaking change. Tool name, binary name, function/type names,
constant names, env vars, header guards, file paths, and GitHub
repo URL all rebrand IAMROOT → SKELETONKEY.

Changes:
  - All "IAMROOT" → "SKELETONKEY" (constants, env vars, enum
    values, docs, comments)
  - All "iamroot" → "skeletonkey" (functions, types, paths, CLI)
  - iamroot.c → skeletonkey.c
  - modules/*/iamroot_modules.{c,h} → modules/*/skeletonkey_modules.{c,h}
  - tools/iamroot-fleet-scan.sh → tools/skeletonkey-fleet-scan.sh
  - Binary "iamroot" → "skeletonkey"
  - GitHub URL KaraZajac/IAMROOT → KaraZajac/SKELETONKEY
  - .gitignore now expects build output named "skeletonkey"
  - /tmp/iamroot-* tmpfiles → /tmp/skeletonkey-*
  - Env vars IAMROOT_MODPROBE_PATH etc. → SKELETONKEY_*

New ASCII skeleton-key banner (horizontal key icon + ANSI Shadow
SKELETONKEY block letters) replaces the IAMROOT banner in
skeletonkey.c and README.md.

VERSION: 0.3.1 → 0.4.0 (breaking).

Build clean on Debian 6.12.86. `skeletonkey --version` → 0.4.0.
All 24 modules still register; no functional code changes — pure
rename + banner refresh.
2026-05-16 22:43:49 -04:00

850 B

Fragnesia — CVE pending

PLANNED stub. See ../../ROADMAP.md Phase 7+.

Summary

ESP shared-frag in-place encrypt path can be coerced into writing into the page cache of an unrelated file. Same primitive shape as Dirty Frag, different reach.

Status

Audit-stage. See security-research/findings/audit_leak_write_modprobe_backups_2026-05-16.md section on backup primitives. Notably: trigger appears to require CAP_NET_ADMIN inside a userns netns. On kCTF (shared net_ns) that's cap-dead, but on host systems where user_ns clone is enabled it's reachable.

Decision needed before implementing

Is the unprivileged-userns-netns scenario in scope for SKELETONKEY? If yes, this module ships. If we restrict to "default Linux user account, no namespace tricks," this module is out of scope.

Not started.