• First off, I wanted thank you for this plugin. It reduces the need for a lot of these application level based security plugins that claim to do what this actually does. It’s significantly more efficient if you know what you’re doing because you can ban people at the server level (or higher), significantly reducing the resources used.

    My question is if we could get feature that allows to define a custom ident for the openlog() to be used for the WP_FAIL2BAN_BLOCKED_USERS setting. The reason I ask this is because most of the usernames that you’re going to be putting in that constant are users that should never even be able to be used, e.g. admin|administrator|user|domain etc. People who try to login with these usernames shouldn’t be given a second chance. Since most JAIL configs might be something like

    bantime  = 3600
    findtime = 600
    maxretry = 5

    This is good for people who might legitimately forgot their password and tried multiple times. However, for those others who use those WP_FAIL2BAN_BLOCKED_USERS we could define a different set of rules that immediately and permanently bans them, as well as any other type of JAIL actions and filters. In my case, I currently ban users all the way up to my load balancer, but if someone did actually forget, I’d prefer that they have a timed ban via iptables and those WP_FAIL2BAN_BLOCKED_USERS are permanently banned via my load balancer.

    Let me know what you think, and thanks again for this plugin, love it.

    https://www.ads-software.com/plugins/wp-fail2ban/

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Custom $ident for WP_FAIL2BAN_BLOCKED_USERS’ is closed to new replies.