Lawrence D. Dunn wrote:
Colleagues,
If you do pursue SSL functionality directly in rsync,
please be sure to take a look at Chris Rapier's work
to "fix" standard ssh implementations, at:
http://www.psc.edu/networking/projects/hpn-ssh/
Turns out "-e ssh" using most libraries puts a fixed-window-size
ssh-windowing
behavior on top of TCP - so for large bandwidth*delay product paths,
even if you use large TCP buffers (which Wayne added for such paths),
an "un-fixed" SSL library can clobber overall performance/throughput,
even for a perfectly clean (no errors/loss) path.
SSL != SSH.
--
Carson
--
To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html