[scponly] disconnects with rsync-3.0 and scponly

[Kaleb Pederson]

Hello,

John at http://rsync.net notified me a couple of days ago that support for 
rsync-3.0 was broken.  I have confirmed that it was an issue and I have fixed 
it in CVS, after confirming on the rsync mailing list that '-e' when used as 
a server option (eg. with --server also present) is safe.

A new snapshot is available at sourceforge (Note: although it has been 
uploaded, it hasn't synced across the Sourceforge servers yet, so I haven't 
yet confirmed it was uploaded correctly. I'll follow up later today.)

The checksums for scponly-20080308.tgz are:

m5dsum: f1eb94c7588e878df806b63aa8348174
sha1sum: 9e12162d5e62975e00b2379336bf68f2b7aebbf6

For interested parties, a patch to scponly-4.8 is also attached.

Please let me know if you run into any problems with it.

Thanks.

--Kaleb
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rsync-3.0.patch
Type: text/x-diff
Size: 5873 bytes
Desc: not available
Url : https://lists.ccs.neu.edu/pipermail/scponly/attachments/20080308/ec5314ab/attachment.bin