[30874] in Kerberos
gss_display_status question
daemon@ATHENA.MIT.EDU (Tom Anderberg)
Mon Mar 16 16:51:06 2009
MIME-Version: 1.0
Date: Mon, 16 Mar 2009 13:50:18 -0700
Message-ID: <b850befd0903161350g715949e9j50e39c539622ec88@mail.gmail.com>
From: Tom Anderberg <tdanderberg@gmail.com>
To: kerberos@mit.edu
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
