Rsync Error..

Tim Conway conway at us.ibm.com
Fri Apr 23 16:09:32 GMT 2004


Ah!  Now I've got you.
rsh without parameters does an rlogin, which uses the service commonly 
called "login", on port 513.
With parameters, it does a plain rsh, using the service commonly called 
"shell", on port 514.

Here's a system with both holes open (deep inside a well-protected 
intranet, host and usernames deleted to protect the innocent).
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
egrep "^shell|^login" /etc/services /etc/inetd.conf
/etc/services:login             513/tcp
/etc/services:shell             514/tcp         cmd             # no 
passwords used
/etc/inetd.conf:shell   stream  tcp     nowait  root    /usr/sbin/in.rshd  
   in.rshd
/etc/inetd.conf:login   stream  tcp    nowait  root /usr/sbin/in.rlogind 
in.rlogind
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
You probably have the shell line in inetd.conf commented out.  open it, 
HUP inetd, and you're probably in business.  No sane security guys could 
complain about shell if login is permitted.
I'm pretty sure that's your issue.  It's also possible, of course, that 
you shell service is on an alternate port, or commented out of services. 
You'll see it, whatever it is.

All ssh sessions go through the sshd service, on port 22, and most systems 
that have one or the other of login and shell enabled have both.  Yours is 
just an unusual case.

Tim Conway
Unix System Administration
Contractor - IBM Global Services
desk:3032734776
conway at us.ibm.com








Hello,
when i gave "rsh 66.123.34.123 which rsync" at the source system i got the 
following error
66.123.34.123:  Connection refused
 
"rsh 66.123.34.123" works perfectly fine.
 
What could be the problem..?



More information about the rsync mailing list