From b5b197aab6ac548159314f57bc9c50e9eee4b851 Mon Sep 17 00:00:00 2001 From: Ashlen Date: Wed, 15 Jul 2026 12:54:05 -0600 Subject: [PATCH] fix(remove-system.map): skip read-only files instead of aborting The read-only branch of the deletion loop calls `exit 0`, which terminates the whole script on the first non-writable System.map. Later writable copies (for example under /usr/src or /lib/modules) are then never shredded, and the "Done. Success." summary is skipped while the exit code still reports success -- a false all-clear that can leave a kernel symbol map on disk. Replace `exit 0` with `continue` so each read-only file is noted and the loop proceeds to the remaining locations. The script's exit code is unchanged, so callers are unaffected. --- .../security-misc/remove-system.map#security-misc-shared | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/usr/libexec/security-misc/remove-system.map#security-misc-shared b/usr/libexec/security-misc/remove-system.map#security-misc-shared index 5b75f6de..ad0c34a1 100755 --- a/usr/libexec/security-misc/remove-system.map#security-misc-shared +++ b/usr/libexec/security-misc/remove-system.map#security-misc-shared @@ -32,7 +32,7 @@ for filename in ${system_map_location} ; do echo "INFO: removed '${filename}'" else echo "NOTE: Cannot delete '${filename}' - read-only. For details, see: https://www.kicksecure.com/wiki/security-misc#system_map" - exit 0 + continue fi fi done