mirror/rsync
1
0
Fork 0
mirror of https://github.com/RsyncProject/rsync.git synced 2026-03-23 00:31:10 -04:00
Code Issues Packages Projects Releases Wiki Activity

Improved the "use chroot" discussion on ID mapping.

Browse Source
This commit is contained in:
Wayne Davison
2004-01-23 16:55:40 +00:00
parent a2b0471f1d
commit cb290916be
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
rsyncd.conf.yo
View File

@@ -136,13 +136,19 @@ the advantage of extra protection against possible implementation security
holes, but it has the disadvantages of requiring super-user privileges,
of not being able to follow symbolic links outside of the new root path
when reading, and of complicating the preservation of usernames and groups
(you'll need to supply in-chroot versions of etc/passwd and etc/group if
you want named-based user/group mapping to be performed).
When "use chroot" is false, for security reasons,
(see below). When "use chroot" is false, for security reasons,
symlinks may only be relative paths pointing to other files within the root
path, and leading slashes are removed from absolute paths. The default for
"use chroot" is true.
In order to preserve usernames and groupnames, rsync needs to be able to
lookup the IDs using getpuid() and getpgid(). This means that the chroot
area will need to have copies of your user/group information (edited, if
desired) inside the chroot tree for rsync to use (the traditional files
are /etc/passwd and /etc/group). If the needed files are not available,
rsync will only be able to copy the IDs, just as if the --numeric-ids
option had been specified.
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