fa7f4e011ab0b76d74198bdc280ebb5afd0cfec8
checkRecursiveDelete compared the raw segment name, `seg.Name != "rm"`, while every sibling rule in the same table resolves the command through baseName -- checkMkfs, checkBlockDeviceWrite, checkKillAll, checkSystemPower, checkSelfTermination and checkDaemonLaunch all call baseName(seg.Name), and baseName's own doc says its purpose is that /sbin/reboot and reboot are judged the same. The test suite already pinned that convention for /sbin/poweroff. Because tokenise yields the raw first word, `/bin/rm -rf /` produced seg.Name == "/bin/rm", the rule declined, no other rule matched, and Hardline returned nil. Since provider/builtin calls command.Hardline on the shell tool's command field before every execution, an absolute path defeated the recursive-root-delete gate entirely. `/bin/rm -rf /etc` (any critical path, not just the root) was equally reachable; an overlay probe confirmed both, and confirmed the sibling /sbin/poweroff case was already correct. Resolve through baseName, matching the rest of the rule table, and add table cases for absolute-path rm plus an allow case for an ordinary absolute-path recursive delete so the normalisation cannot over-block. Found by an adversarial package sweep (temp tracker: tools-command-1, .local/issue-tracker/).
Description
Archie connects events from your systems to agents that can investigate, reason, and act.
Define what an event means, map its data into a workflow, and give that workflow an agent equipped for the job: its own execution environment, tools, and identity.
https://archie.catlow.cloud
133 MiB
0 Stars
1 Watchers
0 Forks
Releases
11
Archie v1.62.0
Latest
Languages
Go
76.7%
Vue
13.1%
TypeScript
7.8%
JavaScript
1.2%
Shell
0.6%
Other
0.4%