[30611] in Kerberos
gss_display_status
daemon@ATHENA.MIT.EDU (Tom Anderberg)
Mon Jan 12 18:24:01 2009
Message-ID: <b850befd0901121523v269865c8t4714e87a0aeb47d2@mail.gmail.com>
Date: Mon, 12 Jan 2009 15:23:10 -0800
From: "Tom Anderberg" <tdanderberg@gmail.com>
To: Kerberos@mit.edu
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu
Hi all,
I work on a security library that provides access to Kerberos through
GSS-API. We are trying to log Kerberos errors using gss_display_status. We
have noticed that the same error code can, at different times, produce
either a helpful or an unhelpful error message. Sometimes this seems to
depend on the Kerberos operations that have been performed.
For example:
Call gss_display_status with 0x96c73a22 and get "Unknown code krb5 34"
Then call gss_acquire_cred (doesn't matter if it succeeds or fails)
Repeat the initial call to gss_display_status and get "Request is a
replay"
However, there are platforms (such as Linux) where we always just get
"Unknown code".
Is there something that we need to do to initialize Kerberos before calling
gss_display_status? Or is there some other explanation?
Thanks,
Tom
________________________________________________
Kerberos mailing list Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos
