memory leak in some Kerberos APIs?

[Tom Yu]

>>>>> "Kent_Wu" ==   <Kent_Wu at trendmicro.com> writes:

Kent_Wu>  Actual leaks report    (actual leaks:         4  total size:      57 bytes)
Kent_Wu>  Total  Num of  Leaked      Allocation call stack
Kent_Wu>  Size   Blocks  Block
Kent_Wu>                 Address
Kent_Wu> ======  ====== ==========  =======================================
Kent_Wu>     25       1    0x2bbd8   asn1buf_remove_octetstring<-
Kent_Wu> asn1_decode_octetstring<-asn1_decode_etype_info_entry<-asn1_decode_etype_info
Kent_Wu> <-decode_krb5_etype_info<-krb5_do_preauth<-krb5_get_init_creds<-
Kent_Wu> krb5_get_init_creds_password

Kent_Wu>     16       1    0x2ab88   calloc<-asn1_decode_etype_info<-
Kent_Wu> decode_krb5_etype_info<-krb5_do_preauth<-krb5_get_init_creds<-
Kent_Wu> krb5_get_init_creds_password<-main

Kent_Wu>      8       1    0x2b2b8   get_profile_etype_list<-krb5_get_tgs_ktypes<-
Kent_Wu> krb5_gss_init_sec_context<-gss_init_sec_context<-main

Kent_Wu>      8       1    0x36248   asn1_decode_etype_info<-decode_krb5_etype_info<-
Kent_Wu> krb5_do_preauth<-krb5_get_init_creds<-krb5_get_init_creds_password<-main

Have you tried compiling with one of the beta releases of krb5-1.3?  I
seem to recall that we have fixed some preauth-related memorly leaks.

---Tom