[16712] in Kerberos_V5_Development
Re: mechglue debugging
daemon@ATHENA.MIT.EDU (Greg Hudson)
Tue Mar 22 10:42:15 2011
From: Greg Hudson <ghudson@mit.edu>
To: Luke Howard <lukeh@padl.com>
In-Reply-To: <937A7C25-E3A8-4AD5-B89D-64641290DC8A@padl.com>
Date: Tue, 22 Mar 2011 10:42:07 -0400
Message-ID: <1300804927.2397.713.camel@t410>
Mime-Version: 1.0
Cc: Sam Hartman <hartmans@mit.edu>, "krbdev@mit.edu List" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On Tue, 2011-03-22 at 00:40 -0400, Luke Howard wrote:
> krb5 context is not a problem (if not ideal), but it does appear to
> require tracing be explicitly enabled on the context, which is not
> very useful if the caller does not have a way to access the context.
No, you can set the environment variable KRB5_TRACE to a filename (or
to /dev/stdout) to enable tracing on all non-secure contexts.
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
