On Tue, 2005-11-29 at 12:08, Tom Trelvik wrote: > > If you are using ssh as a transport or simlar then you have to have the > > client running an ssh daemon listening for connections before the server > > can make an rsync connection over it. Thus you still have to run a > > daemon of some kind, and this will still be running on the untrusted > > network also. > > Yes, but ssh security has proven very robust. =) > > I know, I'm going out of my way here, doing things the difficult way. > But I'm a security nut, and I believe in the importance of that. Most > of the security referenced in the rsyncd approach is simply obscurity.
If you are willing to waste a bunch of disk space (which is actually pretty cheap these days), you can set up a Linux server and run scheduled rsync-over-ssh from the windows boxes to it (the Cygwin version works fine that direction). Then let backuppc pick up the copy from the linux box for the older archives again using rsync over ssh. I do this in some remote offices to keep a local copy for quick access and to allow compression with the -C option to ssh which you can't do with rsyncd. -- Les Mikesell [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
