[2746] in Kerberos
Re: Cannot decode Authenticator
daemon@ATHENA.MIT.EDU (Derek Atkins)
Tue Jul 13 14:50:10 1993
To: Jonathan Chinitz <jec@isoft.com>
Cc: kerberos@Athena.MIT.EDU, gopalan@watson.ibm.com (Anis Gopalani)
In-Reply-To: [2744] in Kerberos
Date: Tue, 13 Jul 1993 14:32:03 -0400
From: Derek Atkins <warlord@GZA.COM>
Anis writes:
> I am writing a sample client-server application that uses kerberos V4.
> It seemsthat the server receives authentication but cannot decode
> successully. If I remove /etc/srvtab, I get the message "Can't decode
> authenticator (krb_rd_req) Thestatus of the return code is 31. If I
> put it back as it should be I get a core dump. Any idea?
Jonathan responds:
> Have you verified that the server password in the KDC is the same as
> the one in your srvtab? I have experienced "Cannot decode
> authenticator" errors when I have changed one, but forgot to do an
> ext_srvtab. When the server tries to learn the session key from the
> ticket, using the srvtab password, it fails (because they are
> different) and thus fails to decrypt the authenticator.
And I say:
The problem is not that you have an incorrect password. Look at what
your problem is: When the srvtab isn't there, krb_rd_req is failing
with an error (this is the correct behavior). When the srvtab is in
place, you get a core dump. Well, this tells me that there is a bug
in your code somwhere that is causing it to core dump.
I recommend compiling with debugging information and run the server
under your favorite debugger. Then connect the client to it and try
to figure out where your code is dying. Take a look at the core dump
and see whats causing it to die. Is it a seg fault or bus error or
something else.
I highly doubt that the bug is in Kerberos, and given the problem you
describe, I doubt that the problem is an incorrect password.
Hope this helps..
-derek
