Ticket History #8538: Need a way to free KDB module e_data

Ticket 8414 unintentionally removed the ability of KDB modules to
correctly free private principal data stored in the e_data field, unless
that field consists of a single memory region which can be freed with
free().

Explicitly copy KDB vtable fields

In preparation for bumping the kdb_vftabl minor version, use explicit
field assignments when copying the module vtable to the internal copy,
so that we can conditionalize assignments for minor versions greater
than 0.

https://github.com/krb5/krb5/commit/50605efa5058583667227223a75ca44a512f4796
Author: Greg Hudson <ghudson@mit.edu>
Commit: 50605efa5058583667227223a75ca44a512f4796
Branch: master
src/lib/kdb/kdb5.c | 79 ++++++++++++++++++++++++++++++++++++++--------------
1 files changed, 58 insertions(+), 21 deletions(-)

Add free_principal_e_data KDB method

Add an optional method to kdb_vftabl to free e_data pointer in a
principal entry, in case it was populated by a module using a more
complex structure than a single memory region.

[ghudson@mit.edu: handled minor version bump; simplified code; rewrote
commit message]

(cherry picked from commit 87d8d1c6da227ff9410413de39ee64e4566429e5)

https://github.com/krb5/krb5/commit/f7b8f312f5395949a7d46e7dc36718a8a5bc6b85
Author: Andreas Schneider <asn@samba.org>
Committer: Greg Hudson <ghudson@mit.edu>
Commit: f7b8f312f5395949a7d46e7dc36718a8a5bc6b85
Branch: krb5-1.15
src/include/kdb.h | 11 +++++++++++
src/lib/kdb/kdb5.c | 14 +++++++++++++-
2 files changed, 24 insertions(+), 1 deletions(-)