Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ucbvax!agate!shelby!MIT.EDU!jon
From: jon@MIT.EDU (Jon A. Rochlis)
Newsgroups: comp.protocols.kerberos
Subject: Re: Kerberized bsd and ports
Message-ID: <9101241932.AA01119@delwin.MIT.EDU>
Date: 24 Jan 91 19:32:45 GMT
References: <9101241916.AA01920@robin.mitre.org>
Sender: news@shelby.stanford.edu (USENET News System)
Organization: Internet-USENET Gateway at Stanford University
Lines: 20


   I added /etc/inetd.conf entries on the server for klogin, eklogin and kshell.
   Also on the server machine I've got /etc/services entries for klogin and
   eklogin (not sure how the knetd entry in /etc/services is used).  

Ignore knetd, it's obsolete.

   The same
   /etc/service entries are on the client machine. I wasn't sure what port
   to use: I picked 513 which is the login port on this machine. 

We use 543 for kerberos rlogin.  513 is the normal rlogin port.  This
could indeed cause confusion, but I don't think it's your problem.
The permission denied makes me suspect that you did not install the
rlogin binary setuid root.  I would guess it's trying to bind a
"priviledged" port (I know that's a dumb concept given a real
authentication system, we probably just didn't touch that part of the
rlogin code).

		-- Jon