Slackware: 2004-285-01: rsync Security Update
Summary
Here are the details from the Slackware 10.0 ChangeLog: patches/packages/rsync-2.6.3-i486-1.tgz: Upgraded to rsync-2.6.3. From the rsync NEWS file: A bug in the sanitize_path routine (which affects a non-chrooted rsync daemon) could allow a user to craft a pathname that would get transformed into an absolute path for certain options (but not for file-transfer names). If you're running an rsync daemon with chroot disabled, *please upgrade*, ESPECIALLY if the user privs you run rsync under is anything above "nobody". Note that rsync, in daemon mode, sets the "use chroot" to true by default, and (in this default mode) is not vulnerable to this issue. I would strongly recommend against setting "use chroot" to false even if you've upgraded to this new package. (* Security fix *)
Where Find New Packages
Updated package for Slackware 8.1:
Updated package for Slackware 9.0:
Updated package for Slackware 9.1:
Updated package for Slackware 10.0:
Updated package for Slackware -current:
MD5 Signatures
Slackware 8.1 package:
294325c65e77660c1013d6b7f731d09a rsync-2.6.3-i386-1.tgz
Slackware 9.0 package:
e6c14f5e26845319d6299aa10dc94d25 rsync-2.6.3-i386-1.tgz
Slackware 9.1 package:
0404feb5f882c0ff4bf6bca211dc8598 rsync-2.6.3-i486-1.tgz
Slackware 10.0 package:
5967a4b24e96713f0fd5ba811acde89b rsync-2.6.3-i486-1.tgz
Slackware -current package:
e1089b13f2966ba6562ddf8b22369b3e rsync-2.6.3-i486-1.tgz
Installation Instructions
Installation instructions: If rsync is running as a server, shut it down first. Then, upgrade the packages as root: # upgradepkg rsync-2.6.3-i486-1.tgz Finally, restart the rsync server if needed.