Modified rsync over SSL patch

[Uri Simchoni]

Hi,
 
I've been working with Casey Marshall's SSL patch, and couldn't get it to work 
reliably - the transfer would abort pretty quickly. So I rewrote the main data 
pump loop of the patch to use non-blocking IO, and am attaching the new patch.
An rsync program using this patch is interoperable with the old patch.
 
Along with the modified message pump I added the following improvements:
- Buffering data to produce large SSL records (16K) to increase the 
encryption/decryption efficiency.
- Control of the SSL cipher list on the client via the RSYNC_SSL_CIPHERS 
environment variable
- Graceful termination in order to better pass last error messages from the 
server to the client
 
To use the patch (against 3.0.7):
 
    patch -p1 < rsync-openssl.diff
    ./prepare-source
    ./configure
    make
 
 
Enjoy,
Uri.

  
_
Hotmail: Trusted email with powerful SPAM protection.
https://signup.live.com/signup.aspx?id=60969

rsync-openssl.diff
Description: Binary data
-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html

Rsync / ssh high cpu load

[Jan Alphenaar]

Hi everybody,

I am using Cygwin rsync/ssh to synchronize my files from my home computer to
my server. I raised a question on the Cygwin list as well, but thought this
list would be appropriate too.

The issue is that the CPU on the sending side is fully allocated by
rsync/ssh (both taking 50%) during a file transfer. This is the command I
use:

rsync -e ssh * @:/data

After some more testing on this I figured out that rsync/ssh is only taking
the full cpu if the bandwidth allocated to the session exceeds the true
bandwidth available on the link.

For example, if the uplink is 128KB/s and I pass in the --bwlimit=24
parameter the cpu is around 0%. Even --bw-limit=126 does not take 100% cpu,
but --bwlimit=132 does. Note this is the first install, the /data directory
on the receiving side is empty.

Would this be because of packet loss on the link and packets have to be
retransmitted ? I will do a quick test tonight with rsync/ssh between two
linux boxes (without cygwin), see what that gives me.

Note that I am using these versions:

Cygwin: 1.7.1-1
ssh: OpenSSH_5.3p1
rsync: 3.0.6

Has anybody seen this before ?

Thanks in advance.

Regards,

Jan

-- 
Please use reply-all for most replies to avoid omitting the mailing list.
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html