Inserting opaque data into the DB
Alejandro Perez Mendez
alex at um.es
Fri Nov 11 03:13:22 EST 2011
I already tested string attributes in KRB 1.10 alpha1 and they have
worked perfectly to my purposed. I have introduced 3K attributes
associated with principals, and extracted them later on from a authdata
plugin. As a comment, I would update the k5wiki page to reflect the
struct of krb5_string_attr, since it is not clear if the argument
"strings_out" in krb5_dbe_get_strings will be a linked list (with a
"next" field) or an array with indexed access.
> On 10/20/2011 04:42 AM, Alejandro Perez Mendez wrote:
>> I have a question related with this string attributes. Will they have a
>> maximus size of will they be unlimited?
> The total size of all string attributes on a principal entry (keys and
> values) will be limited to 64K, because of an ancient restriction that
> tl-data values are limited to 64K.
> There is no other size constraint, although the processing of string
> attributes is not intended to be efficient for large amounts of data.
> (The same is true of tl-data and of the KDB interface in general, since
> we fetch whole principal entries whenever we operate on one.)
More information about the krbdev