Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#76278 - [rsync] 3.2.7-1 breaks compatibility with rsync 2.6.8
Attached to Project:
Arch Linux
Opened by Stephan von Krawczynski (skraw) - Sunday, 23 October 2022, 23:42 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 22 July 2023, 13:59 GMT
Opened by Stephan von Krawczynski (skraw) - Sunday, 23 October 2022, 23:42 GMT
Last edited by Jelle van der Waa (jelly) - Saturday, 22 July 2023, 13:59 GMT
|
DetailsDescription:
Using rsync-3.2.7-1 as daemon and trying to connect with a client rsync 2.6.8 ends up in this error message: @ERROR: auth failed on module XXXX rsync error: error starting client-server protocol (code 5) at main.c(1308) [sender=2.6.8] Going back to rsync-3.2.6-2 makes it work again. Additional info: * package version(s) * config and/or log files etc. Daemon rsyncd.conf: gid = root uid = root read only = false use chroot = true transfer logging = true log format = %a %h %o %f %l %b log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid #hosts allow = trusted.hosts #slp refresh = 300 #use slp = false secrets file = /etc/rsyncd.secrets #protocol = 29 hosts allow = 192.168.0.0/16 hosts deny = ALL list = false [XXXX] path = /some path auth users = XXXX hosts allow = 192.168.C.D * link to upstream bug report, if any Steps to reproduce: Just connect and try to rsync something with 2.6.8 . |
This task depends upon
[1] https://github.com/WayneD/rsync/issues
From the changelog:
The checksum code now uses openssl's EVP methods, which gets rid of various deprecation warnings and makes it easy to support more digest methods. On newer systems, the MD4 digest is marked as legacy in the openssl code, which makes openssl refuse to support it via EVP. You can choose to ignore this and allow rsync's MD4 code to be used for older rsync connections (when talking to an rsync prior to 3.0.0) or you can choose to configure rsync to tell openssl to enable legacy algorithms (see below).
A simple openssl config file is supplied that can be installed for rsync to use. If you install packaging/openssl-rsync.cnf to a public spot (such as /etc/ssl/openssl-rsync.cnf) and then run configure with the option --with-openssl-conf=/path/name.cnf, this will cause rsync to export the configured path in the OPENSSL_CONF environment variable (when the variable is not already set). This will enable openssl's MD4 code for rsync to use.