public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Adolf Belka (ipfire)" <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/2] nagios_nrpe: Update to 4.0.3
Date: Wed, 10 Mar 2021 13:08:14 +0100	[thread overview]
Message-ID: <20210310120814.4481-1-adolf.belka@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3280 bytes --]

- Update nagios_nrpe from 3.2.1 to 4.0.3
- No update for rootfile
- Changelog
   [4.0.3](https://github.com/NagiosEnterprises/nrpe/releases/tag/nrpe-4.0.3) - 2020-04-28
    **FIXES**
     - Fixed nasty_metachars not being read from config file (#235) (Sebastian Wolf)
   [4.0.2](https://github.com/NagiosEnterprises/nrpe/releases/tag/nrpe-4.0.2) - 2020-03-11
    **FIXES**
     - Fixed buffer length calculations/writing past memory boundaries on some systems  (#227, #228) (Andreas Baumann, hariwe, Sebastian Wolf)
     - Fixed use of uninitialized variable when validating requests (#229) (hariwe, Sebastian Wolf)
   [4.0.1](https://github.com/NagiosEnterprises/nrpe/releases/tag/nrpe-4.0.1) - 2020-01-22
    **FIXES**
     * Fixed syslog flooding with CRC-checking errors when both plugin and agent were updated to version 4 (Sebastian Wolf)
   [4.0.0](https://github.com/NagiosEnterprises/nrpe/releases/tag/nrpe-4.0.0) - 2019-01-13
    Note: This update includes security fixes which affect both the check_nrpe plugin and
    the NRPE daemon. The latest version of NRPE is still able to interoperate with previous
    versions, but for best results, both programs should be updated.
    **ENHANCEMENTS**
     * Added TLSv1.3 and TLSv1.3+ support for systems that have it (Nigel Yong, Rahul Golam)
     * Added IPv6 ip address to list of default allow_from hosts (Troy Lea)
     * Added -D option to disable logging to syslog (Tom Griep, Sebastian Wolf)
     * Added -3 option to force check_nrpe to use NRPE v3 packets
     * OpenRC: provide a default path for nrpe.cfg (Michael Orlitzky)
     * OpenRC: Use RC_SVCNAME over a hard-coded PID file (j-licht)
    **FIXES**
     * Checks for '!' now only occur inside the command buffer (Joni Eskelinen)
     * NRPE daemon is more resilient to DOS attacks (Leonid Vasiliev)
     * allowed_hosts will no longer test getaddrinfo records against the wrong protocol (dombenson)
     * nasty_metachars will now handle C escape sequences properly when specified in the config file (Sebastian Wolf)
     * Calculated packet sizes now struct padding/alignment when sending and receiving messages (Sebastian Wolf)
     * Buffer sizes are now checked before use in packet size calculation (Sebastian Wolf)
     * When using `include_dir`, individual files' errors do not prevent the remaining files from being read (Sebastian Wolf)

Signed-off-by: Adolf Belka (ipfire) <adolf.belka(a)ipfire.org>
---
 lfs/nagios_nrpe | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/lfs/nagios_nrpe b/lfs/nagios_nrpe
index 075bfdef9..a011a75b4 100644
--- a/lfs/nagios_nrpe
+++ b/lfs/nagios_nrpe
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 3.2.1
+VER        = 4.0.3
 
 THISAPP    = nrpe-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -32,7 +32,7 @@ DL_FROM    = $(URL_IPFIRE)
 DIR_APP    = $(DIR_SRC)/$(THISAPP)
 TARGET     = $(DIR_INFO)/$(THISAPP)
 PROG       = nagios_nrpe
-PAK_VER    = 6
+PAK_VER    = 7
 
 DEPS       = nagios-plugins
 
@@ -44,7 +44,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = 8997e195fea93cdceb8c7ed8ac1d43bc
+$(DL_FILE)_MD5 = 42252d3c721c87ebb5e38b748f187e8d
 
 install : $(TARGET)
 
-- 
2.30.2


                 reply	other threads:[~2021-03-10 12:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210310120814.4481-1-adolf.belka@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox