[2001] in Kerberos-V5-bugs
Re: Kerberos v5b6 problems
daemon@ATHENA.MIT.EDU (Sam Hartman)
Thu Jun 13 11:30:45 1996
To: Paul Weber <weber@anise.ee.cornell.edu>
Cc: Sam Hartman <hartmans@MIT.EDU>, krb5-bugs@MIT.EDU
From: Sam Hartman <hartmans@MIT.EDU>
Date: 13 Jun 1996 11:30:33 -0400
In-Reply-To: Paul Weber's message of Thu, 13 Jun 1996 09:30:23 -0400
>>>>> "Paul" == Paul Weber <weber@anise.ee.cornell.edu> writes:
Paul> Sam, Thank you, Thank you, Thank you !!!!
Paul> Things seem to be working now! However when I use login.krb5
Paul> I get the following message ( but it does work ):
Paul> "login/v4: Unknown code 61 converting to V4 credentials" and
Paul> then it logs me in.
This probably means you are not running a krb524d. If you don't use Kerberos V4, you can ignore this message.
(Yes,the message could be improved.)
Paul> Sam Hartman wrote:
>> >>>>> "Paul" == Paul Weber <weber@anise.ee.cornell.edu>
>> writes:
>>
Paul> Sam Hartman wrote:
>> >>
Paul> thor(37) > rlogin thor thor.ee.cornell.edu: Connection
Paul> refused rlogin: kcmd to host thor failed - Unknown code ____
Paul> 255 trying normal rlogin (/usr/ucb/rlogin) Last login: Tue
Paul> Jun 11 14:02:22 from THOR.EE.CORNELL. SunOS Release 4.1.4
Paul> (GENERIC) #1: Thu Mar 14 09:50:59 EST 1996
>> >> >> Well, what services did you enable in /etc/inetd.conf,
>> and did >> inetd give errors about them? When you telnet to
>> the klogin and >> eklogin ports on your machine, what happens.
Paul> No errors inetd
>> You actually installed things correctly, but you didn't use
>> the rlogin command correctly. Basically, you only enabled
>> encrypted rlogin. By default, the rlogin(and rsh) clients do
>> not use encryption. You need to include the -x option to get
>> this to work. For example:
>>
>> /krb5/bin/rlogin thor -x
>>
Paul> rlogin thor -x does not work it just hangs, however, rlogin
Paul> thor does work.
I assume you removed the -e from the klogin line in inetd.conf
for this to work. Are you sure you didn't accidentally remove the -e
from the eklogin line as well?
Paul> One last thing! The little-endian CPU code in shs.c would
Paul> not compile on a SUN running 4.1.4. I changed the code so
Paul> the complier would take it. I'm not sure if the changes I
Paul> made broke the code or not, but everything seems to work for
Paul> me and it compiled fine. Here is the code:
Known bug. A last minute change broke this code. Nothing
currently uses shs so it isn't a big deal. (SHS is included so it can
be used by the DES3 code which isn't quite ready).
--Sam
