[36744] in Kerberos

home help back first fref pref prev next nref lref last post

Re: DEBUG: Context data in KDC to peek which principal/realm is

daemon@ATHENA.MIT.EDU (Benjamin Kaduk)
Mon Jan 26 16:02:12 2015

Date: Mon, 26 Jan 2015 16:01:54 -0500 (EST)
From: Benjamin Kaduk <kaduk@mit.edu>
To: Cedric Blancher <cedric.blancher@gmail.com>
In-Reply-To: <CALXu0UcOhjpiKGWS8XyYygNtbr8F=JL3fYfWGoE3tHbpSpsC2g@mail.gmail.com>
Message-ID: <alpine.GSO.1.10.1501261558090.23489@multics.mit.edu>
MIME-Version: 1.0
Cc: "<kerberos@mit.edu>" <kerberos@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu

On Thu, 22 Jan 2015, Cedric Blancher wrote:

> We're debugging a KDC problem and ran into a wall. Is there any
> context data in KDC to peek which principal and realm is currently
> being processed in the KDC?

AS-REQ processing has a struct as_req_state that holds a lot of useful
data.  TGS-REQ processing is not quite so straightforward; the locals in
process_tgs_req() are probably the closest analogue.

-Ben Kaduk
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post