Rsync fails with (very) old server.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rsync (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Does not work:
Trusty Tahr.
Rsync version 3.1.0
Protocol version 31
DOES work:
Saucy
rsync version 3.0.9
protocol version 30
In both cases: "server side":
Suse 7.0
version 2.3.2
protocol version 21
with both "client" side rsyncs I of course get:
> Server is very old version of rsync, upgrade recommended.
but with the newer rsync I get:
Warning: No xauth data; using fake authentication data for X11 forwarding.
Server is very old version of rsync, upgrade recommended.
protocol version mismatch - is your shell clean?
(see the rsync man page for an explanation)
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.0]
According to the manpage I can test the "is your shell clean" with
ssh oldserver /usr/bin/true > out.dat
but I get a clean file (0 bytes).
I just checked: the "no xauth data" doesn't matter:
rsync -e "ssh -x" vsuse:/etc/issue .
has the same problems.
Thank you for taking the time to report this bug and helping to make Ubuntu better.
I think the appropriate next step to take with this bug would be to try and reproduce this with rsync built from the upstream tarball, with no distribution packaging.
If it still does not work with the latest upstream, then this bug will need to go upstream.
If this cannot be reproduced with a clean upstream binary, then we'll need to investigate what broke this in Ubuntu.
Are you able to test this case, please?