summaryrefslogtreecommitdiff
path: root/rsyncd.conf.yo
diff options
context:
space:
mode:
authorWayne Davison <wayned@samba.org>2007-11-27 13:11:08 -0800
committerWayne Davison <wayned@samba.org>2007-11-27 13:11:49 -0800
commitef3f14e6a74a36a428f6d38aa77fc7fff2b6c576 (patch)
treeb36ea145a1a39e421f206b7619da12e96f623a84 /rsyncd.conf.yo
parent9585b27678ee8b94f2f260e8d8d61ff4381f2fa3 (diff)
downloadrsync-ef3f14e6a74a36a428f6d38aa77fc7fff2b6c576.tar.gz
rsync-ef3f14e6a74a36a428f6d38aa77fc7fff2b6c576.tar.bz2
rsync-ef3f14e6a74a36a428f6d38aa77fc7fff2b6c576.zip
When the new "munge symlinks" option is off, a non-chroot
daemon should sanitize its symlinks, as it used to do.
Diffstat (limited to 'rsyncd.conf.yo')
-rw-r--r--rsyncd.conf.yo6
1 files changed, 6 insertions, 0 deletions
diff --git a/rsyncd.conf.yo b/rsyncd.conf.yo
index 052ccc7e..b3eb4dd8 100644
--- a/rsyncd.conf.yo
+++ b/rsyncd.conf.yo
@@ -190,6 +190,12 @@ every symlink's value. There is a perl script in the support directory
of the source code named "munge-symlinks" that can be used to add or remove
this prefix from your symlinks.
+When this option is disabled on a writable module and "use chroot" is off,
+incoming symlinks will be modified to drop a leading slash and to remove ".."
+path elements that rsync believes will allow a symlink to escape the module's
+hierarchy. There are tricky ways to work around this, though, so you had
+better trust your users if you choose this combination of options.
+
dit(bf(max connections)) The "max connections" option allows you to
specify the maximum number of simultaneous connections you will allow.
Any clients connecting when the maximum has been reached will receive a