MIRNagios

Requirements

  1. Availability: http://archive.ubuntu.com/ubuntu/pool/universe/n/nagios2; available for all supported architectures.

    • Dapper has a nagios version in main, however hardy does not. Also requested by Elmo.
  2. Security:

    • No recent CVE entries affecting hardy. But it does have a history of buffer overflows and XSS vulnerabilities.

    • No recent Secunia histroy.

    • No binaries running as root or suid/sgid.
    • Daemon is started at boot for the monitoring of devices.
    • Due to the nature of the package it accepts both incoming and outgoing network traffic.
    • Listens on port 5666.
    • No source code review.
  3. Quality assurance:

    • Due to the nature of the package it requires to be configured by hand.
    • No debconf questions higher than priority 'medium'.
    • Debian bugs

    • Maintenance in Debian is calm.

    • Upstream is vigorous.

    • No upstream bug tracker, it uses the developer mailing list.
    • No special hardware needed.
  4. Standards compliance:

  5. Dependencies:

    • debhelper, dpatch, po-debconf, libperl-dev, libpng12-dev, libgd2-noxpm-dev or libgd2-xpm-dev, iputils-ping, autotools-dev, dpkg-dev , nagios-plugins-basic, coreutils, mailx, adduser, lsb-base, ucf, apache2-utils. All in main except for nagios-plugins-basic.
  6. There are three different versions of nagios. Nagios 1.x - Very old release branch. Nagios 2.x Legacy stable release branch. Nagios 3.x most recent stable release branch.

Reviewers

MIR bug: https://bugs.edge.launchpad.net/ubuntu/+source/nagios2/+bug/211323

The author of this report should put their name here; reviewers will add comments etc. too

MIRNagios (last edited 2008-08-06 16:26:18 by localhost)