<br><br><div><span class="gmail_quote">On 5/22/06, <b class="gmail_sendername">Graham Wood</b> <<a href="mailto:mythtv-users@spam.dragonhold.org">mythtv-users@spam.dragonhold.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Mon, May 22, 2006 at 01:11:43PM -0400, Dylan Semler wrote:<br>> Why is it so important to use ssh underneath? Can I verify that passing -e<br>> ssh to the rsync command is sufficient to tunnel it through ssh?<br>
The other options are rsyncd and rsh.<br><br>rsyncd means running another daemon on the server which is visible to the net (or at least<br>the machines you want to be able to access it). This is both a security risk (another
<br>possible attack vector) and unnecessary load on the server *grin*<br><br>rsh transmits usernames/passwords in clear text.<br><br>--<br><br>You can do a "ps -ef" on each end, and check to make sure that the two ends have ssh
<br>processes linked to the rsync ones. On the server you should see an sshd running as you<br>(IIRC) that has rsync as a child process.<br><br>On the client you should see an ssh process as a child of the rsync. You can also check
<br>open ports between the two servers to make sure that the connection is on port 22.<br><br>Graham</blockquote><div><br>Great, thanks for the help <br></div><br></div><br>