Change between FreeRadius 2.2.5 to 3.0.17 in Filter ?

Olivier CALVANO o.calvano at gmail.com
Tue Jun 23 08:03:05 CEST 2020


In radius.conf ?

i have:

#
#  correct_escapes: use correct backslash escaping
#
#  Prior to version 3.0.5, the handling of backslashes was a little
#  awkward, i.e. "wrong".  In some cases, to get one backslash into
#  a regex, you had to put 4 in the config files.
#
#  Version 3.0.5 fixes that.  However, for backwards compatibility,
#  the new method of escaping is DISABLED BY DEFAULT.  This means
#  that upgrading to 3.0.5 won't break your configuration.
#
#  If you don't have double backslashes (i.e. \\) in your configuration,
#  this won't matter to you.  If you do have them, fix that to use only
#  one backslash, and then set "correct_escapes = true".
#
#  You can check for this by doing:
#
#       $ grep '\\\\' $(find raddb -type f -print)
#
correct_escapes = true


Le lun. 22 juin 2020 à 15:02, Alan Buxey <alan.buxey at gmail.com> a écrit :

> hi,
>
> have you chosen the correct backslashes option in the main config file?
>
> alan
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html


More information about the Freeradius-Users mailing list