From: Nick Porter Date: Mon, 8 Aug 2022 16:50:20 +0000 (+0100) Subject: Replace v3.0 with v3.2 in docs where appropriate X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=27205443b321400414982869a391d0cc5f4de71c;p=thirdparty%2Ffreeradius-server.git Replace v3.0 with v3.2 in docs where appropriate --- diff --git a/doc/antora/modules/howto/pages/modules/ldap/authorization/user_account_controls.adoc b/doc/antora/modules/howto/pages/modules/ldap/authorization/user_account_controls.adoc index cf4ea27740b..1034481cd02 100644 --- a/doc/antora/modules/howto/pages/modules/ldap/authorization/user_account_controls.adoc +++ b/doc/antora/modules/howto/pages/modules/ldap/authorization/user_account_controls.adoc @@ -33,7 +33,7 @@ is enabled, or disabled, depending on the value of `user.access_positive`. | `user.access_positive = no` | `locked out` | `ok` | `ok` |=== -When a user is "locked out", the LDAP module will return `disallow` in (≥ v4.0.x) and `userlock` in (≤ v3.0.x). +When a user is "locked out", the LDAP module will return `disallow` in (≥ v4.0.x) and `userlock` in (≤ v3.2.x). === Editing mods-available/ldap to only allow access if the 'Access Attribute' is present diff --git a/doc/antora/modules/howto/pages/modules/ldap/base_configuration/index.adoc b/doc/antora/modules/howto/pages/modules/ldap/base_configuration/index.adoc index 0e004571a63..47f7a7f30ce 100644 --- a/doc/antora/modules/howto/pages/modules/ldap/base_configuration/index.adoc +++ b/doc/antora/modules/howto/pages/modules/ldap/base_configuration/index.adoc @@ -86,7 +86,7 @@ function(s) it's performing. For simple authentication types like `PAP` and `CHAP` the LDAP module should be listed in the `recv Access-Request { ... }` (≥ v4.0.x) -or `authorize { ... }` (≤ v3.0.x) section of the virtual server +or `authorize { ... }` (≤ v3.2.x) section of the virtual server listening on the network (usually found in `sites-available/default`). For EAP authentication the LDAP module should be listed in @@ -140,7 +140,7 @@ and authentication protocols. LDAP binds for simple authentication types like `PAP` the LDAP module should be listed in the `recv Access-Request { ... }` and `authenticate ldap { ... }` (≥ -v4.0.x) or `authorize { ... }` and `authenticate { ... }` (≤ v3.0.x) sections of +v4.0.x) or `authorize { ... }` and `authenticate { ... }` (≤ v3.2.x) sections of the virtual server listening on the network (usually found in `sites-available/default`). diff --git a/doc/antora/modules/howto/pages/modules/rest/configuration.adoc b/doc/antora/modules/howto/pages/modules/rest/configuration.adoc index 6175c7181c9..f9623265b72 100644 --- a/doc/antora/modules/howto/pages/modules/rest/configuration.adoc +++ b/doc/antora/modules/howto/pages/modules/rest/configuration.adoc @@ -34,7 +34,7 @@ cd raddb/mods-enabled && ln -s ../mods-available/rest The REST module allows a different REST API endpoint to be configured for each type of section it can be called in. -If called in `recv Access-Request` (≥ v4.0.x) or `authorize { ... }` (≤ v3.0.x) +If called in `recv Access-Request` (≥ v4.0.x) or `authorize { ... }` (≤ v3.2.x) the `rest.authorize` module section will be evaluated. [source,config] @@ -63,7 +63,7 @@ rest { <1> The URL to authenticate against. Will be expanded (if required). <2> The HTTP 'verb' to use. -If called in `recv Accounting-Request` (≥ v4.0.x) or `accounting { ... }` (≤ v3.0.x) +If called in `recv Accounting-Request` (≥ v4.0.x) or `accounting { ... }` (≤ v3.2.x) the `rest.authorize` mould section will be evaluated. [source,config] diff --git a/doc/antora/modules/installation/pages/index.adoc b/doc/antora/modules/installation/pages/index.adoc index 6b464819b9d..01de0e8b828 100644 --- a/doc/antora/modules/installation/pages/index.adoc +++ b/doc/antora/modules/installation/pages/index.adoc @@ -29,6 +29,6 @@ sought. If this describes you, then version 4 is for you! (But don't come complaining if it breaks.) Hopefully it is clear, *we recommend 99.9%+ of users use -https://freeradius.org/releases/[FreeRADIUS 3.0.x]* and the +https://freeradius.org/releases/[FreeRADIUS 3.2.x]* and the https://packages.networkradius.com/[pre-built packages] available from https://networkradius.com/[Network RADIUS]. diff --git a/doc/antora/modules/reference/partials/rcode_table.adoc b/doc/antora/modules/reference/partials/rcode_table.adoc index e114e745078..cf8bc5a1498 100644 --- a/doc/antora/modules/reference/partials/rcode_table.adoc +++ b/doc/antora/modules/reference/partials/rcode_table.adoc @@ -33,7 +33,7 @@ [NOTE] ==== -In versions ≤ v3.0.x the `disallow` rcode was called `userlock`. `disallow` and +In versions ≤ v3.2.x the `disallow` rcode was called `userlock`. `disallow` and `userlock` have an identical meaning. `disallow` will be returned in any -instance where `userlock` was returned in v3.0.x +instance where `userlock` was returned in v3.0.x or v3.2.x ==== diff --git a/doc/antora/modules/tutorials/pages/variables.adoc b/doc/antora/modules/tutorials/pages/variables.adoc index 7c0013dbdc5..250dbc2a871 100644 --- a/doc/antora/modules/tutorials/pages/variables.adoc +++ b/doc/antora/modules/tutorials/pages/variables.adoc @@ -61,7 +61,7 @@ ensure it is uncommented in the `accounting {}` section of the `raddb/sites-available/default` virtual server. Now read the -https://github.com/FreeRADIUS/freeradius-server/blob/v3.0.x/doc/configuration/variables.rst[variables] +https://github.com/FreeRADIUS/freeradius-server/blob/v3.2.x/doc/configuration/variables.rst[variables] documentation file to determine the meaning of the variables used in the `filename` configuration entry. Once you are done, send the server an accounting packet (e.g., `bob-acct-stop.sh`), and go look for the detail file, which will be diff --git a/doc/antora/modules/tutorials/partials/unlang_start.adoc b/doc/antora/modules/tutorials/partials/unlang_start.adoc index 73f3034cd62..366073970d4 100644 --- a/doc/antora/modules/tutorials/partials/unlang_start.adoc +++ b/doc/antora/modules/tutorials/partials/unlang_start.adoc @@ -1,6 +1,6 @@ [TIP] ==== For this tutorial you should start with an empty authorization section -(`recv Access-Request { ... }` or in ≤ v3.0.x `authorize { ... }`) +(`recv Access-Request { ... }` or in ≤ v3.2.x `authorize { ... }`) in the virtual server you're using to process requests. ====