Restic Home Backup (Safe Apply Mode)

Design, implement, and operate encrypted restic backups for Linux home directories with systemd automation, retention policies, and restore validation. Use w...

This skill appears to do what it says, but follow these precautions before applying changes: (1) Review scripts/bootstrap_restic_home.sh locally in plan-only mode (run without --apply) to confirm paths/schedules. (2) Ensure restic is installed at /usr/bin/restic (or edit scripts to your restic path). (3) Be aware applying (--apply) writes files under /etc and /usr/local/bin and installs systemd units which will run as root—confirm this matches your security policy. (4) If you intend to use a remote backend (S3/B2/sftp), plan how repository credentials will be provided (the script currently generates/stores a local password file but does not manage cloud credentials). (5) After apply, verify permissions on /etc/restic-home/* (should be 600) and perform the restore smoke test described in the ops checklist. (6) If unsure, run in plan-only mode and manually inspect generated artifacts before using --apply. If you want a more restrictive setup (non-root service user, SELinux/AppArmor constraints, or integration with your secret manager), request those explicit changes before applying.

Type: OpenClaw Skill Name: restic-home-backup-safe Version: 1.0.0 The skill bundle is designed for a legitimate purpose (restic home backups) and implements strong safety boundaries, notably requiring an explicit `--apply` flag for system changes, as documented in SKILL.md. However, the `scripts/bootstrap_restic_home.sh` script directly uses user-provided inputs like `--user` (for `USER_NAME`) and `--timezone` (for `TIMEZONE`) in path constructions and systemd unit files without explicit sanitization. While the script's intent is benign, this lack of input validation presents a vulnerability that could potentially be exploited via prompt injection against the AI agent, leading to path traversal or command injection if malicious inputs are crafted for these parameters and downstream commands are not sufficiently robust.