Hello,
I am using rsync for the first time.
I have rsync 2.6.5 running on Solaris 9. It was built with gcc-2.95.
We are experiencing a reverse lookup host error in rsyncd.log when the
client with ip addy 180.X.XX.XX
tries to access rsync on my Solaris box.
2005/08/11 14:30:13 [18092] rsync denied on module log from unknown
(0.0.0.0)
2005/08/11 14:30:54 [18094] name lookup failed for 0.0.0.0: host/servname
not known
The rsyncd.conf file is configured as follows:
----------------------------------------------------
motd file = /export/home/mydir/edc/etc/motd
max connections = 2
use chroot = no
pid file = /export/home/mydir/edc/rsyncd.pid
lock file = /export/home/mydir/edc/rsyncd.lock
log file = /export/home/mydir/edc/log/rsyncd.log
transfer logging = yes
timeout = 300
hosts allow = 180.X.XX.XX
[log]
path = /export/home/mydir/edc/log
comment = Log files
read only = no
list = yes
----------------------------------------------------
When we comment the line:
#hosts allow = 180.X.XX.XX
We get this new error:
2005/08/11 14:31:47 [18119] name lookup failed for 0.0.0.0: host/servname
not known
2005/08/11 14:31:47 [18119] rsync allowed access on module log from UNKNOWN
(0.0.0.0)
2005/08/11 14:31:47 [18119] rsync on log from UNKNOWN (0.0.0.0)
2005/08/11 14:31:47 [18119] send UNKNOWN [0.0.0.0] log () rsyncd.log 2504
2005/08/11 14:31:47 [18119] sent 2673 bytes received 105 bytes total size
2504
In this case, the transfer does occur and the client gets the files it
needs, but this
means that we cannot restrict access to certain ip addy's.
DNS is working as we can succesfully ping the ip address in question with
it's server name (which, by the way, is in another subnet with a different
domain name).
Other's in my company have used rsync on Linux without any problems.
Any ideas on why the lookup is failing on Solaris 9?
Should I compile with a newer version of gcc?
Marcus Lozano
System Administrator
Maxim Integrated Products
On Thu, Aug 18, 2005 at 09:01:23AM -0500, Lozano, Marcus wrote:> 2005/08/11 14:30:13 [18092] rsync denied on module log from unknown (0.0.0.0)Are you using daemon-mode over rsh/ssh? If so, the only way rsync has to discover the remote IP address is out of the environment. It tries SSH_CONNECTION, SSH_CLIENT, and SSH2_CLIENT (all of which are, of course, entirely insecure since they could be overridden by the user prior to running rsync -- your remote shell is is the thing providing the security in such a scenario, not rsync). If you're using an rsync daemon via sockets, you should investigate why client_sockaddr() isn't functioning properly. ..wayne..