-NEWS for rsync 2.6.9 (unreleased)
-Protocol: 29 (unchanged)
-Changes since 2.6.8:
+NEWS for rsync 3.0.6 (UNRELEASED)
+Protocol: 30 (unchanged)
+Changes since 3.0.5:
BUG FIXES:
- - An rsync daemon that is receiving files with "use chroot = no" no longer
- sanitizes the symlink target strings. This means that the symlinks
- values will now be accepted (and returned) with all their 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. This makes a non-chroot daemon behave the same as a
- chroot daemon with regard to symlinks, and also avoids a potential
- problem where pre-existing symlinks 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
- incorrectly chopped off all "../" prefixes for these options, no matter
- how deep the destination directory was in the 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
- generator. This fixes an "unexpected tag 3" fatal error, and should
- also fix a potential problem where a deferred info/error message from
- the receiver might bypass the log file and get sent only to the client
- process. (These problems could only affect an rsync daemon that was
- receiving files.)
-
- - Make sure that the --link-dest option can still do its job even when -I
- or --size-only is specified.
-
- - The daemon now calls more timezone-using functions prior to doing a
- chroot.
-
- ENHANCEMENTS:
-
- - ...
-
- DEVELOPER RELATED:
-
- - The acls.diff and xattrs.diff patches have received a bunch of work to
- make them much closer to being acceptable in the main distribution.
-
- - Updated config.guess and config.sub to their 2006-02-23 version.
-
- - Updated various files to include the latest FSF address and to have
- consistent opening comments.
+ - Fixed a hang in the batch-reading code with incremental recursion.
+
+ - Fixed the daemon's socket code to handle the simultaneous arrival of
+ multiple connections.
+
+ - Fix --safe-links/--copy-unsafe-links to properly handle symlinks that
+ have consecutive slashes in the value.
+
+ - Fixed the parsing of an [IPv6_LITERAL_ADDR] when a USER@ is prefixed.
+
+ - The sender now skips a (bogus) symlink that has a 0-length value, which
+ avoids a transfer error in the receiver.
+
+ - Fixed a case where the sender could die with a tag-0 error if there was
+ an I/O during the sending of the file list.
+
+ - Fixed the rrsync script to avoid a server-side problem when -e is at the
+ start of the short options.
+
+ - Fixed a problem where a vanished directory could turn into an exit code
+ 23 instead of the proper exit code 24.
+
+ - Fixed the --iconv conversion of symlinks when doing a local copy.
+
+ - Fixed a problem where --one-file-system was not stopping deletions on the
+ receiving side when a mount-point directory did not match a directory in
+ the transfer.
+
+ - Fixed the dropping of an ACL mask when no named ACL values were present.
+
+ - Fixed an ACL/xattr corruption issue where the --backup option could cause
+ rsync to associate the wrong ACL/xattr information with received files.
+
+ - Fixed the use of --xattrs with --only-write-batch.
+
+ - Fixed the use of --dry-run with --read-batch.
+
+ - Fixed configure's erroneous use of target.
+
+ - Fixed configure's --disable-debug option.
+
+ - Fixed a run-time issue for systems that can't find iconv_open() by adding
+ the --disable-iconv-open configure option.