Michael Richardson <[EMAIL PROTECTED]> wrote: > A problem with the method that I did is that the concatenation of > the EAP-Messages may be bigger than MAX_STRING_LEN. Aside from just > making MAX_STRING_LEN bigger, is there any other thoughts?
I had thought of dynamically allocating the memory for strvalue(), but I hadn't done anything about it. It's one reason I hadn't yet done something like add an attribute 'EAP-TLS-Packet', as they can be ~16K. Maybe a new type PW_TYPE_DYNAMIC_STRING, which is identical to 'string', but which is dynamically allocated. But it would still have 'strvalue[MAX_STRING_LEN]' in the struct, which sucks. > I'd hate to go to external storage for an attribute due to the complexity > of making sure all the allocation/deallocations are done right. Nah. src/lib/valuepair.c All VALUE_PAIR's are freed ONLY in pairfree(). Hack that, and it should be OK. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
