Heads up: kadm5 initialization API change in 1.8

Nicolas Williams Nicolas.Williams at sun.com
Mon Aug 17 16:06:28 EDT 2009

On Mon, Aug 17, 2009 at 03:41:00PM -0400, ghudson at mit.edu wrote:
> This is because libkadm5 uses its own internal context inside server
> handles.  My understanding is that krb5 contexts used to be considered
> cheap, so it was fine to keep a bunch of them around for no reason
> other than API convenience, but that's not true now that we have
> extended error messages.  The presence of multiple contexts makes it
> much less likely that good error information will make its way back to
> the user.

But all the kadm5 server functions already take a server handle, and
that server handle already has a krb5_context field, so it should be
possible to always use the same krb5_context.  What am I missing?


More information about the krbdev mailing list