Login-Name Passwort


Sicherheit: Hash-Kollision in rdiff-backup
Aktuelle Meldungen Distributionen
Name: Hash-Kollision in rdiff-backup
ID: FEDORA-2015-3366
Distribution: Fedora
Plattformen: Fedora 20
Datum: Fr, 20. März 2015, 00:03
Referenzen: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-8242


Name        : rdiff-backup
Product : Fedora 20
Version : 1.2.8
Release : 14.fc20
URL : http://www.nongnu.org/rdiff-backup/
Summary : Convenient and transparent local/remote incremental mirror/backup
Description :
rdiff-backup is a script, written in Python, that backs up one
directory to another and is intended to be run periodically (nightly
from cron for instance). The target directory ends up a copy of the
source directory, but extra reverse diffs are stored in the target
directory, so you can still recover files lost some time ago. The idea
is to combine the best features of a mirror and an incremental
backup. rdiff-backup can also operate in a bandwidth efficient manner
over a pipe, like rsync. Thus you can use rdiff-backup and ssh to
securely back a hard drive up to a remote location, and only the
differences from the previous backup will be transmitted.

Update Information:

Changes in librsync 1.0.0 (2015-01-23)

* SECURITY: CVE-2014-8242: librsync previously used a truncated MD4 "strong" check sum to match blocks. However, MD4 is not cryptographically strong. It's possible that an attacker who can control the contents of one part of a file could use it to control other regions of the file, if it's transferred using librsync/rdiff. For example this might occur in a database, mailbox, or VM image containing some attacker-controlled data. To mitigate this issue, signatures will by default be computed with a 256-bit BLAKE2 hash. Old versions of librsync will complain about a bad magic number when given these signature files. Backward compatibility can be obtained using the new `rdiff sig --hash=md4` option or through specifying the "signature magic" in the API, but this should not be used when either the old or new file contain untrusted data. Deltas generated from those signatures will also use BLAKE2 during generation, but produce output that can be read by old versions. See https://github.com/librsync/librsync/issues/5. Thanks to Michael Samuel <miknet.net> for reporting this and offering an initial patch.
* Various build fixes, thanks Timothy Gu.
* Improved rdiff man page from Debian.
* Improved librsync.spec file for building RPMs.
* Fixed bug #1110812 'internal error: job made no progress'; on large
* Moved hosting to https://github.com/librsync/librsync/
* Travis-CI.org integration test at https://travis-ci.org/librsync/librsync/
* Remove bundled copy of popt; it must be installed separately.
* You can set `$LIBTOOLIZE` before running `autogen.sh`, for example on OS X
Homebrew where it is called `glibtoolize`.

* Sun Mar 1 2015 Robert Scheck <robert@fedoraproject.org> - 1.2.8-14
- Rebuild for librsync 1.0.0 (#1126712)
* Sun Aug 17 2014 Fedora Release Engineering
<rel-eng@lists.fedoraproject.org> - 1.2.8-13
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_22_Mass_Rebuild
* Sun Jun 8 2014 Fedora Release Engineering
<rel-eng@lists.fedoraproject.org> - 1.2.8-12
- Rebuilt for https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild

[ 1 ] Bug #1126712 - CVE-2014-8242 librsync: MD4 collision file corruption

This update can be installed with the "yum" update program. Use
su -c 'yum update rdiff-backup' at the command line.
For more information, refer to "Managing Software with yum",
available at http://docs.fedoraproject.org/yum/.

All packages are signed with the Fedora Project GPG key. More details on the
GPG keys used by the Fedora Project can be found at
package-announce mailing list
Traut euch!
Neue Nachrichten