X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/2220ec0a69cc9bb9c2d4f022fb5fec26fd9846e6..d1f66d8d796965d90552db75d63bdbbf0b98c3f9:/NEWS diff --git a/NEWS b/NEWS index c261dc70..9712609e 100644 --- a/NEWS +++ b/NEWS @@ -1,53 +1,54 @@ -NEWS for rsync 2.6.9 (unreleased) -Protocol: 29 (unchanged) -Changes since 2.6.8: +NEWS for rsync 3.0.3 (UNRELEASED) +Protocol: 30 (unchanged) +Changes since 3.0.2: BUG FIXES: - - 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 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. + - Fixed a wildcard matching problem in the daemon when a module has + "use chroot" enabled. + + - Fixed a crash bug in the hard-link code. + + - Fixed the combination of --xattrs and --backup. + + - The generator no longer allows a '.' dir to be excluded by a daemon- + exclude rule. + + - Fixed the conversion of spaces into dashes in the %M log escape. + + - Fixed several places in the code that were not returning the right + errno when a function failed. + + - Fixed the backing up of a device or special file into a backup dir. + + - Moved the setting of the socket options prior to the connect(). + + - If rsync exits in the middle of a --progress output, it now outputs a + newline to prevent the progress line from being overwritten. + + - Fixed a problem with how a destination path with a trailing slash was + compared against the daemon excludes. + + - If a file's length is so huge that we overflow a checksum buffer count + (i.e. several hundred TB), warn the user and avoid sending an invalid + checksum struct over the wire. + + - If an source arg is excluded, --relative no longer adds the excluded + arg's implied dirs to the transfer. + + - Use the overflow_exit() function for overflows, not out_of_memory(). ENHANCEMENTS: - - ... + - The rsyncd.conf manpage now consistently refers to the parameters in + the daemon config file as "parameters". - DEVELOPER RELATED: + - The description of the --inplace option was improved. - - 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. + DEVELOPER RELATED: - - Updated config.guess and config.sub to their 2006-02-23 version. + - Fixed a testcase failure if the tests are run as root and made some + compatibility improvements. - - Updated various files to include the latest FSF address and to have - consistent opening comments. + - Ensure that the early patches don't cause any generated-file hunks to + bleed-over into patches that follow.