From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] suricata: 'Downdate' to 5.0.5
Date: Mon, 14 Dec 2020 10:33:31 +0100 [thread overview]
Message-ID: <347769F2-CB29-474C-988C-0AE3216E3A54@ipfire.org> (raw)
In-Reply-To: <20201212091435.20982-1-matthias.fischer@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1526 bytes --]
Hi,
Thank you for submitting this patch.
I am not sure if I want to merge this, yet.
I will consider this when we move closer to a release, but upstream didn’t provide a solution, yet.
I suppose it is okay if we burn through a little bit more of CPU as long as the system is secure. The overhead seems to be small enough for me to not cause any significant impact on throughput or latency.
Is this an acceptable benchmark for you?
Best,
-Michael
> On 12 Dec 2020, at 10:14, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Triggered by https://lists.ipfire.org/pipermail/development/2020-December/008868.html
>
> Workaround for https://bugzilla.ipfire.org/show_bug.cgi?id=12548
>
> Downgrading to 'suricata 5.0.5' bypasses Bug #12548 for now,
> but its only a temporary workaround...
>
> Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
> ---
> lfs/suricata | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/lfs/suricata b/lfs/suricata
> index 2871d8e7b..c5dc46af4 100644
> --- a/lfs/suricata
> +++ b/lfs/suricata
> @@ -24,7 +24,7 @@
>
> include Config
>
> -VER = 6.0.0
> +VER = 5.0.5
>
> THISAPP = suricata-$(VER)
> DL_FILE = $(THISAPP).tar.gz
> @@ -44,7 +44,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = bbddcf2f209930206ef21977d40120d2
> +$(DL_FILE)_MD5 = fe039cc4571eb56828874ddc0b71dc51
>
> install : $(TARGET)
>
> --
> 2.18.0
>
next prev parent reply other threads:[~2020-12-14 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 9:14 Matthias Fischer
2020-12-14 9:33 ` Michael Tremer [this message]
2020-12-14 20:02 ` Matthias Fischer
2020-12-15 16:12 ` 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=347769F2-CB29-474C-988C-0AE3216E3A54@ipfire.org \
--to=michael.tremer@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