From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/2] libhtp: update to 0.5.33
Date: Tue, 28 Apr 2020 18:35:56 +0200 [thread overview]
Message-ID: <feee1dce-4eee-fb24-bbf6-0b63fcfaa4c0@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]
(Scanty) release notes:
0.5.33 (27 April 2020)
----------------------
- compression bomb protection
- memory handling issue found by Oss-Fuzz
- improve handling of anomalies in traffic
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
lfs/libhtp | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lfs/libhtp b/lfs/libhtp
index 8a7ad6dfc..9cbc8480a 100644
--- a/lfs/libhtp
+++ b/lfs/libhtp
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2019 Michael Tremer & Christian Schmidt #
+# Copyright (C) 2007-2020 IPFire Team <info(a)ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,7 +24,7 @@
include Config
-VER = 0.5.32
+VER = 0.5.33
THISAPP = libhtp-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = db2e049c8e3b5e4826e18b75a0dc0f62
+$(DL_FILE)_MD5 = d01e386d1d8f13774239e920fcf143da
install : $(TARGET)
--
2.16.4
next reply other threads:[~2020-04-28 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 16:35 Peter Müller [this message]
2020-04-28 16:36 ` [PATCH 2/2] Suricata: update to 5.0.3 Peter Müller
2020-04-29 10:31 ` Michael Tremer
2020-04-29 10:31 ` [PATCH 1/2] libhtp: update to 0.5.33 Michael Tremer
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=feee1dce-4eee-fb24-bbf6-0b63fcfaa4c0@ipfire.org \
--to=peter.mueller@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