- - Fixed a crash bug that might appear when --delete was used and
- multiple source directories were specified.
-
- - Fixed the 32-bit truncation of the file length when generating the
- checksums.
-
- - The --backup code no longer attempts to create some directories
- over and over again (generating warnings along the way).
-
- - Fixed a bug in the reading of the secrets file (by the daemon) and
- the password file (by the client): the files no longer need to be
- terminated by a newline for their content to be read in.
-
- - If a file has a read error on the sending side, the receiver will
- no longer keep the resulting file unless the --partial option was
- specified. (Note: both sides must be running 2.6.3 for this to
- work -- older receivers always keep the file, and older senders
- don't tell the receiver that the file was not read correctly.)
-
- - If a file gets resent in a single transfer and the --backup option
- is enabled, rsync no longer performs a duplicate backup (losing the
- original file in the process).
-
- - Fixed an age-old crash problem with --read-batch on a local copy
- (rsync was improperly assuming --whole-file for the local copy).
-
- - Files specified in the daemon's "exclude" or "exclude from" config
- items are now excluded from being uploaded (assuming that the module
- allows uploading at all) in addition to the old download exclusion.
-
- - Got rid of a potential hang in the receiver when near the end of a
- phase.
-
- - When using --backup without a --backup-dir, rsync no longer preserves
- the modify time on directories. This avoids confusing NFS.
-
- - When --copy-links (-L) is specified, we now output a separate error
- for a symlink that has no referent instead of claiming that a file
- "vanished".
-
- - Error messages from the daemon server's option-parsing (such as
- refused options) now get sent back to the client (the server used
- to just exit because the socket wasn't in the right state to send
- the message).
-
- - Most errors that occur during a daemon transfer are now returned to
- the user in addition to being logged (some messages are intended to
- be daemon-only).
-
- - Fixed a bug in the daemon authentication code when using one of the
- batch-processing options.
-
- - We try to work around some buggy IPv6 implementations that fail to
- implement IPV6_V6ONLY. This should fix the "address in use" error
- that some daemons get when running on an OS with a buggy IPv6
- implementation. Also, if the new code gets this error, we might
- suggest that the user specify --ipv4 or --ipv6 (if we think it will
- help).
+ - 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. 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
+ (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.)
+
+ - 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).
+
+ - If the receiving side fails to create a directory, it will now skip
+ trying to update everything that is inside that directory.
+
+ - Make sure that the --link-dest option can still do its job even when -I
+ 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
+ even when the file's modify-time doesn't match the server's file.
+
+ - 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).
+
+ - 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.