From: Greg Hudson <ghudson@mit.edu>
Date: Mon, 20 Jun 2011 16:49:00 +0000 (+0000)
Subject: Document that e_data can be used by KDB modules internally
X-Git-Tag: krb5-1.10-alpha1~401
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=9fa2d9e9bc42303b1793beb6ff38408c5c4ce904;p=krb5.git

Document that e_data can be used by KDB modules internally

git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@24972 dc483132-0cff-0310-8789-dd5450dbe970
---

diff --git a/src/include/kdb.h b/src/include/kdb.h
index d58178801..93242ef87 100644
--- a/src/include/kdb.h
+++ b/src/include/kdb.h
@@ -166,6 +166,15 @@ typedef struct _krb5_keysalt {
     krb5_data             data;                 /* Length, data */
 } krb5_keysalt;
 
+/*
+ * A principal database entry.  Extensions to this structure currently use the
+ * tl_data list.  The e_data and e_length fields are not used by any calling
+ * code except kdb5_util dump and load, which marshal and unmarshal the array
+ * in the dump record.  KDB modules may use these fields internally as long as
+ * they set e_length appropriately (non-zero if the data should be marshalled
+ * across dump and load, zero if not) and handle null e_data values in
+ * caller-constructed principal entries.
+ */
 typedef struct _krb5_db_entry_new {
     krb5_magic            magic;                /* NOT saved */
     krb5_ui_2             len;