From 5be643b8dfb2a19eda024c44d132a313ea7d8eb1 Mon Sep 17 00:00:00 2001 From: "Alan T. DeKok" Date: Sat, 7 Aug 2021 12:12:36 -0400 Subject: [PATCH] minor word smithing --- raddb/proxy.conf | 10 +++------- raddb/radiusd.conf.in | 42 ++++++++++-------------------------------- 2 files changed, 13 insertions(+), 39 deletions(-) diff --git a/raddb/proxy.conf b/raddb/proxy.conf index 7f5ff2e152..c03dad3874 100644 --- a/raddb/proxy.conf +++ b/raddb/proxy.conf @@ -693,10 +693,9 @@ realm example.com { auth_pool = my_auth_failover # acct_pool = acct - # As of Version 3.0, the server can proxy CoA packets - # based on the Operator-Name attribute. This requires - # that the "suffix" module be listed in the "recv-coa" - # section. + # The server can proxy CoA packets based on the Operator-Name + # attribute. This requires that the "suffix" module be + # listed in the "recv-coa" section. # # See raddb/sites-available/coa # @@ -819,9 +818,6 @@ realm LOCAL { # Yes, this rule is different than the normal "unlang" rules for # regular expressions. That may be fixed in a future release. # -# - for version 3.0.4 and following, with "correct_escapes = true", -# use normal regex backslash rules. Just one. Not two. -# # - If you are matching domain names, put a '$' at the end of the regex # that matches the domain name. This tells the regex matching code # that the realm ENDS with the domain name, so it does not match diff --git a/raddb/radiusd.conf.in b/raddb/radiusd.conf.in index 7d7b0c0127..79603c9002 100644 --- a/raddb/radiusd.conf.in +++ b/raddb/radiusd.conf.in @@ -148,27 +148,6 @@ libdir = @libdir@ # 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 = true - # panic_action: Command to execute if the server dies unexpectedly. # # FOR PRODUCTION SYSTEMS, ACTIONS SHOULD ALWAYS EXIT. @@ -568,8 +547,7 @@ security { # rejects will be sent at 'cleanup_delay' time, when the request # is deleted from the internal cache of requests. # - # As of Version 3.0.5, "reject_delay" has sub-second resolution. - # e.g. "reject_delay = 1.4" seconds is possible. + # This number can be a decimal, e.g. 3.4 # # Useful ranges: 1 to 5 reject_delay = 1 @@ -784,19 +762,19 @@ modules { # directory from start to finish. Which means that the # modules are read off of disk randomly. # - # As of 3.0.18, you can list individual modules *before* the - # directory inclusion. Those modules will be loaded first. - # Then, when the directory is read, those modules will be - # skipped and not read twice. + # You can list individual modules *before* the directory + # inclusion. Those modules will be loaded first. Then, when + # the directory is read, those modules will be skipped and + # not read twice. # # $INCLUDE mods-enabled/sql # - # As of 3.0, modules are in mods-enabled/. Files matching - # the regex /[a-zA-Z0-9_.]+/ are loaded. The modules are - # initialized ONLY if they are referenced in a processing - # section, such as authorize, authenticate, accounting, - # pre/post-proxy, etc. + # All modules are in ther mods-enabled/ directory. Files + # matching the regex /[a-zA-Z0-9_.]+/ are read. The + # modules are initialized ONLY if they are referenced in a + # processing section, such as authorize, authenticate, + # accounting, pre/post-proxy, etc. # $INCLUDE mods-enabled/ } -- 2.47.2