From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] suricata: Update to 6.0.10
Date: Thu, 09 Feb 2023 10:31:44 +0100 [thread overview]
Message-ID: <a8e4f068c560b78e5297c4d70020651629f6e67f.camel@ipfire.org> (raw)
In-Reply-To: <20230203161321.3487937-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4050 bytes --]
Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ""6.0.10 -- 2023-01-31
>
> Security #5804: Suricata crashes while processing FTP (6.0.x
> backport)
> Bug #5815: detect: config keyword prevents tx cleanup (6.0.x
> backport)
> Bug #5812: nfs: debug validation triggered on nfs2 read
> Bug #5810: smb/ntlmssp: parser incorrectly assumes fixed field order
> (6.0.x backport)
> Bug #5806: exceptions: midstream flows are dropped if midstream=true
> && stream.midstream-policy=drop-flow (6.0.x backport)
> Bug #5796: TLS Handshake Fragments not Reassembled (6.0.x backport)
> Bug #5795: detect/udp: different detection from rules when UDP/TCP
> header is broken (6.0.x backport)
> Bug #5793: decode: Padded packet to minimal Ethernet length marked
> with invalid length event (6.0.x backport)
> Bug #5791: smb: unbounded file chunk queuing after gap (6.0.x
> backport)
> Bug #5763: libbpf: Use of legacy code in eBPF/XDP programs (6.0.x
> backport)
> Bug #5762: detect/pcre: JIT not disabled when OS doesn't allow RWX
> pages
> Bug #5760: nfs: ASSERT: attempt to subtract with overflow (compound)
> (6.0.x backport)
> Bug #5749: iprep/ipv6: warning issued on valid reputation input
> (6.0.x backport)
> Bug #5744: netmap: 6.0.9 v14 backport causes known packet stalls from
> v14 implementation in "legacy" mode too
> Bug #5738: smb: failed assertion (!((f->alproto == ALPROTO_SMB &&
> txd->files_logged != 0))), function CloseFile, file output-file.c
> (6.0.x backport)
> Bug #5735: smtp: quoted-printable encoding skips empty lines in files
> (6.0.x backport)
> Bug #5723: eve: missing common fields like community id for some
> event types like RFB
> Bug #5601: detect: invalid hex character in content leads to bad
> debug message (6.0.x backport)
> Bug #5565: Excessive qsort/msort time when large number of rules
> using tls.fingerprint (6.0.x backport)
> Bug #5299: YAML warning from default config on 6.0.5
> Optimization #5797: tls: support incomplete API to replace internal
> buffering
> Optimization #5790: smb: set defaults for file chunk limits (6.0.x
> backport)"
>
> 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 4f1887ee8..98710d9e2 100644
> --- a/lfs/suricata
> +++ b/lfs/suricata
> @@ -1,7 +1,7 @@
> ####################################################################
> ###########
> #
> #
> # IPFire.org - A linux based
> firewall #
> -# Copyright (C) 2007-2022 IPFire Team
> <info(a)ipfire.org> #
> +# Copyright (C) 2007-2023 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 = 6.0.9
> +VER = 6.0.10
>
> THISAPP = suricata-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_BLAKE2 =
> 966657eeff216894f6357989f0317b7c5eed82602ca2381269446cbe4c015be449f55
> 98726b2f58924f20aca30c4e130ecafe642ea4ce39f1671f46093292551
> +$(DL_FILE)_BLAKE2 =
> a2b334c0139ead0b914ba6039c116ebad30dd3b5c0d4bb751f608af83e1487a67b962
> 24ffe61635468dc49a9e44f03a76facf2af66582ba18e364f233029b532
>
> install : $(TARGET)
>
prev parent reply other threads:[~2023-02-09 9:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 16:13 Matthias Fischer
2023-02-05 14:44 ` Adolf Belka
2023-02-09 9:31 ` 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=a8e4f068c560b78e5297c4d70020651629f6e67f.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