3 ms·
Set up a Raspberry Pi or something, with the SSH server running in a container (to prevent exploiting privileged processes through Unix domain sockets), under a
by josephcsible 4y ago
Set up a Raspberry Pi or something, with the SSH server running in a container (to prevent exploiting privileged processes through Unix domain sockets), under an unprivileged user, and with PR_SET_NO_NEW_PRIVS enabled. Do not have any ports exposed to the outer host, not even an SSH server on the outer host or any other means of administering it over the network. Rsync your backups to the container, and have a cron job run as root on the host that takes Btrfs snapshots of the backup drive every day. Even knowing the root password wouldn't let a remote attacker modify or delete your old backups. The only way they could is if they exploited a vulnerability in the Linux kernel itself (and an information disclosure one wouldn't be sufficient).