From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail02.haj.ipfire.org (localhost [127.0.0.1]) by mail02.haj.ipfire.org (Postfix) with ESMTP id 4bmhfN0ZmYz331t for ; Tue, 22 Jul 2025 15:54:36 +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 4bmhfJ3k50z2xSN for ; Tue, 22 Jul 2025 15:54:32 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail01.ipfire.org (Postfix) with ESMTPSA id 4bmhfJ01SlzlX; Tue, 22 Jul 2025 15:54:31 +0000 (UTC) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003ed25519; t=1753199672; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=b3USApwLCwW7CLz/1YWg6knT2hjrM5D0dPtwf5UJuRo=; b=BUvGilrlDk4Bvn15xbyRT72EV1vdAuH7hDG9lW2UTDFBjQ9Brw0yLZt5PcujKvEvZsbxVq QXs1lNE4xaD99QCw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipfire.org; s=202003rsa; t=1753199672; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=b3USApwLCwW7CLz/1YWg6knT2hjrM5D0dPtwf5UJuRo=; b=r3rfpXKTmpRPG9g7gJstu5xWnNzwqTiXV19EX3u2cR7pM5ElKZ0lKyxX89jIT1TAfPsC9d VrypuqC9EB0UxzmfDWck846C+ijVNsrGJc2JiREU0unrKKxmumnSy9I701go0Kz9guUs3p IN4DdrsE+MXvgaXOMDtW4w7yd1DXNdwcr78jNyxudNfgAAjOu6Su1TmY/qc7HKK1g6SKp5 rDUsqpaS+8b5jHS4/FcNBDm5HYAth8sXVcCpsDqDONHxgTCMNRPmTJQFxy5jziYl9JHJqV A9SmMQnKCYmtZGKSTfkNDkDirQTRa3pjenSehjWIkKcoIjmNGrZ42YyD34aSGw== Content-Type: text/plain; charset=utf-8 Precedence: list List-Id: List-Subscribe: , List-Unsubscribe: , List-Post: List-Help: Sender: Mail-Followup-To: Mime-Version: 1.0 Subject: Re: suricata-8.0.0 From: Michael Tremer In-Reply-To: <83782aac-0d2e-40e9-acc3-8f6105873821@ipfire.org> Date: Tue, 22 Jul 2025 16:54:31 +0100 Cc: "IPFire: Development-List" Content-Transfer-Encoding: quoted-printable Message-Id: References: <83782aac-0d2e-40e9-acc3-8f6105873821@ipfire.org> To: Adolf Belka Hello Adolf, This is great news. Regarding to where this is going, I don=E2=80=99t know=E2=80=A6 Generally I would say we should release as early as possible. However, = the bottleneck that we currently have is that there is very limited test = feedback. Since we already have OpenVPN in the next release, I would = agree that this might be enough. You can submit the patch no matter what and we can decide where to merge = it later. -Michael > On 22 Jul 2025, at 16:52, Adolf Belka wrote: >=20 > Hi all, >=20 > I have done a patch submission for suricata-7.0.11 as there were a = couple of CVE fixes for that. >=20 > 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. >=20 > 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? >=20 > Regards, >=20 > Adolf. >=20