- An rsync daemon that is receiving files with "use chroot = no" no longer
sanitizes the symlink target strings. This means that each symlink's
value will now be accepted (and thus returned) with its symlink info
- intact. Also, in order to keep things safe, any option that tells a
- non-chroot daemon to treat some symlinks as their referent (such as
- --copy-links or --keep-dirlinks) now manually checks the symlink chain
- to ensure that the symlinks do not try to escape past the top of the
- module's path. Both these changes make a non-chroot daemon behave the
- same as a chroot daemon with regard to symlinks, and also avoids a
+ intact. Also, in order to keep things safe, all arg paths and any
+ dereferenced symlinks (e.g. via --copy-links or --keep-dirlinks) are
+ manually verified to ensure that no symlinks try to escape past the top
+ of the module's path. These changes make a non-chroot daemon behave the
+ same way as a chroot daemon with regard to symlinks, and also avoids a
potential problem where a pre-existing symlink could have escaped the
module's hierarchy.
- - Fixed a overzealous sanitizing bug in the handling of the --*-dest
- options (--link-dest, --copy-dest, and --compare-dest): if the copy's
- destination dir is deeper than the top of the module's path, these
- options now accept a safe number of ../ (parent-dir) references (since
- these options are relative to the destination dir). The old code
+ - Fixed an overzealous sanitizing bug in the handling of the --link-dest,
+ --copy-dest, and --compare-dest options to a daemon without chroot: if
+ the copy's destination dir is deeper than the top of the module's path,
+ these options now accept a safe number of ../ (parent-dir) references
+ (since these options are relative to the destination dir). The old code
incorrectly chopped off all "../" prefixes for these options, no matter
- how deep the destination directory was in the hierarchy.
+ how deep the destination directory was in the module's hierarchy.
- Fixed a bug where a deferred info/error/log message could get sent
directly to the sender instead of being handled by rwrite() in the
receiving files.)
- Make sure that the --link-dest option can still do its job even when -I
- or --size-only is specified.
+ is specified.
+
+ - If --link-dest is specified with --checksum but without --times, rsync
+ will now allow a hard-link to be created to a matching link-dest file
+ regardless of the file's modify-time.
- The daemon now calls more timezone-using functions prior to doing a
- chroot.
+ chroot. This should help some C libraries to generate proper timestamps
+ from inside a chrooted daemon (and to not try to access /etc/timezone
+ over and over again).
+
+ - Fixed a bug in the handling of an absolute --partial-dir=ABS_PATH option:
+ it now deletes an alternate basis file from the partial-dir that was used
+ to successfully update a destination file.
ENHANCEMENTS:
- - ...
+ - Added the --log-file=FILE and --log-file-format=FORMAT options. These
+ can be used to tell any rsync to output what it is doing to a log file.
+ They work with a client rsync, a non-daemon server rsync (see the man
+ page for instructions), and also allows the overriding of rsyncd.conf
+ settings when starting a daemon.
+
+ - The --log-format option was renamed to be --out-format to avoid confusing
+ it with affecting the log-file output. (The old option remains as an
+ alias for the new to preserve backward compatibility.)
DEVELOPER RELATED:
Matt McCutchen's Web Site / rsync / rsync.git / blobdiff