T06 · System Persistence
- Location
REFERENCE.md:805- Finding
Persistent Scheduler Installation Through OS Startup Services
- Content
View full analysis
ProgramArguments /usr/local/bin/croncopilot start RunAtLoad KeepAlive ``` ```bash launchctl load ~/Library/LaunchAgents/com.croncopilot.agent.plist ``` The WSL guidance provides another persistence route: ```bash # To auto-start with WSL, add to ~/.bashrc or ~/.profile: croncopilot start --daemon 2>/dev/null || true ``` ### Technical Analysis The documentation establishes cross-session persistence through three platform-specific mechanisms: 1. A system-wide systemd unit enabled at boot with administrative commands. 2. A macOS LaunchAgent configured with both `RunAtLoad` and `KeepAlive`. 3. A shell startup entry that silently launches the scheduler whenever a WSL login shell starts. CronCopilot is explicitly designed to execute registered scripts on a schedule. Persisting the scheduler consequently persists the ability to execute every script referenced by its task database and configuration. The systemd definition follows least privil ...[truncated 2029 chars]- Remediation
View remediation
