I've configured something usually advised against, but so far I have evaluated it seems perfectly safe to me. I'd like some opinions since playing with non-encrypted connections for my very sensitive data can be disastrous.
Here's my configuration:
- I've set up an rsyncd daemon on my backup server and defined a single backup target in /etc/rsyncd.conf; I don't want to use rsync over SSH since the backup server disallows SSH password logins
- The destination for the backup module is /home//.directory used exclusively for this purpose
- I've setup a /etc/rsyncd.secrets with plaintext username:password pair used exclusively for this purpose and not matching any local username; Owner: root, permissions 600
- I've opened up the configured non-standard rsyncd port with iptables but with a source (-s) restriction of just my NAS
The way I'm using this is:
- In my Synology NAS, I've defined an unencrypted remote rsync target in my the Hyper Backup service to connect to the respective remote rsyncd port
- I've enabled "client-side encryption" when defining the backup details. As far as I've read up on the way it works, it means the .hbk file it creates and transfers can only be unlocked either using the password, or the private key of specifically the Synology NAS that created it.
- I've used a very strong passphrase when defining that backup's encryption
- Since I'm using a daily local backup as another Hyper Backup task, I've configured this to happen just once per week as an off-site reassurance
Can you please consider the above and let me know if I'm right in my thoughts that it's safe to use this non-encrypted connection in this manner?
I have so far enabled it for just a small portion of my data, but I'm planning to extend it to all my sensitive personal data as soon as I get your advice :-) Thanks in advance.