Version consistency checks (v3.0.x and master)
a.cudbardb at freeradius.org
Thu Jan 23 17:55:41 CET 2014
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.
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.
Consistency checks will be based on a magic number.
Each alpha numeric char in the following format strings represents one byte.
For released versions the magic number will consist of:
Where <ma><mi><ic> are the major, minor, and incremental versions encoded in such a way that they appear as base 10 if the magic number is printed as hex.
For development versions the magic number will consist of:
Where commith is the shortened GIT commit hash, which will be updated each time configure is run.
If the magic numbers for any components do not match, the server, and utilities, will exit with an error code.
If you maintain closed source modules, you will need to rebuild them whenever you update the server binaries and libraries.
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