mirror of
https://github.com/nextcloud/server.git
synced 2026-05-28 04:32:30 -04:00
in text: "bruteforce" > "brute force"
In description text we should use correct spelling which is "brute force" or "brute-force", not "bruteforce". In other parts of the documentation, "brute force" is used: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/bruteforce_configuration.html See also https://en.wikipedia.org/wiki/Brute-force_attack Signed-off-by: Alexander Müller <28591861+alexanderdd@users.noreply.github.com>
This commit is contained in:
parent
a23d8b2778
commit
2f89a732fe
1 changed files with 3 additions and 3 deletions
|
|
@ -368,7 +368,7 @@ $CONFIG = [
|
|||
'token_auth_activity_update' => 60,
|
||||
|
||||
/**
|
||||
* Whether the bruteforce protection shipped with Nextcloud should be enabled or not.
|
||||
* Whether the brute force protection shipped with Nextcloud should be enabled or not.
|
||||
*
|
||||
* Disabling this is discouraged for security reasons.
|
||||
*
|
||||
|
|
@ -377,9 +377,9 @@ $CONFIG = [
|
|||
'auth.bruteforce.protection.enabled' => true,
|
||||
|
||||
/**
|
||||
* Whether the bruteforce protection shipped with Nextcloud should be set to testing mode.
|
||||
* Whether the brute force protection shipped with Nextcloud should be set to testing mode.
|
||||
*
|
||||
* In testing mode bruteforce attempts are still recorded, but the requests do
|
||||
* In testing mode brute force attempts are still recorded, but the requests do
|
||||
* not sleep/wait for the specified time. They will still abort with
|
||||
* "429 Too Many Requests" when the maximum delay is reached.
|
||||
* Enabling this is discouraged for security reasons
|
||||
|
|
|
|||
Loading…
Reference in a new issue