[1341] in Kerberos_V5_Development
Re: kadm5 api, krb5_tl_data, type number assignment
daemon@ATHENA.MIT.EDU (Barry Jaspan)
Thu Jun 20 12:21:36 1996
Date: Thu, 20 Jun 1996 12:21:31 -0400
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: tytso@MIT.EDU
Cc: krbdev@MIT.EDU
In-Reply-To: <9606200215.AA08047@dcl.MIT.EDU> (tytso@MIT.EDU)
I'd suggest dumping [the krb5_tl_data stuff] in in libkrb5util.
I'm a bit concerned that libkrb5util is
turning into a dumping ground, but libkrb5 doesn't seem to be the right
place for it, either.
I don't understand the motivation for libkrb5util at all. Adding
extra functions to a library does not increase executable size unless
the functions are actually used. Moving functions from libkrb5 to
libkrb5util does not save disk space, either, since the .o files still
exist, just in a different place. The only argument I can see behind
libkrb5util is to save time running ar and ranlib, but that is a
pretty thin excuse given that it will confuse users to have to link
against Yet Another Library.
Can someone explain why libkrb5util exists?
On a separate but related topic, Marc has made the following
suggestion for the name space of krb5_tl_data tl_data_type values:
0 <= x < 256 reserved for internal use MIT
256 <= x < 32768 should only be used if registered with MIT
32768 <= x < 65536 application-defined
Applicaiton-defined makes no sense; I assume you mean "site-defined"?
"Application-defined" means that an application client and/or server
simply chooses a constant value for the krb5_tl_data type to use, with
no guarantees that it will not conflict with other application-defined
values. Any decent implementation would allow for the value to be
configurable, probably through krb5.conf... which I guess means that
applicatin-defined and site-defined are sorta the same thing in this
case, yes. :-)
Barry
