similar to: [Bug 11879] New: escape rrsync restricted folder

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,

rrsync used to throw the error /usr/local/bin/rrsync: invalid rsync-command syntax or options when run under BackupPC 3.2.1, with this patch full and incremental backups work. --- support/rrsync | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/support/rrsync b/support/rrsync index 6f83f9d..c231ea3 100644 --- a/support/rrsync +++ b/support/rrsync @@ -60,6 +60,7 @@ our

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=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=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

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

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

> 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'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,

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

I've read a few tutorials about how to use rsync via ssh using the command= functionality to restrict where the user can sync to. I've got this on the on the destination side in it's ~/.ssh/authorized_keys... command="rsync --server -vvnlogDtpre.iLsf --timeout=999 . bkp",no-port-forwarding,no-X11-forwarding,no-agent-forwarding ssh-rsa AAetc I've tried variations of the

Hi, Is there a security problem with ssh that I've missed??? Ik keep getting these hords of: Failed password for root from 69.242.5.195 port 39239 ssh2 with all kinds of different source addresses. They have a shot or 15 and then they are of again, but a little later on they're back and keep clogging my logs. Is there a "easy" way of getting these ip-numbers added to

hai, i tried to install wine package in redhat enterprise linux 4 but i am getting so many errors.i tried too much. send step by step how to install wine in linux thanks M. SWAMY --------------------------------- Why delete messages? Unlimited storage is just a click away. -------------- next part -------------- An HTML attachment was scrubbed... URL:

can somebody help me to install steam!!!

When rsync is used in remote-shell server mode, the documentation says: "Rsync supports connecting to a host using a remote shell and then spawning a single-use "daemon" server that expects to read its config file in the home dir of the remote user." I have been trying to make rsync read a config file (which I presume should be named rsyncd.conf) in the home directory of the

In the past, I had restricted rsync so that the -e option was disallowed. As of rsync-3.0.0, I'm now seeing the following requests being made (on the server side): rsync --server -vlogDtprze.iL . I want to prevent '-e' as a client side option so arbitrary programs can't be executed. I found the following, but didn't trace through to verify exactly where I was in the code

Since rsync 3.0 i've detected a problem with rssh and -e option....rssh doesn't allow this option...but is essential to me (cyphered transmission with ssh). Surfing the net i've seen a guy that made a patch but I don't know how reliable is...and rssh former programer says he just left the project so it's no longer his problem. Is this stuff going to be updated in rsync or is

For full system backup, rsync obviously needs to run as root on the machine being backed up For preservation of user/group/permissions info, rsync also typically needs to be run as root on the machine storing the backup - although there appear to be various ways to avoid this (e.g. using fakeroot -s, or running rsync inside a Xen VM which only stores the backup of one host) Can anyone comment on

I've trying to do a backup from a remote host to a local machine via rsync using the following configuration: Remote host (Red Hat Enterprise Linux ES3): $ uname -srmpi Linux 2.4.21-47.EL i686 athlon i386 $ cat /etc/redhat-release Red Hat Enterprise Linux ES release 3 (Taroon Update 8) $ rsync --version rsync version 2.6.8 protocol version 29 Local machine (Mac OS X 10.4.8, Intel): $