X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/b8b0668e85eb3b3350904068eb8d29d499d4e980..cb15269eb0cb5580169e63fada0c71f168879f4f:/NEWS diff --git a/NEWS b/NEWS index c9db11ad..f4777124 100644 --- a/NEWS +++ b/NEWS @@ -1,49 +1,55 @@ -NEWS for rsync 2.6.6 (UNRELEASED) +NEWS for rsync 2.6.9 (unreleased) Protocol: 29 (unchanged) -Changes since 2.6.5: +Changes since 2.6.8: BUG FIXES: - - The setting of flist->high in clean_flist() was wrong for an empty list. - This could cause flist_find() to crash in certain rare circumstances - (e.g. if just the right directory setup was around when --fuzzy was - combined with --list-dest). - - - The outputting of hard-linked files when verbosity was > 1 was not right: - without -i it would output the name of each hard-linked file as though - it had been changed (it now outputs a "is hard linked" message for the - file); with -i it would output all dots for the unchanged attributes of - a hard-link (it now changes those dots to spaces, as is done for other - totally unchanged items). - - - When backing up a changed symlink or device, get rid of any old backup - item so that we don't get an already-exists error. - - - A couple places that were comparing a local and a remote modification- - time were not honoring the --modify-window option. - - - Fixed a really old, minor bug that could cause rsync to warn about being - unable to mkdir() a path that ends in "/." because it just created the - directory (required --relative, --no-implied-dirs, a source path that - ended in either a trailing slash or a trailing "/.", and a non-existing - destination dir to tickle the bug in a recent version). + - 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). ENHANCEMENTS: - - Made the "max verbosity" setting in the rsyncd.conf file settable on a - per-module basis (which now matches the documentation). - - - The support/rrsync script has been upgraded to verify the args of options - that take them (instead of rejecting any such options). The script was - also changed to try to be more secure and to fix a problem in the parsing - of a pull operation that has multiple sources. + - ... - BUILD CHANGES: + DEVELOPER RELATED: - - Made configure define NOBODY_USER (currently hard-wired to "nobody") and - NOBODY_GROUP (set to either "nobody" or "nogroup" depending on what we - find in the /etc/group file). + - 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. - - Added a test to the test suite, itemized.test, that tests the output of - -i (log-format w/%i) and some double-verbose messages. + - 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.