Re: get_field_str() and interpret_field() bug with multi-word fields

Steve Grubb wrote: This is another band-aid compounding the problem by entrenching the hack further into more code which will then have to be modified when a correct solution is finally put into place. Providing an encoder entry point for code which generates audit key/value pairs does not fix the ambiguous parsing problem. During parsing one still has to know a priori which field names in which records are candidates for the hack, it is impossible to correctly parse otherwise. It also does not address the problem that decoding the hex value is only performed by "interpret", which is also the wrong location, it needs to be done during parsing and the field value needs to be returned with the string restored to it's correct value prior to transport encoding. So many people have complained about this; I do not understand the resistance to fixing it. The argument it would break something which is broken to begin with does not seem like a reasonable justification to me. The sooner it's fixed the better IMHO. -- John Dennis <jdennis(a)redhat.com&gt;