From: Nick Porter Date: Fri, 22 Nov 2024 08:19:54 +0000 (+0000) Subject: Use v4 section names X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=942c3f8dcd15027c5f3d8fcba6de296fa5a5f1f1;p=thirdparty%2Ffreeradius-server.git Use v4 section names --- diff --git a/raddb/policy.d/canonicalisation b/raddb/policy.d/canonicalisation index 7d0596d2f36..ae6955797e7 100644 --- a/raddb/policy.d/canonicalisation +++ b/raddb/policy.d/canonicalisation @@ -44,8 +44,8 @@ split_username_nai { mac-addr-regexp = '([0-9a-f]{2})[^0-9a-f]?([0-9a-f]{2})[^0-9a-f]?([0-9a-f]{2})[^0-9a-f]?([0-9a-f]{2})[^0-9a-f]?([0-9a-f]{2})[^0-9a-f]?([0-9a-f]{2})' # -# Add "rewrite_called_station_id" in the "authorize" and -# "preacct" sections. +# Add "rewrite_called_station_id" in the "recv Access-Request" and +# "recv Accounting-Request" sections. # # Makes Called-Station-ID conform to what RFC3580 says should # be provided by 802.1X authenticators. @@ -66,8 +66,8 @@ rewrite_called_station_id { } # -# Add "rewrite_calling_station_id" in the "authorize" and -# "preacct" sections. +# Add "rewrite_calling_station_id" in the "recv Access-Request" and +# "recv Accounting-Request" sections. # # Makes Calling-Station-ID conform to what RFC3580 says should # be provided by 802.1X authenticators. diff --git a/raddb/policy.d/eap b/raddb/policy.d/eap index 0800c0f72b7..4c2978624ea 100644 --- a/raddb/policy.d/eap +++ b/raddb/policy.d/eap @@ -40,7 +40,7 @@ Xeap.authenticate { # # Forbid all EAP types. Enable this by putting "forbid_eap" -# into the "authorize" section. +# into the "recv Access-Request" section. # forbid_eap { if (&EAP-Message) { diff --git a/raddb/policy.d/operator-name b/raddb/policy.d/operator-name index 9cba1a86dd0..467d770f14a 100644 --- a/raddb/policy.d/operator-name +++ b/raddb/policy.d/operator-name @@ -8,12 +8,12 @@ # If you require that the Operator-Name be set # for local clients then call the 'operator-name' policy -# in the authorize section of the virtual-server for your clients in clients.conf +# in the "recv Access-Request" section of the virtual-server for your clients in clients.conf # To inject an Operator-Name whilst proxying, call the # 'operator-name' policy in the pre-proxy section of the virtual server # No need to call this if you have already enabled this in -# the authorize section. +# the "recv Access-Request" section. # # We assume that clients can have the operator-name definition diff --git a/raddb/sites-available/channel_bindings b/raddb/sites-available/channel_bindings index 967ab31cdfd..05df4dd4ad2 100644 --- a/raddb/sites-available/channel_bindings +++ b/raddb/sites-available/channel_bindings @@ -5,7 +5,7 @@ # server channel_bindings { # - # Only the "authorize" section is needed. + # Only the "recv Access-Request" section is needed. # recv Access-Request { # In general this section should include a policy for each type diff --git a/raddb/sites-available/example b/raddb/sites-available/example index ec4d4d1e9bf..528481addde 100644 --- a/raddb/sites-available/example +++ b/raddb/sites-available/example @@ -56,7 +56,7 @@ server example { # Listen on 192.0.2.1:1812 for Access-Requests # # When the server receives a packet, it is processed - # through the "authorize", etc. sections listed here, + # through the "recv ...", etc. sections listed here, # NOT the global ones the "default" site. # listen { diff --git a/raddb/sites-available/inner-tunnel b/raddb/sites-available/inner-tunnel index a586c423be0..ae7d1f78eaf 100644 --- a/raddb/sites-available/inner-tunnel +++ b/raddb/sites-available/inner-tunnel @@ -159,7 +159,7 @@ recv Access-Request { # # This section lists which modules are available for authentication. # Note that it does NOT mean 'try each module in order'. It means -# that a module from the 'authorize' section adds a configuration +# that a module from the 'recv Access-Request' section adds a configuration # attribute 'Auth-Type := ::FOO'. That authentication type is then # used to pick the appropriate module from the list below. # @@ -177,7 +177,7 @@ recv Access-Request { # # PAP authentication, when a back-end database listed -# in the 'authorize' section supplies a password. The +# in the 'recv Access-Request' section supplies a password. The # password can be clear-text, or encrypted. authenticate pap { pap @@ -185,7 +185,7 @@ authenticate pap { # # Most people want CHAP authentication -# A back-end database listed in the 'authorize' section +# A back-end database listed in the 'recv Access-Request' section # MUST supply a CLEAR TEXT password. Encrypted passwords # won't work. authenticate chap { diff --git a/raddb/sites-available/resource-check b/raddb/sites-available/resource-check index cf4b08687f0..aa7a3d697ae 100644 --- a/raddb/sites-available/resource-check +++ b/raddb/sites-available/resource-check @@ -16,7 +16,7 @@ # system status this virtual server is able to manipulate the outcome of the # controlled virtual server. # -# Firstly, the authorize section of this virtual server will need to be +# Firstly, the "recv Status-Server" section of this virtual server will need to be # amended to check the status of the external resources and to set the status # of the control module appropriately, as described in the inline comments # below...