similar to: security hole in non-chroot rsync daemon

https://bugzilla.samba.org/show_bug.cgi?id=13105 Bug ID: 13105 Summary: 1byte heap overflow in sanitize_path Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

Hiya. While merging the 2.6.0 changes into our modified version of rsync, I noticed the following bit of code in 2.6.0's options.c: extern int sanitize_paths; if (sanitize_paths) sanitize_path(strdup(files_from), NULL); filesfrom_fd = open(files_from, O_RDONLY|O_BINARY); Since sanitize_path modifies its first argument in place, the path that open()

Hi NG, I want to do incremental backups to a remote server running rsyncd (because daemonless transfer via ssh often hangs!). In contrast to transfer via ssh (without remote rsyncd) this doesn't seem possible, or do I miss something? Imagine I want to incrementally backup `mydir' to the backup space `backup' on e remote server `alpha' running an rsync daemon. rsyncd on

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

When using the rsync server without chroot, the --link-dest and --compare-dest options are almost useless. This is because sanitize_paths is called on the link-dest directory, stripping out leading dots and slashes. Thus, the only possiblitiy for a link-dest directory is under the target directory, which is generally not useful. There doesn't seem to be an easy fix. sanitize_paths is

https://bugzilla.samba.org/show_bug.cgi?id=10445 Summary: flag to suppress link_stat error messages Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: mij at bitchx.it

Version: 1.0test53 .. 1.0.rc14 (ie. all 1.0alpha, 1.0beta and 1.0rc versions so far). 0.99.x versions are safe (they don't even have mmap_disable setting). Problem: When mmap_disable=yes setting is used, dovecot.index.cache file is read to memory using "file cache" code. It contains a "mapped pages" bitmask buffer. In some conditions when updating the buffer it allocates

Version: 1.0test53 .. 1.0.rc14 (ie. all 1.0alpha, 1.0beta and 1.0rc versions so far). 0.99.x versions are safe (they don't even have mmap_disable setting). Problem: When mmap_disable=yes setting is used, dovecot.index.cache file is read to memory using "file cache" code. It contains a "mapped pages" bitmask buffer. In some conditions when updating the buffer it allocates

https://bugzilla.samba.org/show_bug.cgi?id=12817 Bug ID: 12817 Summary: [PATCH] Allow daemon itself to chroot Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

Hi there, I set up my company's back up server using rsync. And I've got a strange problem. I searched in the archives of this list, but none of them seems not giving me an idea to solve the problem. If anyone can help, it would be grateful. I'm using cron by a user (non wheel/admin) to rsync everyday during the night. The cron is set in the server to transfer the backing-up

I just installed rsync on two machines, I think I'm a complete moron, and I need a clue bat. The remote machine's /etc/rsyncd.conf (just for testing): use chroot = no log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock [auth] path = /var/www/auth comment = apache authentication files. read only = yes Then for a test, I fired up

https://bugzilla.samba.org/show_bug.cgi?id=14407 Bug ID: 14407 Summary: link_stat ... failed: No such file or directory: should mention which end of the connection it is talking about Product: rsync Version: 3.2.0 Hardware: All OS: All Status: NEW Severity: normal

I am trying to use rsync (3.0.6) to keep two directories as exact duplicates. I would normally run: rsync -av -S --delete /path/to/src/ /path/to/dst/ to do this. Unfortunately, the directories have become rather large (2TB, a million files) and so the tree walk has become a prohibitively time consuming part of the operation. However, I have a way to generate a list of file changes

Command like this: rsync -rxlupogtSvve ssh $src_host:"/home/wss_disk/calendar.data/'Conference Calls'" $targ_dir works fine with blanks embeded in the file name. When I try to script it like this: COM='`find '$src_dir' -mtime -'$days' -type f `' rsync -rxlupogtSvve ssh $src_host:"$COM" $targ_dir works fine on regular filenames,

Hi All, Attempting to run rsync but getting "no such file or directory" message. What looks like is happening is solaris 8 is removing the "space" between .../db2_backup and db2inst1@enolagay... As a result rsync creates a new dir on the same box with the files in it. Not sure what to do. VERY new to unix and rsync. bash-2.03$ rsync -e ssh -av

Hi, I am using rsync version 3.0.7 on an arm linux based embedded device. The device pulls data periodically from a rsync server and stores the files on an SD card. The partial, temp and final rsync destinations all reside on the SD card. I came across an issue where it seems that the rsync call returned with a success but the files that it pulled are not moved immediately to its final

https://bugzilla.samba.org/show_bug.cgi?id=6095 Summary: code 23 when files or directories disappear, instead of code 24. Product: rsync Version: 3.0.5 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

Just tripped over this one today. $ rsync --no-motd rsync://alphageek.dyndns.org/slackware rsync: link_stat "." (in slackware) failed: No such file or directory (2) rsync error: some files could not be transferred (code 23) at main.c(1498) [receiver=3.0.1pre2] $ rsync --no-motd rsync://alphageek.dyndns.org/slackware/slackware-current drwxr-xr-x 4096 2008/03/26 01:30:27

Hello, we have a old version of rsync running since 2005. Now I tried to sync between two new servers with rsync 3.0.7 and get the error rsync: link_stat "." (in sprengel) failed: Permission denied (13) On one server ( 192.168.10.2 ) I have rsync running as daemon and this rsyncd.conf read only = true use chroot = false transfer logging = true log format = %h %o %f %l %b log file