From: Michael Tremer <michael.tremer@ipfire.org>
To: "IPFire: Development-List" <development@lists.ipfire.org>
Subject: Fwd: Advance Notification of Suricata 8.0.4 and 7.0.15
Date: Tue, 17 Mar 2026 16:04:32 +0000 [thread overview]
Message-ID: <BE7B7EF1-37BB-47AE-AC8D-F78CE0FB1D22@ipfire.org> (raw)
In-Reply-To: <CAMYRET-jnK8MGL5QPfwmsLRHok7kNN8HLBqqQZDMtJSQD_d5LA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Hello,
Is anyone working on this one? It has already been released.
-Michael
> Begin forwarded message:
>
> From: Jason Ish <jish@oisf.net>
> Subject: Advance Notification of Suricata 8.0.4 and 7.0.15
> Date: 13 March 2026 at 16:04:28 GMT
> To: Jason Ish <jish@oisf.net>, Victor Julien <vjulien@oisf.net>
>
> Hello everyone,
>
> On Tuesday, March 17, 2026, we plan to release Suricata 8.0.4 and 7.0.15. These are security releases addressing multiple issues.
>
> For other issues fixed, please see:
> 8.0.4: https://redmine.openinfosecfoundation.org/versions/229 <https://redmine.openinfosecfoundation.org/versions/227>
> 7.0.15: https://redmine.openinfosecfoundation.org/versions/230 <https://redmine.openinfosecfoundation.org/versions/228>
> Regards,
> The OISF Team.
>
> --
> Jason Ish
> Open Information Security Foundation
>
> 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>.
[-- Attachment #2: Type: text/html, Size: 6078 bytes --]
next parent reply other threads:[~2026-03-17 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMYRET-jnK8MGL5QPfwmsLRHok7kNN8HLBqqQZDMtJSQD_d5LA@mail.gmail.com>
2026-03-17 16:04 ` Michael Tremer [this message]
2026-03-17 17:30 ` Matthias Fischer
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=BE7B7EF1-37BB-47AE-AC8D-F78CE0FB1D22@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