diff options
| author | Ezra Peisach <epeisach@mit.edu> | 2007-02-03 18:09:56 +0000 |
|---|---|---|
| committer | Ezra Peisach <epeisach@mit.edu> | 2007-02-03 18:09:56 +0000 |
| commit | 2d12564207af0aa76ecddd131cdc0530e447a915 (patch) | |
| tree | 60f2eae1a25a000d11bf3759750a8d68b54a338a /src/lib | |
| parent | 605c7645d316bb591aaad9a1911d0c3c68032272 (diff) | |
| download | krb5-2d12564207af0aa76ecddd131cdc0530e447a915.tar.gz krb5-2d12564207af0aa76ecddd131cdc0530e447a915.tar.xz krb5-2d12564207af0aa76ecddd131cdc0530e447a915.zip | |
Memory leak in new memory keytab
The memory keytab introduced in ticket 5411 suffers from a memory leak
in the Heimdal compatible kt_close() handling and thread destructor in which
the cursor->entry is not freed.
ticket: new
git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@19138 dc483132-0cff-0310-8789-dd5450dbe970
Diffstat (limited to 'src/lib')
| -rw-r--r-- | src/lib/krb5/keytab/kt_memory.c | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/lib/krb5/keytab/kt_memory.c b/src/lib/krb5/keytab/kt_memory.c index f30c7d7b5a..5e550d4929 100644 --- a/src/lib/krb5/keytab/kt_memory.c +++ b/src/lib/krb5/keytab/kt_memory.c @@ -175,6 +175,7 @@ void krb5int_mkt_finalize(void) { * krb5_context since we know that the context isn't used by
* krb5_kt_free_entry or krb5_free_principal. */
krb5_kt_free_entry(NULL, cursor->entry);
+ krb5_xfree(cursor->entry);
krb5_xfree(cursor);
}
@@ -354,6 +355,7 @@ krb5_mkt_close(krb5_context context, krb5_keytab id) next_cursor = cursor->next;
krb5_kt_free_entry(context, cursor->entry);
+ krb5_xfree(cursor->entry);
krb5_xfree(cursor);
}
|