xmlrpc logging to LOG_AUTH

  • Resolved richardwo

    (@richardwo)


    10 years, 6 months ago

    I’ve been getting many pingback requests via xmlrpc.php so I installed this plugin, made fail2ban changes and set WP_FAIL2BAN_LOG_PINGBACKS to true in wp-config.php
    However the pingbacks weren’t getting logged to /var/log/auth.log.
    I tried setting
    define(‘WP_FAIL2BAN_PINGBACKS_LOG’,LOG_AUTH);
    in wp-config.php but that didn’t help.
    In the end I removed the WP_FAIL2BAN_PINGBACKS_LOG line from wp-config.php and edited the plugin and changed the last openlog line to use LOG_AUTH instead of LOG_USER and it all started working as intended.
    Is this a problem with the plugin or did I do something wrong?
    Thanks.

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • vguna

    (@veitgunagmxde)

    Same here. Tried both, LOG_AUTH and LOG_AUTHPRIV. It’s always logged to /var/log/syslog. I’m using Ubuntu 14.04. Any idea what’s going wrong?

    Plugin Author invisnet

    (@invisnet)

    Pingbacks aren’t an authentication event so LOG_USER is a more suitable place than LOG_AUTH.

    If this is a big problem for people I’ll add another option to configure it (the default will still be LOG_USER).

    Thread Starter richardwo

    (@richardwo)

    Thanks – I’ve just updated to 2.3.0 and by using:

    define('WP_FAIL2BAN_LOG_PINGBACKS',true);
define('WP_FAIL2BAN_PINGBACK_LOG',LOG_AUTH);

    in my wp-config.php it is logging the pingbacks to the auth.log just how I want it to (without having to change the plugin code).

    Thread Starter richardwo

    (@richardwo)

    Marked as resolved.
    I think it may have just been me using the wrong constant initially – WP_FAIL2BAN_PINGBACKS_LOG instead of WP_FAIL2BAN_PINGBACK_LOG.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘xmlrpc logging to LOG_AUTH’ is closed to new replies.