Skip to content

Conversation

@iharthi
Copy link
Collaborator

@iharthi iharthi commented Nov 15, 2016

Changed maximum lockdown time (config key 'auth.bruteforcingProtectMaxTime', default 5 minutes) instead of max integer value.

Made BruteforceProtection abstract, and it is now possible to use classic and new simple bruteforce protection methods. (config key 'bruteforcingProtectClass', default 'ClassicBruteforceProtection')

Only changes to old/Classic bruteforce protection method is adding MaxTime.

SimpleBruteforceProtection method also has minimum lockdown time (config key 'auth.bruteforcingProtectMinTime', default 10 seconds) and a changed logic: once lockdown is complete, the entry is erased; next time bruteforce attempt is suspected the counter restarts with minimum time.

…eforce protection method using 'auth.bruteforcingProtectClass' config key (which should be a class name, default to net.rujel.auth.ClassicBruteforceProtection)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant