chore(github-actions): update super-linter/super-linter action to v8 (#557)

* chore(github-actions): update super-linter/super-linter action to v8

* rector main

Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>

---------

Signed-off-by: Jan-Otto Kröpke <mail@jkroepke.de>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Jan-Otto Kröpke <mail@jkroepke.de>

Author: renovate[bot]

.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -78,7 +78,7 @@ body:
     attributes:
       label: openvpn server logs
       description: |
-        Log of openvpn server
+        Log of OpenVPN server
       render: shell
     validations:
       required: false

.github/workflows/ci.yaml

@@ -89,7 +89,7 @@ jobs:
           fetch-depth: 0
 
       - name: Lint Code Base
-        uses: super-linter/super-linter/slim@12150456a73e248bdc94d0794898f94e23127c88 # v7.4.0
+        uses: super-linter/super-linter/slim@5119dcd8011e92182ce8219d9e9efc82f16fddb6 # v8.0.0
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           MULTI_STATUS: false

docs/Configuration.md

@@ -208,7 +208,7 @@ Usage of openvpn-auth-oauth2:
   --openvpn.common-name.mode value
     	If common names are too long, use md5/sha1 to hash them or omit to skip them. If omit, oauth2.validate.common-name does not work anymore. Values: [plain,omit] (env: CONFIG_OPENVPN_COMMON__NAME_MODE) (default plain)
   --openvpn.override-username
-    	Requires OpenVPN Server 2.7! If true, openvpn-auth-oauth2 use the override-username command to set the username in OpenVPN connection. This is useful to use real usernames in OpenVPN statistics. The username will be set after client configs are read. Read openvpn man page for limitations of the override-username. (env: CONFIG_OPENVPN_OVERRIDE__USERNAME)
+    	Requires OpenVPN Server 2.7! If true, openvpn-auth-oauth2 use the override-username command to set the username in OpenVPN connection. This is useful to use real usernames in OpenVPN statistics. The username will be set after client configs are read. Read OpenVPN man page for limitations of the override-username. (env: CONFIG_OPENVPN_OVERRIDE__USERNAME)
   --openvpn.pass-through.address value
     	The address of the pass-through socket. Must start with unix:// or tcp:// (env: CONFIG_OPENVPN_PASS__THROUGH_ADDRESS) (default unix:/run/openvpn-auth-oauth2/server.sock)
   --openvpn.pass-through.enabled
@@ -276,7 +276,7 @@ See [Filesystem Permissions](Filesystem%20Permissions) for more information.
 
 ## Setup OpenVPN server
 
-To connect openvpn-auth-oauth2 with openvpn server, add lines below:
+To connect openvpn-auth-oauth2 with OpenVPN server, add lines below:
 
 ```ini
 # openvpn server.conf

docs/FAQ.md

@@ -28,21 +28,21 @@ we encourage users to up-vote the relevant feature requests on the OpenVPN GitHu
 You can find and support these requests at the following link:
 [Feature Request on GitHub](https://github.com/OpenVPN/openvpn/issues/299)
 
-## Q: `mismatch: openvpn client is empty` / `username-as-common-name`
+## Q: `mismatch: OpenVPNclient is empty` / `username-as-common-name`
 
 A: When setting up `username-as-common-name` on the OpenVPN server, it's crucial to also configure `openvpn.common-name.environment-variable-name` to `username`.
 
 This configuration is indispensable because `username-as-common-name` functions post-authentication. Aligning the environment variable name with `username` guarantees smooth operation.
 
 On authentication, it's expected that common-name is not the values of the username. That may mis-leading, because after authentication, the common name has the correct value at OpenVPN logs.
 
-**Upstream Issue:** [OpenVPN/openvpn #498](https://github.com/OpenVPN/openvpn/issues/498#issuecomment-1939194149)
+**Upstream Issue:** [`OpenVPN/openvpn` #498](https://github.com/OpenVPN/openvpn/issues/498#issuecomment-1939194149)
 
 ## Q: Options error: No client-side authentication method is specified.
 
 A: Although openvpn-auth-oauth2 theoretically doesn't require client-side authentication, the OpenVPN client expects it.
 
-**Upstream Issue:** [OpenVPN/openvpn #501](https://github.com/OpenVPN/openvpn/issues/501) (Please react with :+1: if you're affected.)
+**Upstream Issue:** [`OpenVPN/openvpn` #501](https://github.com/OpenVPN/openvpn/issues/501) (Please react with :+1: if you're affected.)
 
 **Potential Workarounds:**
 

docs/Filesystem Permissions.md

@@ -1,11 +1,12 @@
 # Filesystem Permissions
 
-When started by systemd, openvpn runs with a [dynamic arbitrary UID](https://0pointer.net/blog/dynamic-users-with-systemd.html).
+When started by systemd,
+OpenVPN runs with a [dynamic arbitrary UID](https://0pointer.net/blog/dynamic-users-with-systemd.html).
 This means that it may not have access to certain files and directories if the appropriate permissions are not set.
 
 Any additional files, such as TLS keys, should reside in the `/etc/openvpn-auth-oauth2/` directory.
 The ownership of these files should be set to `root`, and the group should be set to `openvpn-auth-oauth2`.
-This setup ensures that openvpn has the necessary permissions to access and utilize these files.
+This setup ensures that OpenVPN has the necessary permissions to access and use these files.
 
 When installing the openvpn-auth-oauth2 Linux package, the system automatically creates the openvpn-auth-oauth2 group.
 This group manages access to the necessary files and directories

docs/HTTPS Listener.md

@@ -68,7 +68,7 @@ You need to install `certbot` and suitable for you `DNS plugin`. More informatio
 
 You can create certs with command below and than copy them to `/etc/openvpn-auth-oauth2/` directory or create a link to files. Do not forget to set right permissions.
 
-The command below uses certbot to create a free SSL certificate for a domain hosted on cloudflare.
+The command below uses certbot to create a free SSL certificate for a domain hosted on Cloudflare.
 
 ```bash
 certbot certonly --noninteractive --verbose \

docs/Installation.md

@@ -49,7 +49,7 @@ Replace `<package_file>` with the name of the downloaded file.
 ## Manual Installation
 
 If you prefer to build the binary yourself, follow these steps:
-1. Ensure you have [golang](https://go.dev/doc/install) and Make installed on your system.
+1. Ensure you have [Go](https://go.dev/doc/install) and Make installed on your system.
 2. Download the source code from our [releases page](https://github.com/jkroepke/openvpn-auth-oauth2/releases/latest).
 3. Open a terminal.
 4. Navigate to the directory where you downloaded the source code.

docs/Providers.md

@@ -83,9 +83,9 @@ To require multiple groups, define `CONFIG_OAUTH2_VALIDATE_GROUPS`.
 <details>
 <summary>Expand</summary>
 
-### Register an app on google cloud console
+### Register an app on Google Cloud Console
 
-1. Login as admin into your [Google console](https://console.cloud.google.com/).
+1. Login as admin into your [Google Cloud Console](https://console.cloud.google.com/).
 2. In the project Dashboard center pane, choose **"APIs & Services"**.
 3. If necessary, complete the `OAuth consent screen` wizard. You will probably want to create an `Internal` application.
     * If you reuse an existing application, your users may already have given consent for the usage of this application,

internal/config/flags.go

@@ -181,7 +181,7 @@ func (c *Config) flagSetOpenVPN(flagSet *flag.FlagSet) {
 		"Requires OpenVPN Server 2.7! "+
 			"If true, openvpn-auth-oauth2 use the override-username command to set the username in OpenVPN connection. "+
 			"This is useful to use real usernames in OpenVPN statistics. The username will be set after client configs are read. "+
-			"Read openvpn man page for limitations of the override-username.",
+			"Read OpenVPN man page for limitations of the override-username.",
 	)
 	flagSet.BoolVar(
 		&c.OpenVPN.Passthrough.Enabled,