rsync 3.0.3 fails with rssh to some older servers

Bug #302403 reported by vroetman on 2008-11-26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
rsync (Ubuntu)

Bug Description

Binary package hint: rsync

Using rsync 3.0.3-2ubuntu1 on intrepid over rssh to a version 2.6.6 server,
rsync -a directory user@server:~/
fails with "insecure -e option not allowed."

This can be worked around with --protocol=29 but it has been fixed in rsync 3.0.4 (where the announcement says, "Rsync version 3.0.4 has been released. This is a bug-fix release with the only enhancement being the adding of a way to interact with an overly-restrictive server that refuses rsync's behind-the-scenes use of the -e option.")

Can we fix this for intrepid, or if not at least put 3.0.4 in the backports?

aporter (aporter) wrote :

I'm using rsync 3.0.7 and I still see this problem so it's not fixed in 3.0.7. Your workaround "--protocol=29" DOES work with rssh. I can help provide more information about this observation.

Changed in rsync (Ubuntu):
status: New → Confirmed
Petar Maric (petar-maric) wrote :

I too can confirm both the issue and the workaround on a freshly installed and updated Ubuntu 10.04 LTS 64bit Rackspace Cloud Server (used as a client, running rsync 3.0.7) connecting to a Debian server which is running rsync 2.6.9

Please let me know if I can help in any way, as this bug was really painful to track down.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers