[4099] in Kerberos
Telnet Principals
daemon@ATHENA.MIT.EDU (Matt Perry)
Thu Oct 27 16:21:25 1994
To: kerberos@MIT.EDU
Date: Thu, 27 Oct 1994 18:24:21 GMT
From: mattp@apertus.com (Matt Perry)
I am working with MIT K4 and a telnet client that runs on a PC that
supports K4. I have a service that handles Telnet clients which
follow RFC1411/1416.
I am able to authenticate the client if I set up the service key to
with a principal of "rcmd" and an instance of <machine name>.
It appears from the Telnet code I have that it always assumes that
the end-service is going to be known by Kerberos as "rcmd".
In rfc1411 there is only one line that mentions rcmd:
In:
3. Implementation Rules
...
The authenticator (Kerberos Principal) used is of the form
"rcmd.host@realm".
...
Does this mean that any Service with Telnet support must be known as rcmd?
What if one has multiple Services with Telnet support on the same
host and wants to differentiate those services within Kerberos?
Matt Perry
Apertus Technologies, Inc.
mattp@apertus.com
