+NEWS for rsync 2.6.3 (UNRELEASED)
+Protocol: 28 (unchanged)
+Changes since 2.6.2:
+
+ SECURITY FIXES:
+
+ - A bug in the sanitize_path routine (which affects a non-chrooted
+ rsync daemon) could allow a user to craft a pathname that would get
+ transformed into an absolute path for certain options (but not for
+ file-transfer names). If you're running an rsync daemon with chroot
+ disabled, *please upgrade*, ESPECIALLY if the user privs you run
+ rsync under is anything above "nobody".
+
+ OUTPUT CHANGES (ATTN: those using a script to parse the verbose output):
+
+ - Please note that the 2-line footer (output when verbose) now uses the
+ term "sent" instead of "wrote" and "received" instead of "read". If
+ you are not parsing the numeric values out of this footer, a script
+ would be better off using the empty line prior to the footer as the
+ indicator that the verbose output is over.
+
+ - The output from the --stats option was similarly affected to change
+ "written" to "sent" and "read" to "received".
+
+ - Rsync ensures that a filename that contains a newline gets mentioned
+ with each newline transformed into a question mark (which prevents a
+ filename from causing an empty line to be output).
+
+ BUG FIXES:
+
+ - 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 or the reconstructed
+ data doesn't match the expected checksum (perhaps due to the basis
+ file changing during the transfer), the receiver will no longer
+ retain the resulting file unless the --partial option was specified.
+ (Note: for the read-error detection to work, neither side can be
+ older than 2.6.3 -- older receivers will always retain the file, and
+ older senders don't tell the receiver that the file had a read
+ error.)
+
+ - If a file gets resent in a single transfer and the --backup option
+ is enabled, rsync no longer performs a duplicate backup (it used to
+ overwrite the original file in the backup area).
+
+ - 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".
+
+ - The --copy-links (-L) option no longer has the side-effect of telling
+ the receiving side to follow symlinks. See the --keep-dirlinks
+ option (mentioned below) for a way to specify that behavior.
+
+ - 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).
+
+ - When the remote rsync dies, make a better effort to recover any error
+ messages it may have sent before dying (the local rsync used to just
+ die with a socket-write error).
+
+ - When using --delete and a --backup-dir that contains files that are
+ hard-linked to their destination equivalents, rsync now makes sure
+ that removed files really get removed (works around a really weird
+ rename() behavior).
+
+ - Avoid a bogus run-time complaint about a lack of 64-bit integers when
+ the int64 type is defined as an off_t and it actually has 64-bits.
+
+ - Added a configure check for open64() without mkstemp64() so that we
+ can avoid using mkstemp() when such a combination is encountered.
+ This bypasses a problem writing out large temp files on OSes such as
+ AIX and HP-UX.
+
+ - Fixed an age-old crash problem with --read-batch on a local copy
+ (rsync was improperly assuming --whole-file for the local copy).
+
+ - When --dry-run (-n) is used and the destination directory does not
+ exist, rsync now produces a correct report of files that would be
+ sent instead of dying with a chdir() error.