Updated Backup to rsync.net via ZFS (markdown)
@ -92,15 +92,11 @@ Although rsync.net is a very professional and trustworthy company, i still will
|
||||
|
||||
* The rsync staff can login to your VM to support your machine, so this means they can easily access your data. Even if you use encryption, as long as the key is loaded on the target they could access your data.
|
||||
* You're allowed to deny them access by removing they ssh key. (but this can have some other implications, like updates and support)
|
||||
* To make absolutely sure your data is safe, you should encrypt your data on the source side. (on your server) This will be send over in encrypted form to rsync.net
|
||||
|
||||
|
||||
|
||||
* To make absolutely sure your data is safe without denying anyone access, you should encrypt your data on the source side. (on your server) This will be send over in encrypted form to rsync.net
|
||||
|
||||
### Crypto ware
|
||||
|
||||
* If you use a push-backup, you are not secured against hackers: If they hack your server, they will have access to your rsync.net server as well.
|
||||
* You can actually let the rsync.net server login to your server and pull the backup. Keep in mind that in that case the rsync.net staff could access your server. (or in case your the backup server gets hacked)
|
||||
|
||||
### Pull backup
|
||||
|
||||
* You can actually let the rsync.net server login to your server and pull the backup. Keep in mind that
|
||||
|
||||
Reference in New Issue
Block a user