From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] suricata: Update to 4.1.5
Date: Fri, 27 Sep 2019 18:58:53 +0200 [thread overview]
Message-ID: <b6ff6dfb9a9bb36f7ce3af85ff39fcf65e2d5bb3.camel@ipfire.org> (raw)
In-Reply-To: <20190927160849.1860-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2783 bytes --]
Excellent work.
This fixes bug #12186
Reviewed-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> Changelog:
> "4.1.5 -- 2019-09-24
>
> Feature #3068: protocol parser: vxlan (4.1.x)
> Bug #2841: False positive alerts firing after upgrade suricata 3.0 ->
> 4.1.0 (4.1.x)
> Bug #2966: filestore (v1 and v2): dropping of "unwanted" files
> (4.1.x)
> Bug #3008: rust: updated libc crate causes depration warnings (4.1.x)
> Bug #3044: tftp: missing logs because of broken tx handling (4.1.x)
> Bug #3067: GeoIP keyword depends on now discontinued legacy GeoIP
> database (4.1.x)
> Bug #3094: Fedora rawhide af-packet compilation err (4.1.x)
> Bug #3123: bypass keyword: Suricata 4.1.x Segmentation Faults (4.1.x)
> Bug #3129: Fixes warning about size of integers in string formats
> (4.1.x)
> Bug #3159: SC_ERR_PCAP_DISPATCH with message "error code -2" upon
> rule reload completion (4.1.x)
> Bug #3164: Suricata 4.1.4: NSS Shutdown triggers crashes in test mode
> Bug #3168: tls: out of bounds read
> Bug #3170: defrag: out of bounds read
> Bug #3173: ipv4: ts field decoding oob read
> Bug #3175: File_data inspection depth while inspecting base64 decoded
> data (4.1.x)
> Bug #3184: decode/der: crafted input can lead to resource starvation
> Bug #3186: Multiple Content-Length headers causes HTP_STREAM_ERROR
> (4.1.x)
> Bug #3187: GET/POST HTTP-request with no Content-Length,
> http_client_body miss (4.1.x)"
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> lfs/suricata | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/lfs/suricata b/lfs/suricata
> index 6f779d875..12dcfe08c 100644
> --- a/lfs/suricata
> +++ b/lfs/suricata
> @@ -1,7 +1,7 @@
> ####################################################################
> ###########
> #
> #
> # IPFire.org - A linux based
> firewall #
> -# Copyright (C) 2007-2018 IPFire Team <info(a)ipfire.org>
> #
> +# Copyright (C) 2007-2019 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 = 4.1.4
> +VER = 4.1.5
>
> THISAPP = suricata-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = cb8bf6b8330c44ae78dfb5b083a6fe82
> +$(DL_FILE)_MD5 = 0dfd68f6f4314c5c2eed7128112eff3b
>
> install : $(TARGET)
>
prev parent reply other threads:[~2019-09-27 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 16:08 Matthias Fischer
2019-09-27 16:58 ` Stefan Schantl [this message]
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=b6ff6dfb9a9bb36f7ce3af85ff39fcf65e2d5bb3.camel@ipfire.org \
--to=stefan.schantl@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