Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
path: root/net-analyzer
Commit message (Collapse)AuthorAgeFilesLines
* net-analyzer/nagios-check_rbl: x86 stable (bug #627066)Thomas Deutschmann2017-11-071-1/+1
| | | | Package-Manager: Portage-2.3.13, Repoman-2.3.4
* net-analyzer/ndoutils: add myself as maintainer, update upstream info.Michael Orlitzky2017-11-071-1/+4
| | | | Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/ndoutils: new version 2.1.3.Michael Orlitzky2017-11-079-102/+343
| | | | | | | | | | | | | | | | | | | | This is somewhat of a work in progress. The new version 2.1.3 is intended mainly to fix the compatibility with modern versions of nagios-core. However, there are still several fixes in the pipeline that we're having to carry patches for in the meantime: * format-security warnings (upstream pull request 42) * default PID file location (upstream pull request 44) * asprintf compile warnings (upstream issue 43) * openrc service file improvements (not yet submitted) The last patch has not been submitted because I'm waiting on a response for upstream issue 45 that affects the init scripts. Regardless, we might as well push out v2.1.3 now, since it has to work better than v2.0.0. Closes: https://bugs.gentoo.org/599452 Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/nessus-agent-bin: remove some old versionsMarek Szuba2017-11-063-130/+0
| | | | Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/nessus-agent-bin: bump to 6.11.2Marek Szuba2017-11-062-0/+65
| | | | Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/prometheus: Version bump to 2.0.0_rc3Manuel Rüger2017-11-052-0/+69
| | | | Package-Manager: Portage-2.3.12, Repoman-2.3.4
* net-analyzer/prometheus: Version bump to 1.8.2Manuel Rüger2017-11-052-0/+60
| | | | Package-Manager: Portage-2.3.12, Repoman-2.3.4
* net-analyzer/postal: fix building with GCC-6.Peter Levine2017-11-051-4/+4
| | | | | | Closes: https://bugs.gentoo.org/595084 Closes: https://github.com/gentoo/gentoo/pull/5912 Package-Manager: Portage-2.3.10, Repoman-2.3.3
* net-analyzer/goaccess: version bump to 1.2.Vladimir Pavljuchenkov (SpiderX)2017-11-053-2/+55
| | | | | | | | 1. Added geoipv2 USE-flag to support MaxMind's GeoIP. 2. Updated REQUIRED_USE. Package-Manager: Portage-2.3.8, Repoman-2.3.2 Closes: https://github.com/gentoo/gentoo/pull/6064
* net-analyzer/pnp4nagios: use group permissions for writable directories.Michael Orlitzky2017-11-041-3/+6
| | | | | | | | | | The past few revisions have made some directories owned by the "nagios user" so that the nagios/icinga daemon can write stuff there. Instead of giving ownership of those directories to the nagios user, it's a little bit more secure to give group-rwx permissions to the "nagios group." This new revision does that instead. Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pnp4nagios: drop USE=icinga2 in a new revision.Michael Orlitzky2017-11-042-11/+7
| | | | | | | | | Now that pnp4nagios doesn't rely on the localstatedir of Nagios or Icinga, the two implementations of Icinga are actually suitable for an "or" dependency. We therefore do away with USE=icinga2, and let USE=icinga mean "either icinga or icinga2." Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pnp4nagios: tighten permissions on process_perfdata.cfg.Michael Orlitzky2017-11-041-5/+0
| | | | | | | With USE=apache2, we used to set the group of process_perfdata.cfg to "apache2", but that appears unnecessary. This revision doesn't do it. Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pnp4nagios: fix the default stats directory.Michael Orlitzky2017-11-041-8/+13
| | | | | | | | | | | The process_perfdata.cfg file refers to a STATS_DIR that is set to "@localstatedir@/stats" at build-time. However, the build system doesn't create that directory nor ensure that it is writable. This latest revision passes --localstatedir to econf, and then creates the associated directory with the desired permissions. The "bulk mode" without NPCD now works out-of-the-box! Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pnp4nagios: use consistent perfdata directories.Michael Orlitzky2017-11-041-17/+15
| | | | | | | | | | Past revisions have stored the RRDtool data and the process_perdata.pl logs in (for example) /var/nagios or /var/icinga, depending on whether or you had Nagios or Icinga installed. That's silly: the data format doesn't change, so it makes more sense to choose one location (now: /var/lib/pnp) and stick with it. Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pnp4nagios: new revision to fix apache2 conf file.Michael Orlitzky2017-11-041-1/+1
| | | | | | | | | | | | | The last few revisions have done, insinto "${APACHE_MODULES_CONFDIR}" but the depend.apache eclass was removed in pnp4nagios-0.6.25-r3, which means that the conf file wound up installed to ${ROOT}. The new revision specifies the path explicitly without using the eclass variable. Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pnp4nagios: drop pointless rrdtool lower bound.Michael Orlitzky2017-11-041-1/+1
| | | | Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pnp4nagios: change "-DPHP5" to "-DPHP" in pkg_postinst().Michael Orlitzky2017-11-041-1/+1
| | | | | | | | The apache "define" changed a while ago from "PHP5" to simply "PHP". This commit fixes the latest revision, in place, to output the correct instructions. Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pnp4nagios: new revision to fix insecure config permissions.Michael Orlitzky2017-11-041-1/+3
| | | | | | | | | | | | Previous revisions of pnp4nagios install /etc/pnp owned by the "nagios user," and the npcd daemon also runs as that user. That configuration is insecure: the unprivileged user can edit /etc/pnp/npcd.cfg, and escalate his own privileges by setting "user = root". To avoid the problem, we set INSTALL_OPTS="" while running "emake install". That leaves all of /etc/pnp with the default (root:root) ownership. Bug: https://github.com/lingej/pnp4nagios/issues/140 Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pnp4nagios: new revision with a better fix for CVE-2012-3457.Michael Orlitzky2017-11-041-14/+7
| | | | | | | | | | In CVE-2012-3457, it was reported that one particular file should not be world-readable. To fix that, our ebuild made all of /etc/pnp unreadable; that made other permissions issues difficult to work around. This r2 sets o-rwx only on /etc/pnp/process_perfdata.cfg. Bug: https://bugs.gentoo.org/430358 Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pnp4nagios: new revision to fix nagios/icinga "or" dependency.Michael Orlitzky2017-11-042-9/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previous revisions of pnp4nagios have an "or" dependency on either Nagios or Icinga, || ( net-analyzer/nagios-core net-analyzer/icinga ... The way "or" dependencies work is that they are considered satisfied if any elements of the associated group are installed. Thus the above stanza allows Nagios and Icinga to be swapped out without rebuilding pnp4nagios. That is incorrect, since later in the ebuild, nagios- or icinga-specific paths are compiled into pnp4nagios. The usual solution to that problem is to choose a default package that satisfies the "one of these" dependency, but to allow the user to specify one with a USE flag. This new revision adds three USE flags: icinga, icinga2, and nagios. The "nagios" flag is enabled by default, and builds pnp4nagios against net-analyzer/nagios. The other flags build against the associated package. In the process, the dependency on nagios-3.x was loosened to accept nagios-4.x as well. The nagios-3.x series has been end-of-life'd, and has multiple open security bugs. Bug: https://bugs.gentoo.org/628086 Bug: https://bugs.gentoo.org/629380 Bug: https://bugs.gentoo.org/636234 Closes: https://bugs.gentoo.org/600424 Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pnp4nagios: new version 0.6.26.Michael Orlitzky2017-11-042-0/+99
| | | | Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/iftop: stable 1.0_pre4-r2 for sparc, bug #615812 (thanks to ↵Sergei Trofimovich2017-11-041-1/+1
| | | | | | | Rolf Eike Beer) Package-Manager: Portage-2.3.13, Repoman-2.3.4 RepoMan-Options: --include-arches="sparc"
* net-analyzer/argus: Add option to build against libtirpc for RPC support, ↵Andreas K. Hüttel2017-11-013-0/+136
| | | | | | | bug 631474 Closes: https://bugs.gentoo.org/631474 Package-Manager: Portage-2.3.10, Repoman-2.3.3
* net-analyzer/nsat: Depend unconditionally on libnslAndreas K. Hüttel2017-11-011-1/+1
| | | | Package-Manager: Portage-2.3.13, Repoman-2.3.4
* net-analyzer/dsniff: Depend unconditionally on libnslAndreas K. Hüttel2017-11-011-1/+1
| | | | Package-Manager: Portage-2.3.13, Repoman-2.3.4
* net-analyzer/snort: Depend unconditionally on libnslAndreas K. Hüttel2017-11-011-1/+1
| | | | Package-Manager: Portage-2.3.13, Repoman-2.3.4
* net-analyzer/ifstatus: amd64 stable, bug 632311Andreas K. Hüttel2017-10-311-1/+1
| | | | | Bug: https://bugs.gentoo.org/632311 Package-Manager: Portage-2.3.13, Repoman-2.3.4
* net-analyzer/testssl: remove 2.8Michael Palimaka2017-10-312-62/+0
| | | | Package-Manager: Portage-2.3.8, Repoman-2.3.4
* net-analyzer/testssl: stabilise 2.9.5 for amd64Michael Palimaka2017-10-311-1/+1
| | | | Package-Manager: Portage-2.3.8, Repoman-2.3.4
* net-analyzer/nagios-check_ipmi_sensor: Removed proxied maintainerJonas Stein2017-10-291-10/+1
| | | | | | | Removed proxied maintainer due to inactivity. Did not respond to mail. No more activity on bugzilla. Closes: https://bugs.gentoo.org/633160 Package-Manager: Portage-2.3.13, Repoman-2.3.4
* net-analyzer/snort: Removed proxied maintainerJonas Stein2017-10-291-9/+0
| | | | | | Removed proxied maintainer due to inactivity. Closes: https://bugs.gentoo.org/633262 Package-Manager: Portage-2.3.13, Repoman-2.3.4
* net-analyzer/barnyard2: Removed proxied maintainerJonas Stein2017-10-291-28/+19
| | | | | | | Removed proxied maintainer due to inactivity. Fixed spaces/tabs in metadata. Package-Manager: Portage-2.3.13, Repoman-2.3.4
* net-analyzer/munin: add 2.0.34Hans de Graaff2017-10-292-0/+415
| | | | | | | Consolidate patches into patchset Avoid test that is broken on Linux, bug 630472 Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/wireshark: keyworded 2.4.2 for ia64, bug #635686Sergei Trofimovich2017-10-281-1/+1
| | | | | Package-Manager: Portage-2.3.13, Repoman-2.3.4 RepoMan-Options: --include-arches="ia64"
* net-analyzer/monitoring-plugins: new revision to fix build failure with MariaDB.Michael Orlitzky2017-10-272-0/+104
| | | | | | | | The latest -r2 adds a patch (which I've sent upstream) to fix a build failure against newer versions of MariaDB. Closes: https://bugs.gentoo.org/633548 Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/nagios-plugins: new revision to fix build failure with MariaDB.Michael Orlitzky2017-10-272-0/+102
| | | | | | | | | The latest -r2 adds a patch (which I've sent upstream) to fix a build failure against newer versions of MariaDB. Bug: https://bugs.gentoo.org/633548 Bug: https://bugs.gentoo.org/635106 Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/ifstatus: x86 stable (bug #632311)Thomas Deutschmann2017-10-261-1/+1
| | | | Package-Manager: Portage-2.3.11, Repoman-2.3.3
* net-analyzer/prometheus-node_exporter: Remove oldManuel Rüger2017-10-263-68/+0
| | | | Package-Manager: Portage-2.3.12, Repoman-2.3.3
* net-analyzer/prometheus: Remove oldManuel Rüger2017-10-263-129/+0
| | | | Package-Manager: Portage-2.3.12, Repoman-2.3.3
* net-analyzer/prometheus: Version bump to 2.0.0_rc2Manuel Rüger2017-10-262-0/+69
| | | | Package-Manager: Portage-2.3.12, Repoman-2.3.3
* net-analyzer/cacti-spine: amd64 stable wrt bug #626992Agostino Sarubbo2017-10-251-1/+1
| | | | | | Package-Manager: Portage-2.3.8, Repoman-2.3.3 RepoMan-Options: --include-arches="amd64" Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
* net-analyzer/cacti: amd64 stable wrt bug #626992Agostino Sarubbo2017-10-251-1/+1
| | | | | | Package-Manager: Portage-2.3.8, Repoman-2.3.3 RepoMan-Options: --include-arches="amd64" Signed-off-by: Agostino Sarubbo <ago@gentoo.org>
* net-analyzer/hexinject: Respect CFLAGSNils Freydank2017-10-252-0/+54
| | | | | | | Closes: https://github.com/gentoo/gentoo/pull/5987 Package-Manager: Portage-2.3.11, Repoman-2.3.3 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org>
* net-analyzer/prometheus: Version bump to 1.8.1Manuel Rüger2017-10-242-0/+60
| | | | Package-Manager: Portage-2.3.12, Repoman-2.3.3
* net-analyzer/pmacct: CPPFLAGS not CFLAGS.Jeroen Roovers2017-10-231-1/+1
| | | | Package-Manager: Portage-2.3.12, Repoman-2.3.3
* net-analyzer/pmacct: Fix building against >>>=o=>>>dev-db:::mariadb/10.2.Jeroen Roovers2017-10-231-1/+2
| | | | Package-Manager: Portage-2.3.12, Repoman-2.3.3
* net-analyzer/monitoring-plugins: new revision adding radius support.Michael Orlitzky2017-10-221-0/+102
| | | | | | | | | | | | | The monitoring-plugins build system has automagic support for radius that can be disabled via the --without-radius flag. Doing so allows (or prevents) the check_radius plugin from being built. This new revision adds "radius" to IUSE for monitoring-plugins, and builds check_radius (and pulls in its dependencies) only with USE=radius. Thanks to Martin Samek who noticed the missing flag. Closes: https://bugs.gentoo.org/634582 Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/nagios-plugins: new revision adding radius support.Michael Orlitzky2017-10-221-0/+116
| | | | | | | | | | | | | The nagios-plugins build system has automagic support for radius that can be disabled via the --without-radius flag. Doing so allows (or prevents) the check_radius plugin from being built. This new revision adds "radius" to IUSE for nagios-plugins, and builds check_radius (and pulls in its dependencies) only when USE=radius is set. Thanks to Martin Samek who noticed the missing flag. Bug: https://bugs.gentoo.org/634582 Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/arpwatch: new revision to fix privilege escalation.Michael Orlitzky2017-10-223-0/+113
| | | | | | | | | | | | | | | | | | | | | In previous revisions, the init script for arpwatch called "chown" as root on a location under /var/lib/arpwatch -- a path that is controlled by the "arpwatch" user per its ebuild. That could be exploited by the "arpwatch" user to take control of root-owned files. This new revision comes with a new init script and conf.d file that completely rework the way instances are created and run. The "arpwatch" user is hard-coded, because as was mentioned, the ebuild sets some important permissions for that user. Since it is not possible to change that user, the need for "chown" is eliminated. Separate instances are now created by symlinking the init script (like our network interface scripts), rather than by enumerating them in a single arpwatch init script. Upgraders will want to review their configurations. Bug: https://bugs.gentoo.org/602552 Package-Manager: Portage-2.3.8, Repoman-2.3.3
* net-analyzer/pmacct: Version bump.Jeroen Roovers2017-10-223-6/+94
| | | | Package-Manager: Portage-2.3.12, Repoman-2.3.3