Need to _kt_close() after _kt_default() ?

Rick van Rein rick at
Sat Sep 17 07:32:28 EDT 2016


According to the krb5 API description for krb5_kt_default(), "The key
table is not opened."

Still, valgrind reports a memory leak in my program, and points back to
a calloc() inside krb5_kt_default().  When I call krb5_kt_close() on the
keytab this leak is gone.

Might this be a glitch in the documentation, or elsewhere?


More information about the krbdev mailing list