- * Fixed several exclude/include matching bugs when using wild-cards.
- This has a several user-visible effects, all of which make the
- matching more consistent and intuitive. This should hopefully not
- cause anyone problems since it makes the matching work more like
- what people are expecting. (Wayne Davison)
-
- - A pattern with a "**" no longer causes a "*" to match slashes.
- For example, with "/*/foo/**", "foo" must be 2 levels deep.
- [If your string has BOTH "*" and "**" wildcards, changing the
- "*" wildcards to "**" will provide the old behavior in all
- versions.]
-
- - "**/foo" now matches at the base of the transfer (like /foo
- does). [Use "/**/foo" to get the old behavior in all versions.]
-
- - A non-anchored wildcard term floats to match beyond the base of
- the transfer. E.g. "CVS/R*" matches at the end of the path,
- just like the non-wildcard term "CVS/Root" does. [Use "/CVS/R*"
- to get the old behavior in all versions.]
-
- - Including a "**" in the match term causes it to be matched
- against the entire path, not just the name portion, even if
- there aren't any interior slashes in the term. E.g. "foo**bar"
- would exclude "/path/foo-bar" (just like before) as well as
- "/foo-path/baz-bar" (unlike before). [Use "foo*bar" to get the
- old behavior in all versions.]
-
- * The exclude list specified in the daemon's config file is now
- properly applied to the pulled items no matter how deep the
- user's file-args are in the source tree. (Wayne Davison)
-
- * For protocol version >= 27, mdfour_tail() is called when the
- block size (including checksum_seed) is a multiple of 64.
- Previously it was not called, giving the wrong MD4 checksum.
- (Craig Barratt)
-
- * For protocol version >= 27, a 64 bit bit counter is used in
- mdfour.c as required by the RFC. Previously only a 32 bit bit
- counter was used, causing incorrect MD4 file checksums for
- file sizes >= 512MB - 4. (Craig Barratt)
+ - 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
+ 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
+ incorrectly chopped off all "../" prefixes for these options, no matter
+ 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
+ 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. 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).