Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
liblongpath-rsync
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
liblongpath
liblongpath-rsync
Commits
e8087670
Commit
e8087670
authored
Oct 12, 2006
by
Wayne Davison
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Got rid of changes that aren't going to make it into 2.6.9.
parent
ec55b4f2
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
0 additions
and
15 deletions
+0
-15
NEWS
NEWS
+0
-15
No files found.
NEWS
View file @
e8087670
...
...
@@ -7,17 +7,6 @@ Changes since 2.6.8:
- If rsync is interrupted via a handled signal (such as SIGINT), it will
once again clean-up its temp file from the destination dir.
- An rsync daemon that is receiving files with "use chroot = no" no longer
sanitizes the symlink target strings (by default). 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, all arg paths and any
dereferenced symlinks (e.g. via --copy-links or --keep-dirlinks) are
manually verified to ensure that no symlinks try to escape past the top
of the module's path. These changes make a non-chroot daemon behave the
same way 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. See also the new "munge symlinks" daemon setting.
- Fixed an overzealous sanitizing bug in the handling of the --link-dest,
--copy-dest, and --compare-dest options to a daemon without chroot: if
the copy's destination dir is deeper than the top of the module's path,
...
...
@@ -95,10 +84,6 @@ Changes since 2.6.8:
- Made "log file" and "syslog facility" settable on a per-module basis in
the daemon's config file.
- Added the "munge symlinks" daemon setting to enable the old-style
tweaking of "unsafe" symlinks, but it can now be consistently applied
regardless of how "use chroot" is set.
- Added the --remove-source-files option as a replacement for the (now
deprecated) --remove-sent-files option. This new option removes all
non-dirs from the source directories, even if the file was already
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment