Commit 06448a3d authored by Jonathan's avatar Jonathan Committed by GitHub
Browse files

Merge pull request #45 from sts/fix_escapes_radiusd_conf

Add correct_escapes=true to radiusd.conf
parents f41cc1e6 b1d53c73
...@@ -14,6 +14,7 @@ class freeradius ( ...@@ -14,6 +14,7 @@ class freeradius (
$syslog = false, $syslog = false,
$log_auth = 'no', $log_auth = 'no',
$preserve_mods = true, $preserve_mods = true,
$correct_escapes = true,
) inherits freeradius::params { ) inherits freeradius::params {
validate_re($freeradius::fr_version, '^3', 'This module is only compatible with FreeRADIUS 3') validate_re($freeradius::fr_version, '^3', 'This module is only compatible with FreeRADIUS 3')
......
...@@ -117,6 +117,27 @@ libdir = <%= @fr_libdir %> ...@@ -117,6 +117,27 @@ libdir = <%= @fr_libdir %>
# #
pidfile = ${run_dir}/${name}.pid pidfile = ${run_dir}/${name}.pid
#
# 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 = <%= @correct_escapes %>
# panic_action: Command to execute if the server dies unexpectedly. # panic_action: Command to execute if the server dies unexpectedly.
# #
# FOR PRODUCTION SYSTEMS, ACTIONS SHOULD ALWAYS EXIT. # FOR PRODUCTION SYSTEMS, ACTIONS SHOULD ALWAYS EXIT.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment