[Bug 297472] net-mgmt/monitoring-plugins: check_mailq broken in 3.0.3

[email protected]
Newsgroups gmane.os.freebsd.devel.ports.bugs
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=297472

            Bug ID: 297472
           Summary: net-mgmt/monitoring-plugins: check_mailq broken in
                    3.0.3
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: [email protected]
          Reporter: [email protected]

# /usr/local/libexec/nagios/check_mailq
Global symbol "$sudo" requires explicit package name (did you forget to declare
"my $sudo"?) at /usr/local/libexec/nagios/check_mailq line 580.
Execution of /usr/local/libexec/nagios/check_mailq aborted due to compilation
errors.


Version 3.0.3 deprecated the usage of sudo in check_mailq -
https://github.com/monitoring-plugins/monitoring-plugins/releases

check_mailq could be used with the sudo option (-s/--sudo) and would execute
sudo then with mailq as an argument AND additional arbitrary arguments given by
the user.
A simple sudo rule to allow the monitoring user to execute this, could lead to
arbitrary command execution with root privileges.

The patch with this release disables the whole sudo option of check_mailq.
Allowing the monitoring user to view the mail queue is now a problem of the MTA
and most (hopefully all) MTAs should support this in one way or another.

In FreeBSD we have a patch files/patch-plugins-scripts_check__mailq.pl which
adds a new command to the check, which currently contains "$sudo" which must be
removed for the plugin to work again with version 3.0.3. Since this also made
it into quarterly, I would recommend also updating quarterly + main :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.