Mention the recent changes.
[rsync/rsync.git] / NEWS
CommitLineData
8fe27e76 1NEWS for rsync 2.6.6 (UNRELEASED)
3ae6c187 2Protocol: 29 (unchanged)
8fe27e76 3Changes since 2.6.5:
060f3150 4
9db17434
WD
5 SECURITY FIXES:
6
870dddc5
WD
7 - The zlib code was upgraded to version 1.2.3 in order to make it more
8 secure. While the widely-publicized security problem in zlib 1.2.2 did
9 not affect rsync, another security problem surfaced that affects rsync's
10 zlib 1.1.4.
9db17434 11
ac1541f4
WD
12 BUG FIXES:
13
30e7b0b2
WD
14 - The setting of flist->high in clean_flist() was wrong for an empty list.
15 This could cause flist_find() to crash in certain rare circumstances
16 (e.g. if just the right directory setup was around when --fuzzy was
f3ee7268 17 combined with --link-dest).
30e7b0b2 18
8fe27e76 19 - The outputting of hard-linked files when verbosity was > 1 was not right:
e8432be9 20 without -i it would output the name of each hard-linked file as though
8fe27e76 21 it had been changed (it now outputs a "is hard linked" message for the
301569f0
WD
22 file); with -i it would output all dots for the unchanged attributes of
23 a hard-link (it now changes those dots to spaces, as is done for other
24 totally unchanged items).
bac72590 25
20667b6d 26 - When backing up a changed symlink or device, get rid of any old backup
9db17434 27 item so that we don't get an "already exists" error.
20667b6d 28
e8432be9
WD
29 - A couple places that were comparing a local and a remote modification-
30 time were not honoring the --modify-window option.
31
b8b0668e
WD
32 - Fixed a really old, minor bug that could cause rsync to warn about being
33 unable to mkdir() a path that ends in "/." because it just created the
34 directory (required --relative, --no-implied-dirs, a source path that
35 ended in either a trailing slash or a trailing "/.", and a non-existing
36 destination dir to tickle the bug in a recent version).
37
9425918d
WD
38 - If the user specifies a remote-host for both the source and destination,
39 we now output a syntax error rather than trying to open the destination
40 hostspec as a filename.
41
870dddc5
WD
42 - Rsync now outputs a targeted error if both the source and destination
43 path appear to be a remote filespecs rather than treating the dest as
44 a very strange local path and (most likely) generating an error about
45 non-existent directories.
46
ac1541f4
WD
47 ENHANCEMENTS:
48
870dddc5
WD
49 - Added the --append option that makes rsync append data onto files
50 that are longer on the source than the destination (this includes new
51 files).
52
53 - The configure script now checks for lutimes() and lchmod() so that
54 rsync can make use of them to update attributes of symlinks (on
55 systems that support this).
56
8fe27e76
WD
57 - Made the "max verbosity" setting in the rsyncd.conf file settable on a
58 per-module basis (which now matches the documentation).
7d7a34ae 59
870dddc5
WD
60 - Added two config items to the rsyncd.conf parsing: "pre-xfer exec"
61 and "post-xfer exec". These allow a command to be specified on a
62 per-module basis that will be run before and/or after a daemon-mode
63 transfer.
64
3f6c17cf 65 - The support/rrsync script has been upgraded to verify the args of options
870dddc5 66 that take args (instead of rejecting any such options). The script was
3f6c17cf 67 also changed to try to be more secure and to fix a problem in the parsing
301569f0 68 of a pull operation that has multiple sources.
3f6c17cf 69
870dddc5
WD
70 - Improved the documentation that explains the difference between a
71 normal daemon transfer and a daemon-over remote-shell transfer.
72
73 - Some of the diffs supplied in the patches dir were fixed and/or
74 improved.
9db17434 75
ac1541f4
WD
76 BUILD CHANGES:
77
8fe27e76
WD
78 - Made configure define NOBODY_USER (currently hard-wired to "nobody") and
79 NOBODY_GROUP (set to either "nobody" or "nogroup" depending on what we
80 find in the /etc/group file).
7d7a34ae 81
8fe27e76
WD
82 - Added a test to the test suite, itemized.test, that tests the output of
83 -i (log-format w/%i) and some double-verbose messages.
20667b6d 84