On Fri, Apr 30, 2010 at 05:02:48PM -0400, Huckle Berry wrote:
Ah, but you got too much. Now you have Perl, Python, the SSL library and all those other things with a newer version than those in karmic.
I don't see how having newer versions of perl/python could be an issue. As far as SSL is concerned, see below, as this server will be wiped soon.
Practically any package could need security updates in the future. For reference, http://security-tracker.debian.org/tracker/source-package/perl http://security-tracker.debian.org/tracker/source-package/python2.5
I have a feeling that this server will eventually be wiped anyway, it's more of an experiment right now than anything.
OK, then you should be reasonably safe. Just remember not to do this in production. :)
Initial tests using radtest showed positive results, however even after reinstalling with libmysqlclient-dev, freeradius still fails to start with the error
/etc/freeradius/sites-enabled/default[159]: Failed to find module "sql". /etc/freeradius/sites-enabled/default[62]: Errors parsing authorize section.
Which may or may not be related to the versions of the installed packages and the configuration script's ability to determine what is and is not installed. I'm assuming at this point that the difference between freeradius with sql and w/o sql is determined by whether certian header packages are installed on the system at the time freeradius is complied?
No, assuming you installed a freeradius-*sql package you want, this is simply a configuration issue - you need to define a sql module, which is usually done by adding $INCLUDE sql.conf to the modules section of the configuration, which is done for example by adding an /etc/freeradius/modules/local-sql.conf file with something like that inside. -- 2. That which causes joy or happiness.