I decided that the best way to handle rsync security is with rsync in daemon mode, over ssh, with sudo. The advantages are that rsync daemon mode allows for chroot and a lot of access controls, but running a normal rsync daemon could leave some local access security holes, and id very restricted by many SELinux security configurations.
I now have set up an ssh authorized_key to an unprivileged account, which runs sudo to start rsync in daemon mode, with a specific rsyncd.conf. (Earlier, I didn't realize that sudo can limit command arguments as well as executables.) The rsyncd.conf enforce restrictions better than my previous attempt at an rsync proxy command. I have this working for BackupPC. It required a bit of hacking to merge rsync and rsyncd connections in File::RsyncP.pm, which is implemented outside of the RsyncP.pm module. I hacked the option to use it into BackupPC/Xfer/Rsync.pm by using this method when rsyncd is selected with a port value of zero. Joe Krahn ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ BackupPC-users mailing list [email protected] List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
