[11710] in Kerberos-V5-bugs
[krbdev.mit.edu #6787] S4U memory leak
daemon@ATHENA.MIT.EDU (Arlene Berry" via RT)
Tue Sep 28 08:47:01 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-6787@krbdev.mit.edu>
Message-ID: <rt-6787-33187.3.26524382931218@krbdev.mit.edu>
To: "'AdminCc of krbdev.mit.edu Ticket #6787'":;"'AdminCc of krbdev.mit.edu Ticket #6787'":;@MIT.EDU
Date: Tue, 28 Sep 2010 08:42:34 -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
When using S4U, in src/lib/gssapi/krb5/s4u_gss_glue.c
kg_compose_deleg_cred, it creates a new unique memory credential cache
that is internal to the credential. It needs to be destroyed when the
credential is released. However, krb5_gss_release_cred only closes the
cache and it's being leaked. Under other circumstances the cache field
points to a pre-existing credential cache that should not be destroyed.
There is nothing that indicates whether the cache should be destroyed,
so to solve this we'll add a flag to the credential structure unless you
have a better solution.
_______________________________________________
krb5-bugs mailing list
krb5-bugs@mit.edu
https://mailman.mit.edu/mailman/listinfo/krb5-bugs
