Rdiff-backup

Latest version: v2.2.6

Safety actively analyzes 688600 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 19

1.1.3

Regression metadata bug introduced with 1.1.1/1.1.2 fixed.

rdiff-backup should now give a clean error message (no stack traces!) when aborted with control-C, killed with a signal, or when the connection is lost.

When removing older than, delete empty increments directories

Long filename bug finally fixed (phew).
rdiff-backup should now correctly mirror any file that it can read.

Due to very detailed error report from Yoav, fixed a "Directory not empty" error that can arise on emulated filesystems like NFS and EncFS.

Cleaned up remove older than report, and also stopped it from deleting current data files if you specify a time later than the current mirror.

1.1.2

This version corrects a packaging error in v1.1.1, which was totally broken.

1.1.1

rdiff-backup now writes SHA1 sums into its mirror_metadata file for all regular files, and checks them when restoring.

The above greatly increases the size of the mirror_metadata files, so diff them for space efficiency, as suggested by Dean Gaudet.

Added two new comparison modes: full file (using the --compare-full or --compare-full-at-time) or by hash (--compare-hash and --compare-hash-at-time).

Applied Alec Berryman's patch to update the no-compression regexp.

Alec Berryman's fs_abilities patch is supposed to help with AFS.

Fixed filename-too-long crash when quoting.

Patched carbonfile support, re-enabled it by default.

1.1.0

Refactored fs_abilities for more flexibility.
In particular, avoid quoting if both source and destination file systems are case-insensitive.

Increased buffer sizes by factor of 4, because everyone probably has 4 times as much RAM now as when I originally picked those values.

When possible, fsync using a writable file descriptor.
This may help with cygwin.
(Requested/tested by Dave Kempe.)

Support req 104755: Added --preserve-numerical-ids option, which makes rdiff-backup preserve uids/gids instead of unames/gnames.
(Suggested by Wiebe Cazemier)

Fix for bug 14799 reported by Bob McKay: Crash when backing up files with high permissions (like suid) to some FAT systems.

1.0.2

Fix for spurious security violation from --create-full-path (reported by Mike Bydalek).

Fix for bug 14545 which was introduced in version 1.0.1: Quoting caused a spurious security violation.
(Important for Mac OS X)

An error reading carbonfile data on Mac OS X should no longer cause a crash.
(Thanks to Kevin Horton for testing.)

Carbonfile support now defaults to off, even if the system appears to support it.
It can be manually enabled with the --carbonfile switch.
If you know something about Mac OS X and want to look at the carbonfile code so it can be re-enabled by default, please do so :) (help available from list)

1.0.1

Fix for "'filetype' of type exceptions.KeyError" error when restoring.
Test case provided by Davy Durham.
(The problem was the mirror_metadata file could become un-synced when a file is deleted when rdiff-backup is running and later the directory that file is in gets deleted.)

Librsync signature blocksize now based on square root of file length.

rdiff-backup now writes its PID to current_mirror marker (suggested by Kevin Spicer).

fsync_directories defaults to None, to avoid errors in testing (suggestion by Charles Duffy).

bug14209: Security bug with --restrict-read-only and --restrict-update-only allowed file statting and directory listing outside path.
Bug with --restrict option allowed writes outside path.
(Reported by Charles Duffy.)

bug 14304: Python 2.2 compatibility spoiled by device files.

lchown no longer required, which is good news for Mac OS X 10.3.

Page 9 of 19

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.