[comp.sys.apollo] telnet/rlogin question

thompson@ANIMAL.SSEC.HONEYWELL.COM ("John Thompson") (05/03/90)

Hi netlanders:
Well, now it's my turn to ask what's bound to be a stupid question
with an obvious answer.  Loading 10.2, on several node types (dn4000,
dn3550, dsp160), I can not successfully telnet or rlogin to the node
after loading.  I'm sure it's an ACL problem, but WHERE?

Details:
	1) I adjust the ACLs to something between open and closed.  This
is probably what's screwing me up.
	2) Some nodes have come up just fine (dn3000, dn3550, dn4500).  I
don't know what I did to start the problems.
	3) tcp/ip is definitely up and running.  THis isn't THAT trivial
a problem.
	4) "telnet hostname" gives the connection message, and the intro
login messaage, and the login: prompt.  It accepts input, and immediately
returns with "login incorrect" and a new login: prompt.
	5) "rlogin hostname" gives the error message
		bind: Permission denied
		rcmd: socket: Permission denied
	   and sends me back to my local node.
	6) ACLs on the /dev directory give world 'rwxk' rights.  Dirs
created in /dev have the same rights, files in /dev give world 'rwx'.


Thanks for any/all help.
John Thompson
Honeywell, SSEC
12001 State Hwy 55
Plymouth, MN   55441
thompson@animal.ssec.honeywell.com
thompson@pan.ssec.honeywell.com

My views, opinions, and problems are my own.  Honeywell takes no
responsibility for them -- they'll always blame me.               :-)

achille@cernvax.UUCP (achille petrilli) (05/04/90)

In article <9005030049.AA04549@umix.cc.umich.edu> thompson@ANIMAL.SSEC.HONEYWELL.COM ("John Thompson") writes:
>	5) "rlogin hostname" gives the error message
>		bind: Permission denied
>		rcmd: socket: Permission denied
>	   and sends me back to my local node.

If you look up in /etc/services the ports on which rlogin/rshell are listening,
you'll see that both port numbers are < 1024. On Unix, you must be root to     
'bind' on such port numbers. This means rlogin should be mode 4755 and is no
more, probably because of the changes to the ACLs. I seem to remember that this
is a new feature at sr10.2 (i.e. sr10.1 was not "real Unix" in this respect and
did not need you to run as root to bind to port numbers < 1024).

Hope this helps,
	Achille Petrilli