similar to: Rsync-daemon security advisories for writable daemons

It was recently brought to my attention that a writable rsync daemon that has "use chroot" enabled could potentially be tricked into loading a user-supplied library file if the library can be uploaded into a spot where a normal rsync action (such as an attempt to lookup a username from an ID) would cause the loader to load it in. If you haven't already taken steps to exclude library

It was recently brought to my attention that a writable rsync daemon that has "use chroot" enabled could potentially be tricked into loading a user-supplied library file if the library can be uploaded into a spot where a normal rsync action (such as an attempt to lookup a username from an ID) would cause the loader to load it in. If you haven't already taken steps to exclude library

Hello, i have found, that major distros (especially opensuse) ship their rsync packages with a lot of patches which i don`t find in the official rsync-patches git. Maybe there is a reason for that or i missed something or looked wrong, but for convenience/transparency i have compiled a list of those and ask if it would make sense to put them into the official rsync patches git, as most of them

Hello, I'm trying to push some data from one machine to another via rsync source machine uses rsync 3.0.8, it's a CentOS 5.6 Linux with rsync 3.0.8 package from rpmforge destination machine uses rsync 3.0.6, it's a Scientific Linux 6.0 with rsync 3.0.6 from its repository destination machine is running a rsync daemon with the following configuration: log file = /var/log/rsyncd.log

https://bugzilla.samba.org/show_bug.cgi?id=5457 Summary: Add a client-side --munge-symlinks option Product: rsync Version: 3.0.3 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: matt@mattmccutchen.net

SUMMARY There is a path-sanitizing bug that affects daemon mode in all recent rsync versions (including 2.6.2) but only if chroot is disabled. It does NOT affect the normal send/receive filenames that specify what files should be transferred (this is because these names happen to get sanitized twice, and thus the second call removes any lingering leading slash(es) that the first call left

https://bugzilla.samba.org/show_bug.cgi?id=13364 Bug ID: 13364 Summary: rsyncd clips trims relative symlinks outside of source tree Product: rsync Version: 3.1.3 Hardware: x64 OS: Linux Status: NEW Severity: normal Priority: P5 Component: core Assignee:

Hi, I've got an issue since about a week and I still can't solve it after a thorough research. I've setup a rsync server on my backup host, with shares using post/pre-xfer exec options but the scripts seems not to even be called : they should write a lockfile, and write in a logfile some information about the transfer request / report. I'm using rsync through stunnel and

https://bugzilla.samba.org/show_bug.cgi?id=4263 Summary: Symlinks gets corruped when rsyncd is used to 'put' the symlink. Product: rsync Version: 2.6.8 Platform: Sparc OS/Version: Solaris Status: NEW Severity: critical Priority: P3 Component: core AssignedTo:

Hi, I can't figure out how to backup a tree with symlinks. I either get errors like rsync: open(rc2.d/S20inetd) failed!!: No such file or directory (2) or (with --safe-link on the client and "munge symlinks = yes" on the server): ignoring unsafe symlink "/etc/rc2.d/S20inetd" (in backups) -> "/rsyncd-munged/../init.d/inetd" What I am trying to do is

https://bugzilla.samba.org/show_bug.cgi?id=13364 --- Comment #3 from Chris Severance <samba.severach at spamgourmet.com> --- >enable munge-symlinks. That way the client will get back the same out-of-tree symlink as it started with This is a lousy option for backups. The only way to get my original links back is to pull the restore through rsync. Restoring directly from the rsyncd server

I've just released rsync 3.0.0pre6, the latest pre-release version of the upcoming 3.0.0 release. Things are still progressing in our efforts to stamp out bugs for the final release. There are still some things reported earlier that I have either not yet had a chance to fix or have been unable to reproduce yet, but I hope to get even more of these problems sorted out soon. Please keep up

I've just released rsync 3.0.0pre6, the latest pre-release version of the upcoming 3.0.0 release. Things are still progressing in our efforts to stamp out bugs for the final release. There are still some things reported earlier that I have either not yet had a chance to fix or have been unable to reproduce yet, but I hope to get even more of these problems sorted out soon. Please keep up

On Mac OS X 10.5.2 I run rsync to keep a couple of instances of my / usr/local tree in sync. With Apple's rsync I run (e.g.): sudo /usr/bin/rsync --rsync-path=/usr/bin/rsync -E --progress -avu -- delete --dry-run --exclude=TeXLive-working-copy/ --exclude=context- update/ --exclude=.Spotlight-V100/ --exclude=.fseventsd/ \ -e "ssh -i /Users/gerben/.ssh/id_rsync -l root" \

Hy there, My name is Alex Vladulescu, and i found this very interesting tool for backup files and folders over remote network servers. For the past four days i have been reading the FAQ on the site, google-ing the web for some answers on my local problem, but i am very stuck, nothing seems to answer my question so far. My issue consists on having a rsyncd.conf on a master server on which i

This adds support for whitelisting the acceptable options in the "refuse options" setting in rsyncd.conf. It introduces "!" as a special option string that refuses most options and interprets any following strings as patterns of options to allow. For example, to allow only verbose and archive: refuse options = ! verbose archive The "!" does't refuse no-iconv,

https://bugzilla.samba.org/show_bug.cgi?id=4757 Summary: Daemon mis-logs paths if module path in rsyncd.conf is relative Product: rsync Version: 3.0.0 Platform: Other OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Hi, I'm trying to setup an rsync daemon such that I can synchronize my home pc (or other remote system) with my pc at work. I'm fairly new to linux and am just starting to learn its amazing possibilities. I followed an online toturial to create a rsyncd.conf file which reads: #motd file = /etc/rsyncd.motd log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file =

Hi all, Tripped over a documentation bug. I'm guessing the behavior I've found isn't a bug in itself as it's kind of implied by chroot (unless the /etc/passwd db is read *before* you do the chroot call), so I'm calling it a documentation bug. The Setup: System A: running rsync --daemon from xinetd, configured with a read-only share. System B: syncing a local directory

Hi all. This looks like a common question. I want to backup a dir, in which i put some symlinks, so it looks like machinegun:/tmp/daily_backup # ls -la total 8 drwxr-xr-x 2 root root 4096 2010-02-17 17:41 . drwxrwxrwt 19 root root 4096 2010-02-17 17:30 .. lrwxrwxrwx 1 root root 16 2010-02-17 17:41 cgi-bin -> /srv/www/cgi-bin lrwxrwxrwx 1 root root 4 2010-02-17 17:17 etc -> /etc