Right, thank you, that clarifies it. I suspected that was the case indeed.
The "persist.data" file is totally a cake to grasp, since it's kinda written in the same easily-readable format that "abyss.conf" uses.
I thought about trying <range> or <iprange> tags, but didn't really count on those being actually implemented.
How do I get in touch with you? Emailing at
support@aprelium.com?
I'd actually LOVE to see an interface option in the Antihacking Protection section, offering to manually input IPs/ranges for use by the protection module. Main reason is - it handles the blacklisted connections differently than the graceful 403s of the Allowed/Denied section, dropping the connection immediately, and not wasting server resources on actually honoring the request by serving a "Forbidden" page. Also, a lot of attackers can easily be identified manually by a vigilant observer, and might be missed by an automated module - therefore we need the option to manually pinpoint ban targets for the protection.
Once the perpetrator sees the "Forbidden" page, they will actually know that they've been blacklisted. Security through obscurity is something I really like, and I do consider the Antihacking protection method of handling the connections a lot more effective in fending off those pesky attackers.
I mean - if you cannot even connect, what can you do? Plus, when the connection is simply dropped, the attacker will not have a clear idea as to why this is happening, and therefore will be less likely to implement proper counteracting measures to try and circumvent the ban.