Advisories
Mandriva Advisories
|
 |
| Problem Description |
Ethan Benson discovered a bug in rsync where the supplementary groups
that the rsync daemon runs as (such as root) would not be removed
from the server process after changing to the specified unprivileged
uid and gid. This seems only serious if rsync is called using "rsync
--daemon" from the command line where it will inherit the group of the
user starting the server (usually root). Note that, by default,
Mandrake Linux uses xinetd to handle connections to the rsync daemon.
This was fixed upstream in version 2.5.3, as well as the previously
noted zlib fixes (see MDKSA-2002:023). The authors released 2.5.4 with
some additional zlib fixes, and all users are encouraged to upgrade to
this new version of rsync.
| Updated Packages |
Mandrakelinux 7.1
fdfd74524914606306ab5717b696e030 7.1/RPMS/rsync-2.5.4-1.2mdk.i586.rpm 34a71b565a7413ecb4efe48acb4df65f 7.1/SRPMS/rsync-2.5.4-1.2mdk.src.rpm
Mandrakelinux 7.2
7eda7d7a7df5bf088a64990bf5c4d70d 7.2/RPMS/rsync-2.5.4-1.1mdk.i586.rpm f425baa9b832265d6a199bd4409a28db 7.2/SRPMS/rsync-2.5.4-1.1mdk.src.rpm
Mandrakelinux 8.0
914f020aa62c9ce6fdd61dfce245fc1c 8.0/RPMS/rsync-2.5.4-1.1mdk.i586.rpm f425baa9b832265d6a199bd4409a28db 8.0/SRPMS/rsync-2.5.4-1.1mdk.src.rpm
Mandrakelinux 8.0/PPC
c9c5275126721f7aa38f6a4e09742ce9 ppc/8.0/RPMS/rsync-2.5.4-1.1mdk.ppc.rpm f425baa9b832265d6a199bd4409a28db ppc/8.0/SRPMS/rsync-2.5.4-1.1mdk.src.rpm
Mandrakelinux 8.1
e3733dc91021b997e656fafe86915fe9 8.1/RPMS/rsync-2.5.4-1.1mdk.i586.rpm f425baa9b832265d6a199bd4409a28db 8.1/SRPMS/rsync-2.5.4-1.1mdk.src.rpm
Corporate Server 1.0.1
fdfd74524914606306ab5717b696e030 1.0.1/RPMS/rsync-2.5.4-1.2mdk.i586.rpm 34a71b565a7413ecb4efe48acb4df65f 1.0.1/SRPMS/rsync-2.5.4-1.2mdk.src.rpm
| References |
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=132272
| Upgrade |
To upgrade automatically, use MandrivaUpdate.
| Verification |
Please verify the update prior to upgrading to ensure the integrity of the downloaded package. You can do this with the command :
rpm --checksig package.rpm
You can get the GPG public key of the Mandriva Security Team to verify the GPG signature of each RPM.
If you use MandrivaUpdate, the verification of md5 checksum and GPG signature is performed automatically for you.