IMHO, this was a horribly bad decision upstream. If you've restricted your incoming NRPE source to a trusted one with UFW or similar, this is a perfectly safe thing to do and helps centrally manage lots of parameters. I think a default arg of 0 was enough to keep a safe config. Users who choose to enable an unsafe configuration without mitigations despite the documented warnings are idiots and the package shouldn't be crippled as a result.
I volunteer to maintain this package in Ubuntu and build with a different config than upstream. Please contact me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nagios-nrpe in Ubuntu. https://bugs.launchpad.net/bugs/1384931 Title: NRPE does not respect "dont_blame_nrpe" argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nagios-nrpe/+bug/1384931/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
