I have set up an Rsync server on FreeBSD 5.3 and plan on having windows clients synchronize data to it. Rsync running as a daemon works fine. I can successfully copy data up to the server and view it via scp. Also- I can connect via ssh and run rsync as well. HOWEVER- I cannot connect "passwordless" with SSH and then connect to the rsync daemon. The following demonstartes what I would like to do: rsync -av -e "ssh -l myusername" "/cygdrive/pathtolocaldata" rsyncusername@3.3.3.3::modulename --password-file filename When I run the above I successfully authenticate with SSH but then I get an error that the rsyncd.conf cannot be read. Permissions on the rsyncd.conf file are root:wheel -rw-r------ I have tried chown to rsync:rync the user the daemon runs under as specified in my conf file. I would like the have the granularity of using rsyncd.conf. I was somewhat content with just using ssh but ssh wants to change the permissions on the upload directory where others can rwx. I tried changing the umask but apparently it is ignored when making an ssh connection. In addition- the local accounts on the server are setup for scponly. Any help would be greatly appreciated. I have been googling and experimenting for over two weeks. I believe everything is proper... :( TIA __________________________________ Do you Yahoo!? Yahoo! Mail - 250MB free storage. Do more. Manage less. http://info.mail.yahoo.com/mail_250
Hi, FAQ at http://www.itefix.no/phpws/index.php?module=faq&FAQ_op=view&FAQ_id=27 may help. Rgrds Tev cwRsync maintainer> -----Original Message----- > From: rsync-bounces+tevfik=itefix.no@lists.samba.org > [mailto:rsync-bounces+tevfik=itefix.no@lists.samba.org] On > Behalf Of d c > Sent: 19. desember 2004 04:28 > To: rsync@lists.samba.org > Subject: SSH Tunnel Problem > > I have set up an Rsync server on FreeBSD 5.3 and plan on > having windows clients synchronize data to it. > > Rsync running as a daemon works fine. I can successfully > copy data up to the server and view it via scp. > > Also- I can connect via ssh and run rsync as well. > > HOWEVER- I cannot connect "passwordless" with SSH and then > connect to the rsync daemon. The following demonstartes what > I would like to do: > > rsync -av -e "ssh -l myusername" > "/cygdrive/pathtolocaldata" > rsyncusername@3.3.3.3::modulename --password-file filename > > When I run the above I successfully authenticate with SSH but > then I get an error that the rsyncd.conf cannot be read. > Permissions on the rsyncd.conf file are > > root:wheel -rw-r------ > > I have tried chown to rsync:rync the user the daemon runs > under as specified in my conf file. > > > I would like the have the granularity of using rsyncd.conf. > > I was somewhat content with just using ssh but ssh wants to > change the permissions on the upload directory where others > can rwx. I tried changing the umask but apparently it is > ignored when making an ssh connection. > > In addition- the local accounts on the server are setup for > scponly. > > Any help would be greatly appreciated. I have been googling > and experimenting for over two weeks. I believe everything > is proper... :( > > TIA > > > > __________________________________ > Do you Yahoo!? > Yahoo! Mail - 250MB free storage. Do more. Manage less. > http://info.mail.yahoo.com/mail_250 > -- > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: > http://www.catb.org/~esr/faqs/smart-questions.html >
On Sat, Dec 18, 2004 at 07:28:24PM -0800, d c wrote:> HOWEVER- I cannot connect "passwordless" with SSH and then connect to > the rsync daemon.If you combine daemon-syntax with ssh, you spawn a new rsync daemon that will be run by the ssh program, so it needs its own rsyncd.conf file (which must be in the logged-in user's home directory by default). If you want to talk to an existing rsync daemon using an encoded socket, you need to use some kind of tunnel, such as this one using ssh: ssh -f -i ~/.ssh/id_dsa -C -l SOMEUSER -L 8730:localhost:873 SOMEHOST sleep 40 rsync -av rsync://localhost:8730/module /dest That will connect to port 8730 on the localhost, which ssh forwards over its connection to SOMEHOST, and that machine then connects to port 873 on "localhost". Changing the "localhost" in the -L option would change what machine the remote end of the tunnel connects with, which would allow you to ssh into REMOTEHOST and have it connect to port 873 on some other machine on REMOTEHOST's network. If you're using the ssh2 protocol, you should also be able to use the -N option to ssh instead of the "sleep 40" command. ..wayne..