Problem/Motivation
Sometimes we want to have a more persistent ban alongside the less permanent ones.
Steps to reproduce
Proposed resolution
Add a new button with callback to "Ban indefinitely". The actual ban period is limited to the year 2038 because of the storage limitations, but it should suffice.
Remaining tasks
Discuss proposed solution.
User interface changes
API changes
Data model changes
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | auto_unban-add-longer-ban-time-3395292-4.patch | 2.77 KB | primsi |
| #4 | auto_unban-add-longer-ban-time-3395292-4.interdiff.txt | 2.96 KB | primsi |
| #2 | auto_unban-add-longer-ban-time-3395292-2.patch | 3.31 KB | primsi |
Comments
Comment #2
primsi commentedInitial patch.
Comment #3
berdirI think if we go with a separate submit button then a new method that's banIpIndefinitely() or banIpWithExpire() makes more sense, we don't need to introduce state in the storage then.
Comment #4
primsi commentedThanks. Seems it's fine even with just a new argument (that's what the module is doing anyway with $attempts).
Comment #5
primsi commentedFew notes for the maintainer:
I aliased this for a bit better code clarity, because the replacement class auto_unban provides has the same name as the one that it substitutes.
We discussed with @Berdir, that just Count is a bit confusing. So we are proposing here a small renaming. Sorry for the scope creep.
Comment #6
berdirComment #7
andybroomfieldHave tested this and selecting add indefinatly does ban the IP address with a date set to 2038 (max unix time stamp).
Comment #9
douggreen commentedCommitted, I wasn't initially a fan of this, but as an option it's certainly valuable.
Comment #10
douggreen commented