Your message dated Thu, 12 Mar 2009 11:24:07 +0100
with message-id <20090312102407.ga17...@msgid.wurtel.net>
and subject line Re: Bug#519398: rsync: 'insecure -e option not allowed' after
upgrade to lenny
has caused the Debian Bug report #519398,
regarding rsync: 'insecure -e option not allowed' after upgrade to lenny
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
519398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=519398
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rsync
Version: 2.6.9-2etch2
Severity: grave
Justification: renders package unusable
Sanitised expect log from backup script...
spawn /usr/bin/rsync -bv x...@www.www:~/dbbackup/* /home/data/xx/dbbackup/
Password:
insecure -e option not allowed.
This account is restricted by rssh.
Allowed commands: sftp rsync
If you believe this is in error, please contact your system administrator.
*** glibc detected *** malloc(): memory corruption: 0x08051bc8 ***
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(635)
[receiver=3.0.3]
total 5172
note please that the -e option is not used!
My workround is to revert to rsync from oldstable:
spawn /usr/bin/rsync -bv x...@www:~/dbbackup/* /home/data/xxx/dbbackup/
Password:
xxx.yyy
sent 9030 bytes received 709948 bytes 287591.20 bytes/sec
total size is 1972930 speedup is 2.74
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages rsync depends on:
ii libacl1 2.2.47-2 Access control list shared library
ii libc6 2.7-18 GNU C Library: Shared libraries
ii libpopt0 1.14-4 lib for parsing cmdline parameters
ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip
rsync recommends no packages.
Versions of packages rsync suggests:
ii openssh-client 1:5.1p1-5 secure shell client, an rlogin/rsh
ii openssh-server 1:5.1p1-5 secure shell server, an rshd repla
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu 12 Mar 2009, Bernard Elbourn wrote:
> Package: rsync
> Version: 2.6.9-2etch2
Really?
The message you include shows 3.0.3.
I'm assuming you downgraded rsync but didn't check the version that was
reported.
> Severity: grave
> Justification: renders package unusable
Thousands (hunderds of thousands? Millions? ;-) of people are using it just
fine,
it's just that _you_ ran into a problem. By that criterium almost every
bug should be grave.
> Sanitised expect log from backup script...
>
> spawn /usr/bin/rsync -bv x...@www.www:~/dbbackup/* /home/data/xx/dbbackup/
> Password:
>
> insecure -e option not allowed.
> This account is restricted by rssh.
> Allowed commands: sftp rsync
It sounds like the remote rssh is not updated to allow for the changed
options that the local rsync sends to the remote system.
This is not a bug in rsync, but a problem with rssh. See:
http://lists.samba.org/archive/rsync/2008-March/020273.html
http://lists.samba.org/archive/rsync/2008-March/020274.html
Paul
--- End Message ---
