| 1 | NEWS for rsync 2.6.9 (unreleased) |
| 2 | Protocol: 29 (unchanged) |
| 3 | Changes since 2.6.8: |
| 4 | |
| 5 | BUG FIXES: |
| 6 | |
| 7 | - If rsync is interrupted via a handled signal (such as SIGINT), it will |
| 8 | once again clean-up its temp file from the destination dir. |
| 9 | |
| 10 | - An rsync daemon that is receiving files with "use chroot = no" no longer |
| 11 | sanitizes the symlink target strings. This means that each symlink's |
| 12 | value will now be accepted (and thus returned) with its symlink info |
| 13 | intact. Also, in order to keep things safe, all arg paths and any |
| 14 | dereferenced symlinks (e.g. via --copy-links or --keep-dirlinks) are |
| 15 | manually verified to ensure that no symlinks try to escape past the top |
| 16 | of the module's path. These changes make a non-chroot daemon behave the |
| 17 | same way as a chroot daemon with regard to symlinks, and also avoids a |
| 18 | potential problem where a pre-existing symlink could have escaped the |
| 19 | module's hierarchy. |
| 20 | |
| 21 | - Fixed an overzealous sanitizing bug in the handling of the --link-dest, |
| 22 | --copy-dest, and --compare-dest options to a daemon without chroot: if |
| 23 | the copy's destination dir is deeper than the top of the module's path, |
| 24 | these options now accept a safe number of ../ (parent-dir) references |
| 25 | (since these options are relative to the destination dir). The old code |
| 26 | incorrectly chopped off all "../" prefixes for these options, no matter |
| 27 | how deep the destination directory was in the module's hierarchy. |
| 28 | |
| 29 | - Fixed a bug where a deferred info/error/log message could get sent |
| 30 | directly to the sender instead of being handled by rwrite() in the |
| 31 | generator. This fixes an "unexpected tag 3" fatal error, and should |
| 32 | also fix a potential problem where a deferred info/error message from |
| 33 | the receiver might bypass the log file and get sent only to the client |
| 34 | process. (These problems could only affect an rsync daemon that was |
| 35 | receiving files.) |
| 36 | |
| 37 | - Make sure that the --link-dest option can still do its job even when -I |
| 38 | is specified. |
| 39 | |
| 40 | - If --link-dest is specified with --checksum but without --times, rsync |
| 41 | will now allow a hard-link to be created to a matching link-dest file |
| 42 | even when the file's modify-time doesn't match the server's file. |
| 43 | |
| 44 | - The daemon now calls more timezone-using functions prior to doing a |
| 45 | chroot. This should help some C libraries to generate proper timestamps |
| 46 | from inside a chrooted daemon (and to not try to access /etc/timezone |
| 47 | over and over again). |
| 48 | |
| 49 | - Fixed a bug in the handling of an absolute --partial-dir=ABS_PATH option: |
| 50 | it now deletes an alternate basis file from the partial-dir that was used |
| 51 | to successfully update a destination file. |
| 52 | |
| 53 | ENHANCEMENTS: |
| 54 | |
| 55 | - Added the --log-file=FILE and --log-file-format=FORMAT options. These |
| 56 | can be used to tell any rsync to output what it is doing to a log file. |
| 57 | They work with a client rsync, a non-daemon server rsync (see the man |
| 58 | page for instructions), and also allows the overriding of rsyncd.conf |
| 59 | settings when starting a daemon. |
| 60 | |
| 61 | - The --log-format option was renamed to be --out-format to avoid confusing |
| 62 | it with affecting the log-file output. (The old option remains as an |
| 63 | alias for the new to preserve backward compatibility.) |
| 64 | |
| 65 | DEVELOPER RELATED: |
| 66 | |
| 67 | - The acls.diff and xattrs.diff patches have received a bunch of work to |
| 68 | make them much closer to being acceptable in the main distribution. |
| 69 | |
| 70 | - Updated config.guess and config.sub to their 2006-02-23 version. |
| 71 | |
| 72 | - Updated various files to include the latest FSF address and to have |
| 73 | consistent opening comments. |