Phil Mayers wrote:
For any specific reason? I don't care one way or the other, just curious.
The extended attributes. They're fairly weird. It is useful to have just *one* way to parse unknown attributes. The new OID format is general, simple, and works.
If you have third-party tools which read the detail files, fix them to use libfreeradius-radius. That will parse the attributes correctly.
One thing worth bearing in mind is that many (most?) detail parsers I've seen are not written in "C". This is perfectly reasonable given the use-case, and calling into libfreeradius-radius from those tools is likely prohibitively complex.
Well.... they're going to have to be updated to understand the new extended attributes.
It's probably not an issue in practice of course, since these are *unknown* attributes; I suspect if people care about them, they'll be defined in dictionaries.
Yup. Alan DeKok.