Package: rsync
Version: 3.1.1-3+deb8u1
Severity: important

Dear Maintainer,

I am using rsyncd via inetd. Worked fine before latest update for years.
Now I get:

attempt to hack rsync failed.
rsync error: protocol incompatibility (code 2) at receiver.c(586) 
[receiver=3.1.1]
rsync error: protocol incompatibility (code 2) at io.c(1633) [generator=3.1.1]

This always happens when sending to the server after a while of inactivity
(old start of rsyncd?). It does never happen when 1st receiving and then sending
within a short period. My inetd command is:

rsync  stream tcp nowait root  /usr/bin/rsync    rsync --daemon

The client command is (sorry for bad line-splitting):

rsync --archive --protect-args --out-format=%o %n%L --exclude=/backup/*** 
--exclude=.
   * --exclude=*~ --exclude=*.pyc --include=/archived/ 
--include=/archived/centauri/ --i
   nclude=/archived/centauri/alpha7 --include=/configs/ 
--include=/configs/jessie/ --inc
   lude=/configs/jessie/@admin/*** --include=/configs/jessie/centauri/*** 
--exclude=* --
   backup --backup-dir=backup/centauri --compress --fuzzy --hard-links --update 
--delete
   -after --dry-run /var/centauri/ root@alpha::@centauri

Thanks for your attention
Jürgen

-- System Information:
Debian Release: 8.10
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-0.bpo.4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages rsync depends on:
ii  base-files  8+deb8u10
ii  libacl1     2.2.52-2
ii  libattr1    1:2.4.47-2
ii  libc6       2.19-18+deb8u10
ii  libpopt0    1.16-10
ii  lsb-base    4.1+Debian13+nmu1

rsync recommends no packages.

Versions of packages rsync suggests:
ii  openssh-client  1:6.7p1-5+deb8u4
ii  openssh-server  1:6.7p1-5+deb8u4

-- Configuration Files:
/etc/default/rsync changed:
RSYNC_ENABLE=inetd
RSYNC_OPTS=''
RSYNC_NICE=''


-- no debconf information

Reply via email to