[1229] in Kerberos_V5_Development
Re: tl_data, e_data, and kadm5
daemon@ATHENA.MIT.EDU (Christopher Provenzano)
Thu May 23 23:09:03 1996
Reply-To: proven@cygnus.com
To: "Barry Jaspan" <bjaspan@MIT.EDU>
Cc: krbdev@MIT.EDU
In-Reply-To: Your message of "Thu, 23 May 1996 12:24:10 EDT."
<9605231624.AA02903@beeblebrox.MIT.EDU>
Date: Thu, 23 May 1996 23:06:06 -0400
From: Christopher Provenzano <proven@proven.org>
My only objection is that you are using a krb5_tl_data structure data type
that will never be stored in the actual database. Since you have a mapping
of your principal type to some combination of the krb5_db_entry and
krb5_tl_data data types, you should create a new type/length data type
(call it krb5_barry_tl_data) that goes with your principal data type.
This way we keep the krb5_db_entry and krb5_tl_data at one level and
your principal data type with its krb5_barry_tl_data at another level.
CAP
