Version consistency checks (v3.0.x and master)
a.cudbardb at freeradius.org
Thu Jan 23 18:32:00 CET 2014
On 23 Jan 2014, at 17:10, Phil Mayers <p.mayers at IMPERIAL.AC.UK> wrote:
> On 23/01/14 16:55, Arran Cudbard-Bell wrote:
>> A common issue appears to be version mismatches between FreeRADIUS
>> utilities/the server binary, it's libraries (libfreeradius-radius and
>> libfreeradius-server) and the various modules.
> And the dictionaries. Maybe a special comment:
> # dict version=x.x
> ...and check for this when reading, aborting if it's different? Probably will have to ignore w/ absent values which won't help with people using 2.x dicts against 3.x but, long term, it might.
Yes and yes. Expected version could be passed to my_dict_init which is compares against any version keywords it finds.
>> To help prevent this, all utilities and the server binary will
>> perform runtime version consistency checks against the libraries
>> they're linked to, and the modules they load.
> The answer is probably "no that's crazy" but I don't suppose ABI / symbol versioning helps here?
It should! But jlibtool needs to be updated to do it correctly. Last time I tried it didn't work on OSX, and broke the build on Linux.
It's definitely something that should be revisited.
Arran Cudbard-Bell <a.cudbardb at freeradius.org>
FreeRADIUS Development Team
FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 881 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the Freeradius-Devel