MEMORY keytab does not copy keytab_entry keyblock contents
authorEzra Peisach <epeisach@mit.edu>
Sun, 4 Feb 2007 02:03:48 +0000 (02:03 +0000)
committerEzra Peisach <epeisach@mit.edu>
Sun, 4 Feb 2007 02:03:48 +0000 (02:03 +0000)
commitcbf68e7ae3bbae299793240ee3b65a45bb09f7c6
treeae6d04e353e7e5e7378bdc29f46ad09806a96174
parent1e88e68ab68e74df6b1118a74a3bdcbf0cf4a32f
MEMORY keytab does not copy keytab_entry keyblock contents

In krb5_kt_add_entry: The MEMORY keytab does not make a copy of the
keytab_entry keyblock contents - but instead retains a pointer to the
incomming one.

In krb5_kt_get_entry and krb5_kt_get_next - a pointer to internal
keyblock contents memory is returned to the caller - which is subsequently
freed when tht caller invokes krb5_free_keytab_entry_contents.

Solution is to use krb5_copy_keyblock_contents() instead of simply copying
the structure.

Ticket: new

git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@19140 dc483132-0cff-0310-8789-dd5450dbe970
src/lib/krb5/keytab/kt_memory.c