[11727] in Kerberos-V5-bugs
[krbdev.mit.edu #6793] memory leak
daemon@ATHENA.MIT.EDU (Arlene Berry" via RT)
Wed Oct 6 19:09:15 2010
Mail-followup-to: rt@krbdev.mit.edu
mail-copies-to: never
From: ""Arlene Berry" via RT" <rt-comment@krbdev.MIT.EDU>
In-Reply-To: <rt-6793@krbdev.mit.edu>
Message-ID: <rt-6793-33223.19.3239897397257@krbdev.mit.edu>
To: "'AdminCc of krbdev.mit.edu Ticket #6793'":;"'AdminCc of krbdev.mit.edu Ticket #6793'":;@MIT.EDU
Date: Wed, 6 Oct 2010 19:09:11 -0400 (EDT)
Reply-To: rt-comment@krbdev.MIT.EDU
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krb5-bugs-bounces@mit.edu
If I'm understanding things right, objects should only be added to the
internal database if they are going to be passed out in output
parameters. Both instances of kg_init_name in acquire_cred.c are called
on cred->name which is an internal object and which is not passed out.
I checked krb5_gss_release_cred which does not use KG_INIT_NAME_INTERN
when releasing cred->name. I also looked at krb5_gss_inquire_cred to
see what it does and, if it passes back the name, it calls
kg_duplicate_name with KG_INIT_NAME_INTERN set. As best I can
determine, cred->name is strictly an internal object and the
kg_init_name calls on it should not set KG_INIT_NAME_INTERN.
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
