From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <development+bounces-747-archive=lists.ipfire.org@lists.ipfire.org>
Received: from mail02.haj.ipfire.org (localhost [127.0.0.1])
	by mail02.haj.ipfire.org (Postfix) with ESMTP id 4bmhbp0NVLz331t
	for <archive@lists.ipfire.org>; Tue, 22 Jul 2025 15:52:22 +0000 (UTC)
Received: from mail01.ipfire.org (mail01.haj.ipfire.org [172.28.1.202])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature ECDSA (secp384r1)
	 client-signature RSA-PSS (4096 bits))
	(Client CN "mail01.haj.ipfire.org", Issuer "R11" (verified OK))
	by mail02.haj.ipfire.org (Postfix) with ESMTPS id 4bmhbk3zH9z2xSN
	for <development@lists.ipfire.org>; Tue, 22 Jul 2025 15:52:18 +0000 (UTC)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
	(No client certificate requested)
	by mail01.ipfire.org (Postfix) with ESMTPSA id 4bmhbj52zrzkc
	for <development@lists.ipfire.org>; Tue, 22 Jul 2025 15:52:17 +0000 (UTC)
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org;
	s=202003ed25519; t=1753199537;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding;
	bh=5x/eiiIqeTkbL8JN06O4++5GDB18hCevaZGeYsXj970=;
	b=i+mbG8ycrbWQ07c2DckQi8mD6t3sS0Mk53m8s9FRK/TbNqias84HhIVjnwj5EgYcbcTtJQ
	N0Bwmd1TOQFX/GBg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa;
	t=1753199537;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:mime-version:mime-version:content-type:content-type:
	 content-transfer-encoding:content-transfer-encoding;
	bh=5x/eiiIqeTkbL8JN06O4++5GDB18hCevaZGeYsXj970=;
	b=g8iiH6S5DF1dkZbpMrWAgaejpmPbMRfPrhY+kIsUzSB+Bw97TC9LmHlRjyS2E5hIAgr7Rc
	1ECz+f/mAGokpOlIIEwjzfZ0OwYsPrxu4GHSAMfO8f9XPI88MyqlJbyPXJbbNWTL423Wv9
	fD61jiaZWzApiuGgO0G4liY3oPdsgVvHQKCFJh3ySpok7nw1dS4d6H+Cemq3xZuTvGXAlY
	cN+pieE76xz0Lea7b83/Ff7DEhmi967LK/ev65w2JYX8pYtQ/OUBgYDUzFNrAoUk14cxiK
	oZaGyXlPv6BB3wRY+fKezINSUu4cAxrrELLAW+qgnTTmEAgMfd+AI6UiQW/Kyg==
Message-ID: <83782aac-0d2e-40e9-acc3-8f6105873821@ipfire.org>
Date: Tue, 22 Jul 2025 17:52:14 +0200
Precedence: list
List-Id: <development.lists.ipfire.org>
List-Subscribe: <https://lists.ipfire.org/>,
 <mailto:development+subscribe@lists.ipfire.org?subject=subscribe>
List-Unsubscribe: <https://lists.ipfire.org/>,
 <mailto:development+unsubscribe@lists.ipfire.org?subject=unsubscribe>
List-Post: <mailto:development@lists.ipfire.org>
List-Help: <mailto:development+help@lists.ipfire.org?subject=help>
Sender: <development@lists.ipfire.org>
Mail-Followup-To: <development@lists.ipfire.org>
MIME-Version: 1.0
Content-Language: en-GB
To: "IPFire: Development-List" <development@lists.ipfire.org>
From: Adolf Belka <adolf.belka@ipfire.org>
Subject: suricata-8.0.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

I have done a patch submission for suricata-7.0.11 as there were a couple of CVE fixes for that.

However suricata-8.0.0 has been released. I have built it and installed it and confirmed that it is working as expected and that testing it with an alert blocked the traffic access and logged the information.

The question I have is should I submit a patch to update suricata to 8.0.0 in CU197 or wait for next to become CU198?

Regards,

Adolf.