similar to: [PATCH] rrsync: Add several long options used by BackupPC

https://bugzilla.samba.org/show_bug.cgi?id=6020 Summary: support/rrsync fails when server-side options include "- e." Product: rsync Version: 3.0.4 Platform: All OS/Version: Other Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org

https://bugzilla.samba.org/show_bug.cgi?id=11879 Bug ID: 11879 Summary: escape rrsync restricted folder 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 all, is it possible to get rrsync with the "--delete" option working? Or is the rsync server really started unidirectional in this special scenario? Regards. JS -- GRATIS f?r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

https://bugzilla.samba.org/show_bug.cgi?id=11513 Bug ID: 11513 Summary: Modified rrsync to support write-only usage Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: core Assignee: wayned at samba.org

Hi, Since I am new around here and I could not find this anywhere, is there something like a list of commit ids of llvm and clang which are known to work together? I've ran a lot of times in this situation that I can't build clang because some interfaces changed in llvm and I had to find commits which work together by multiple checkout and compile iterations by hand. As you probably all

On 12/03/2014 01:37:58 PM, Kevin Korb wrote: > As far as a backup provider goes I wouldn't expect them to use rsync > over SSL unless that were built into rsync in the future (and has > been > around long enough that most users would have it). > > I would expect them to either use rsync over ssh secured by rrsync or > rsyncd over ssh with them managing the rsyncd.conf

> The benefit of rsync over ssh secured by rrsync is that it is more > like what rsync users are already used to. i don`t like rsync over ssh in an environemt with users you can?t trust. from a security perspective, i think such setup is broken by design. it`s a little bit like giving a foreigner the key to your front door and then hope that the door in the corridor to your room will be

Hi, I'm using rsync over ssh. Is there a way to log the transfer statistic on the server side. Some thing like rsync client "--stats" option. Do you thing it possible by some modification to rrsync? http://samba.anu.edu.au/ftp/unpacked/rsync/support/rrsync Regards, Milutin Voinivich -------------- next part -------------- A non-text attachment was scrubbed... Name: milutin.vcf

https://bugzilla.mindrot.org/show_bug.cgi?id=3570 Bug ID: 3570 Summary: Add substitution token for explicitly selected IdentityFile for ControlPath selection Product: Portable OpenSSH Version: 9.3p1 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5

Hi, Background : I am using rsync to push/sync FTP uploaded files from master server to slave servers. On slaves the full directory path of each file doesn't exist so rsync is unable to sync it and there a no options in rsync to do something like "mkdir -p/install -D -d" on destination before sync file. N.B. I don't want to do a full sync of the root/home directory every time a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As far as a backup provider goes I wouldn't expect them to use rsync over SSL unless that were built into rsync in the future (and has been around long enough that most users would have it). I would expect them to either use rsync over ssh secured by rrsync or rsyncd over ssh with them managing the rsyncd.conf file. Either way the server side

Hi, We use an rsync (rrsync, to be precise) based back-up solution. Every so often an iSCSI based file-system gets brought up and left connected for the night. After a mount event rsync will back that volume up, including server TB of data that haven't been modified, but the ctime is newer than the mtime. Is there a way to stop this behaviour? Cheers, Andrej

Hi Nick, Just in case you aren't already aware of it, there is a tool that limits rsync to particular directories: rrsync - Restricts rsync to subdirectory declared in .ssh/authorized_keys https://www.samba.org/ftp/unpacked/rsync/support/rrsync There is also a generic tool (I wrote this one) for limiting incoming ssh commands to a fixed list of specific actual commands (with

https://bugzilla.mindrot.org/show_bug.cgi?id=2713 Bug ID: 2713 Summary: Please provide a StrictModes-like setting (command line parameter) for ssh (client) Product: Portable OpenSSH Version: 7.5p1 Hardware: Other OS: Other Status: NEW Severity: enhancement Priority: P5

from a security perspective this is bad. think of a backup provider who wants to make rsyncd modules available to the end users so they can push backups to the server. do you think that such server is secure if all users are allowed to open up an ssh shell to secure their rsync transfer ? ok, you can restrict the ssh connection, but you open up a hole and you need to think twice to make it secure

https://bugzilla.samba.org/show_bug.cgi?id=10181 Summary: --stats bug Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: RutleCorps at gmail.com QAContact: rsync-qa at

Hi, I've a setup where a special account (limited by the ssh-key) can use rsync via ssh to make a backup of / (limited by sudo). Obviously it needs read-access to everything. However, since he can read everything, he could also easily _write_ everything. Can I limit the rsync command on the server to read-only? Thanks in advance Martin -- Martin Schr?der,

The delete-dir-and-suffix patch creates two new command line options as follows: --delete-dir --delete-suffix The delete-dir and delete-suffix options give the ability to store backup of deleted files on the receiver in different directories or with different suffix than the backup of files that have been changed but that are still on the source drive. Both commands can be

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The ctime will always be newer or the same as the mtime. This is because changing the mtime also changes the ctime as does other things like changing the permissions. Rsync only pays attention to the mtime because rsync can set a specific mtime (--times) but setting a specific ctime is impossible as it would violate the basic *nix security model.

Setup: Redhat linux 7.3 rrsync: version 2.5.6 protocol version 27 I'm trying to employ rsync in conjuction with with a cvs setup. The setup employs a bufffer where changes are made then moved to a checked out module from cvs repository and finally any cvs actions necessary are done. So far just testing this out with some copies of both directory trees. Right now the files in both are