public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: Michael Tremer <michael.tremer@ipfire.org>
Cc: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Re: Fwd: Advance Notification of Suricata 8.0.2 and 7.0.13
Date: Thu, 6 Nov 2025 16:39:28 +0100	[thread overview]
Message-ID: <a67098ef-0f01-4d5e-adfe-b7000f56644f@ipfire.org> (raw)
In-Reply-To: <FB65C8F2-5AB3-4472-B392-64357D5AD15C@ipfire.org>

Hi Michael,


On 06/11/2025 16:22, Michael Tremer wrote:
> Hello,
> 
> Is someone already on this one?

I wasn't but I can do so if no one else has already picked it up.

Regards,

Adolf.


> 
> Best,
> -Michael
> 
>> Begin forwarded message:
>>
>> *From: *Jason Ish <jish@oisf.net>
>> *Subject: **Advance Notification of Suricata 8.0.2 and 7.0.13*
>> *Date: *4 November 2025 at 17:43:20 GMT
>> *To: *Jason Ish <jish@oisf.net>, Victor Julien <vjulien@oisf.net>
>>
>> Hello everyone,
>>
>> On Thursday, November 6, 2025, we plan to release Suricata 8.0.2 and 7.0.13. These are bug-fix and security releases addressing a number of important issues.
>>
>> For other issues fixed in these releases, please see:
>> - Suricata 8.0.2: https://redmine.openinfosecfoundation.org/versions/225 <https://redmine.openinfosecfoundation.org/versions/225>
>> - Suricata 7.0.13: https://redmine.openinfosecfoundation.org/versions/224 <https://redmine.openinfosecfoundation.org/versions/224>
>>
>> Regards,
>> The OISF Team.
>>
>> To unsubscribe from this group and stop receiving emails from it, send an email to oss-advisories+unsubscribe@openinfosecfoundation.org <mailto:oss-advisories+unsubscribe@openinfosecfoundation.org>.
> 



  reply	other threads:[~2025-11-06 15:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAMYRET-TdKq7UMoMn37-BFQfhFOJgAr1V+GHX-DKsBOVqzfr9w@mail.gmail.com>
2025-11-06 15:22 ` Michael Tremer
2025-11-06 15:39   ` Adolf Belka [this message]
2025-11-06 15:40     ` 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=a67098ef-0f01-4d5e-adfe-b7000f56644f@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    --cc=michael.tremer@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