similar to: security issues

Hi there, I use rsync over ssh to syncronise various directories between a windows machine and a linux box. Now I want to sync files between two linux boxes. Because the I want to do that as a cron job I need rsa key authentification. I have a user called test on both machines. On both pc I also run "ssh-keygen -t rsa1" and enter no passphrase. I copied the identity.pub file from the

Greetings list, I've been banging my head against this for a few days now, so finally I throw myself upon your tender mercies. I had rsync working fine to make offsite backups via an IPSEC VPN over an ADSL connection - until the remote raid5 server went down. It was rebuilt with RedHat 8 and since then I have not been able to rsync to it. Both ends have vanilla rsync-2.5.5 installed.

I am using rsync 2.5.5 running as a daemon on the destination system, which is SuSE Linux 8.0. The source system is SuSE 7.3, also with rsync 2.5.5. With the default 'use chroot = true' and not using --numeric-ids, I get the wrong user names on the destination files. I have tracked this down to getpwnam() failing to return the user name from the passwd file. It does not fail when

We are using rsync to push DNS records from one machine (running rsync 2.5.6 as a client process on Debian woody) to a collocation server ( running rsync 2.5.6 as a daemon on RedHat 7.3). To test this process we are using a script that pushes one file from the Debian box to the collocation server. It appears that a file transfers, but upon checking there is no file transfer and an error in the

I'm getting an error trying to pull a file with ssh/rsync: $ rsync -e 'ssh -i .ssh/id_rsa' test@server.com::www/index.html index.html rsync: unable to open configuration file "rsyncd.conf": No such file or directory rsync error: syntax or usage error (code 1) at clientserver.c(502) rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync

Hi- I have a solaris 8 box with the latest ssl, ssh, and rsync all set up. ssh and an apache-sll site are running good - I feel confident that ssl and ssh are set up correctly, but when I use rsync over ssh, it (rsync) will allow me to sync as any (system) user from any host ecven though the rsyncd.conf file in /etc has user auth = <one real system user> and host deny = * is there

I am running rsync version 2.56 in daemon mode on a server running Redhat 8.0. When I check my log file (located in /var/log/rsyncd.log), the only lines I see have to do with the server starting up, like so: 2003/09/11 16:53:42 [15025] rsyncd version 2.5.6 starting, listening on port 873 I would like to see output relating to connections, usernames etc., so I set up the following rsyncd.conf

Hi all, When i use rsync with on the server : motd file = /etc/rsyncd.motd log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsync.lock [filieres] path = /home2 comment = Repertoire de sauvegarde des filieres read only = no hosts allow = 172.18.1.246 # vador only dont compress = *.gz *.jpg *.zip *.rpm *.tgz note : the

Hi rsync@lists.samba.org, when trying to use rsync there's an error message: 10.80.12.6: Connection refused rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(151) there are 2 servers, both have RedHat 7.3 installed rsync version 2.5.4 is used, protocol version 26 rsync is run on one of them as a demon

This has been asked before, but my question is somewhat different. On FreeBSD, the message: rsyncd[520]: /etc/pwd.db: No such file or directory is obviously caused by a chrooted rsyncd being unable to access /etc/pwd.db to get at the password database to convert UIDs to names and back. Workorounds of putting /etc/pwd.db in the chrooted directory have been offered, and that's one solution.

I've got an rsyncd.secrets file with 59 accounts in it. Almost all these need to be enabled concurrently. My rsyncd.conf thus has an auth users field with upward of 50 values. I'm starting to wonder at what point I'll have maxed that field out, especially as we're taking on new accounts all the time. Incidentally, whether or not there is a limit, is it possible to do some

I was looking for suggestions on how I could get rsyncd to send its log information to multilog, and I came across this post: http://marc.theaimsgroup.com/?l=rsync&m=105034709927741&w=2 Is there any initiative to integrate this or something like it into the rsync base? It would be a really useful feature for people who run rsync under process supervision. Toby

Hi, If anyone has an Idea on how to solve the following problem it would be greatly appreciated :). The scenario is as follows: Im running an rsync server on Redhat7.3. The rsync server configuration file looks as follows: #### rsyncd.conf log file = /var/log/rsyncd.log pid file = /var/run/rsyncd.pid lock file = /var/run/rsyncd.lock max connections = 5 use chroot = true list = true

I was startled to find that the --csum-length option is not implemented even though it is documented in the manpage. Not a good thing. Here's a patch that removes the manpage entry. I'd much rather not see this option and actually have the csum_length be per-file dynamic. Either way this patch should be applied at least until the code changes. The patch also brings rsync.1 and

Hello, (I found a post in the archives titled "link_dest checks perms despite no -p -o or -g" on April 7th, which might be related - not sure...) I'm trying to get a rotating daily backup going with previous days kept as hard links to save on network transfer and disk space. The plan: on day N, rsync to blah/N/, using --link-dest=../<N-1> (modulo 7 or whatever). My test

I have rsync-2.5.5 humming along on FreeBSD 4.7-STABLE with no apparent problems. However, I notice when some clients connect to sync, I get this in /var/log/messages rsyncd[42843]: /etc/pwd.db: No such file or directory rsync is running as root with this basic rsync.conf: use chroot = yes read only = yes timeout = 600 Well of course /etc/pwd.db exists and could be readable, but more

Hi, I'm trying to use rsync from Windows to Unix. I've followed the directions on : http://optics.ph.unimelb.edu.au/help/rsync/rsync_pc1.html I can see ssh running on the windows machine, because I tested it using telnet localhost 22 and I can see the result "SSH-2.0-OpenSSH_3.4p1". But when I try "$ rsync -avz -e ssh user@windowsserver::/rsync/* ." from the Linux

Hi, I would like to change the rsync default port to something other than 873. I changed in the rsyncd.conf file. But, still it listens to 873 only. How to fix this issue. Thanks and regards Sethu Subramanian Rengarajan Principal Solution Architect Green House Group Pte Ltd 750 Chai Chee Road #02-01/03, The Oasis Technopark@Chai Chee SINGAPORE 469000 Tel: (65) 62220068 Ext 8588 DID: (65)

Just a few quick questions.. Does rsync copy open files? If so, does file integrity remain intact? I’m looking to backup IIS log files and maybe Oracle and SQL Server DB files. If rsync isn’t appropriate, what would you recommend? Thanks for your time, Mark J. de Jong ,.,.,.,...,.,,.,..,.,....,.,..,.,..,.,.,,.,...,..,,... Senior Network Engineer - Secure Dog Hosting, Inc. P.703.256.2869

With much hope I upgraded to rsync version 2.5.6 in hopes that it would correct the symbolic link bug I have been wrestling with... No dice. It still insists on dropping the leading slash from a symbolic link outside the source tree. Interactively it still works fine, but as a daemon it's busted. See previous posting 'rsyncd treats symlinks differently' for details. Can someone