X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/b06050f9ad6657a41b5ca5f7e205e48ed6edb173..99eba67585c79180be72ea10889ae7eec61f9034:/NEWS diff --git a/NEWS b/NEWS index bfc2d836..50e12ac1 100644 --- a/NEWS +++ b/NEWS @@ -7,21 +7,10 @@ Changes since 2.6.8: - If rsync is interrupted via a handled signal (such as SIGINT), it will once again clean-up its temp file from the destination dir. - - An rsync daemon that is receiving files with "use chroot = no" no longer - sanitizes the symlink target strings (by default). 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, 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. See also the new "munge symlinks" daemon setting. - - 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 + 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 module's hierarchy. @@ -34,6 +23,10 @@ Changes since 2.6.8: process. (These problems could only affect an rsync daemon that was receiving files.) + - Fixed a bug where using --dry-run with a --*-dest option with a path + relative to a directory that does not yet exist: the affected option + gets its proper path value so that the output of the dry-run is right. + - Fixed a bug in the %f logfile escape when receiving files: the destination path is now included in the output (e.g. you can now tell when a user specifies a subdir inside a module). @@ -73,7 +66,7 @@ Changes since 2.6.8: - If either --remove-source-files or --remove-sent-files is enabled and we are unable to remove the source file, rsync now outputs an error. - - Fixed a bug in the daemon's "incoming chmod" rule: newly-created + - Fixed a bug in the daemon's "incoming chmod" rule: newly-created directories no longer get the 'F' (file) rules applied to them. ENHANCEMENTS: @@ -91,10 +84,6 @@ Changes since 2.6.8: - Made "log file" and "syslog facility" settable on a per-module basis in the daemon's config file. - - Added the "munge symlinks" daemon setting to enable the old-style - tweaking of "unsafe" symlinks, but it can now be consistently applied - regardless of how "use chroot" is set. - - Added the --remove-source-files option as a replacement for the (now deprecated) --remove-sent-files option. This new option removes all non-dirs from the source directories, even if the file was already