Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision Next revisionBoth sides next revision | ||
mobi_2.0 [31.12.2020 00:28] – created Pascal Suter | mobi_2.0 [31.12.2020 08:51] – [self-made collection of other tools] Pascal Suter | ||
---|---|---|---|
Line 56: | Line 56: | ||
* 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 upon restore. the share should be mountable on the client, so that we can use again gocryptfs to decrypt the backup before restoring files. Maybe NFS piped through ssh or something similar might be a solution. | + | * provide a read-only share via rsync daemon where the client can access all its backups to restore files from. --> |
* 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: | ||
+ | * **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 to change at least file ownership to a dedicated user and limit the possibilities for an attack | ||
+ | * **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 '' | ||
+ | * it would be nice to be able to mount an entire backup, or even all backups at once, via for example sshfs. One could then remount it using gocryptfs on the client to see a decrypted representation. however, this brings another isse: the mount should be read-only, so that a hacked client can't destroy existing backups on the backup server. so either we find a way to create a read-only share using for example NFS (possibly tunnelled over ssh) or we find a way to make them read-only on the backup server already before sharing them through sshfs. | ||
+ | * i have found [[https:// | ||