• Resolved Ovidiu

    (@ovidiu)


    WP_FAIL2BAN_PROXIES

    To list all of CloudFlare’s IPs, (se https://www.cloudflare.com/ips )would that look like this:

    define('WP_FAIL2BAN_PROXIES','199.27.128.0/21','173.245.48.0/20','103.21.244.0/22','103.22.200.0/22','103.31.4.0/22','141.101.64.0/18','108.162.192.0/18','190.93.240.0/20','188.114.96.0/20','197.234.240.0/22','198.41.128.0/17','162.158.0.0/15','104.16.0.0/12');

    What exactly does this directive do? I mean in clear words please…
    define('WP_FAIL2BAN_BLOCK_USER_ENUMERATION',true);

    Thanks for any assistance ??

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

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author invisnet

    (@invisnet)

    Not quite:

    define('WP_FAIL2BAN_PROXIES','199.27.128.0/21,173.245.48.0/20,103.21.244.0/22,103.22.200.0/22,103.31.4.0/22,141.101.64.0/18,108.162.192.0/18,190.93.240.0/20,188.114.96.0/20,197.234.240.0/22,198.41.128.0/17,162.158.0.0/15,104.16.0.0/12');

    The list of IP ranges has to be a single string.

    WP_FAIL2BAN_BLOCK_USER_ENUMERATION stops bots from getting a list of users by checking for a 404 response from /?author=12345. It’s a speed-bump rather than a real barrier, but it does help.

    Thread Starter Ovidiu

    (@ovidiu)

    Ah, thanks for correcting my syntax and clarifying my other question.
    Seems I don’t need the second option since I’m using WordFence that has a similar option described as: “Prevent discovery of usernames through ‘?/author=N’ scans”

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘need some hand-holding with the advanced features of this plugin’ is closed to new replies.