One way that works for both rsh and ssh is to enable host-based authentication, which would allow all connections from the middle system to the target system to succeed (when the username remains the same). To effect this extra hop, you’ll need to make sure that the remote-shell connection from the middle system to the target system does not involve any tty-based user interaction (such as prompting for a password) because there is no way for the middle system to access the local user’s tty. ssh) to access the middle system and have it use a remote shell to hop over to the actual target system. If you have a setup where there is no way to directly connect two systems for an rsync transfer, there are several ways to use the firewall system to act as an intermediary in the transfer. I’m using their “Method 2” since I only need to sync against a filesystem target.
#RSYNC WITH SSH PROXY HOW TO#
Sure enough, the rsync FAQ has some good information on how to do this. Since several sites reside behind firewalls, I needed to find a way to tunnel rsync traffic through an ssh hop.
CVS is too much of a pain with blog-driven sites that create static pages. I’ve been experimenting various approaches to keep my remote/local sites in sync.
0 kommentar(er)
