Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revisionBoth sides next revision | ||
rethinking_my_backup_strategy [01.01.2021 18:51] – [Design Goals for Mobi 2.0] Pascal Suter | rethinking_my_backup_strategy [01.01.2021 22:12] – [self-made collection of other tools] Pascal Suter | ||
---|---|---|---|
Line 63: | Line 63: | ||
* use rsync daemon on the server to provide access to the backup repos for each of the clients. | * use rsync daemon on the server to provide access to the backup repos for each of the clients. | ||
* use '' | * use '' | ||
- | * provide a read-only share via rsync daemon where the client can access all its backups to restore files from. --> **this needs some more thinking / research**, as the backups will contain encrpyted file- and directory names as well as data.. so we would need some other means of sharing the backups in read-only mode but that will retain the orignal linux permissuons | + | * provide a read-only share via rsync daemon where the client can access all its backups to restore files from. --> **this needs some more thinking / research**, as the backups will contain encrpyted file- and directory names as well as data.. so we would need some other means of sharing the backups in read-only mode but that will retain the orignal linux permissions |
* use the same set of tools again to create backups from the primary backup server to the secondary. | * use the same set of tools again to create backups from the primary backup server to the secondary. | ||
Unsolved issues of this solution: | Unsolved issues of this solution: | ||
- | * **file ownership** is retained on all the files, so a file belonging to root on the client will belong to root on the backup server.. this brings some security issues, as for example a privilege escalation could be made possible by backing up a copy of bash belonging to root and with the suid bit set.. once the attacker gets unprivileged user access to the backup server, he could start this shell and become root. So it would be preferrable | + | * **file ownership** is retained on all the files, so a file belonging to root on the client will belong to root on the backup server.. this brings some security issues, as for example a privilege escalation could be made possible by backing up a copy of bash belonging to root and with the suid bit set.. once the attacker gets unprivileged user access to the backup server, he could start this shell and become root. So it would be preferable |
* **restoring files and browsing backups** needs to be simple. for example it should be possible to either use normal '' | * **restoring files and browsing backups** needs to be simple. for example it should be possible to either use normal '' | ||
* backups are encrypted before rsync lays a hand on the file, so '' | * backups are encrypted before rsync lays a hand on the file, so '' |