T06 · System Persistence
- Location
SKILL.md:44- Finding
Persistent Scheduled Task Installation Without Lifecycle Safeguards
- Content
View full analysis
~/.config/systemd/user/pilot-task.timer </dev/null | grep -v 'pilot-cron' > /tmp/crontab.tmp || true cat >> /tmp/crontab.tmp <> $HOME/.pilot/logs/health-check.log 2>&1 EOF crontab /tmp/crontab.tmp ``` ### Technical Analysis The Skill explicitly modifies the user's persistent scheduling configuration through `crontab` and an enabled systemd user timer. These jobs survive the Skill invocation and continue executing commands under the user's account without renewed authorization. Recurring scheduling is consistent with the Skill's declared purpose, so the persistence is not concealed or unrelated functionality. Nevertheless, the examples install persistent execution directly rather than first generating a preview or requesting confirmation immediately before installation. They also lack expiration controls, integrity validation for referenced scripts, duplicate-entry protection in the basic examples, and documented removal procedures. The systemd timer sets `Persistent=true`, which can cause a missed invocation to run after the user timer manager resumes. The shown timer is also incomplete because no corresponding `pilot-task.service` unit is defined. The cron workflow repeatedly discovers a Pilot peer and submits a network task every five ...[truncated 1513 chars]- Remediation
View remediation
