problem with rlm_dbm_parser and DEFAULT Realms
Seamus Bridgeman
seamusb114 at gmail.com
Tue Apr 7 15:34:16 CEST 2009
Id really appreciate anyone could clarify if they are indeed using DBM files
with multiple DEFAULT user profiles and/or user profiles with duplicate
usernames. From my tests and cursory look at code (especially
rlm_dbm_parser), it seems the key is based solely on username which wont
work for multiple 'DEFAULT' usernames or duplicate usernames. As the
key-value pair will be overwritten and this is what I see. Only the last
DEFAULT Realm=xxx record exists in the DBM file.
Other/Earlier Radius implementations used a combination of username and
incremental counter to support ordered duplicate usernames.So multiple
DEFAULTS would be read in as DEFAULT, DEFAULT\n00, DEFAULT\n01 ...when
creating the DBM file and equally duplicate username matches would be
returned by adding the same incremental counter when fetching .
This is causing an issue for us as we cant migrate from this earlier Radius
to Freeradius2.1.3
Could I also ask if anyone is explicltiy using DEFAULT Realm = xxx records
in the DBM file and also if they are using
regexp matches successfully (e.g DEFAULT Realm =~ "*.domain) as the
rlm_dbm_parser is not matching this and
records Realm as "" (bombs out on *). I know there is a regexp fix in 2.1.4
but not sure if this also applies to rlm_dbm_parser.
thanks in anticipation/desperation !
Seamus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20090407/5ad6fc15/attachment.html>
More information about the Freeradius-Users
mailing list