Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Sign up!
EnGarde Community
What is the most important Linux security technology?
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Latest Newsletters
Linux Advisory Watch: March 27th, 2015
Linux Security Week: March 23rd, 2015
LinuxSecurity Newsletters
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

Slackware: rsync security update Print E-mail
User Rating:      How can I rate this item?
Posted by Team   
Slackware New rsync 2.6.3 packages are available for Slackware 8.1, 9.0, 9.1, 10.0, and -current to a fix security issue when rsync is run as a non-chrooted server.

[slackware-security]  rsync (SSA:2004-285-01)

New rsync 2.6.3 packages are available for Slackware 8.1, 9.0, 9.1,
10.0, and -current to a fix security issue when rsync is run as
a non-chrooted server.

More details about this issue may be found in the Common
Vulnerabilities and Exposures (CVE) database:

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 to find the 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:

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.


Slackware Linux Security Team

| To leave the slackware-security mailing list:                          |
| Send an email to with this text in the body of |
| the email message:                                                     |
|                                                                        |
|   unsubscribe slackware-security                                       |
|                                                                        |
| You will get a confirmation message back containing instructions to    |
| complete the process.  Please do not reply to this email address.      |

< Prev   Next >


Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
FBI Quietly Removes Recommendation To Encrypt Your Phone
And the prize for LEAST SECURE BROWSER goes to ... Chrome!
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2015 Guardian Digital, Inc. All rights reserved.