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 7.0.11
Date: Tue, 8 Jul 2025 17:56:37 +0200 [thread overview]
Message-ID: <d8a913a7-9d81-4ee8-9725-0d53aa3c8474@ipfire.org> (raw)
In-Reply-To: <947E2631-E7AC-4D78-9DBE-6DC8DFD29CBA@ipfire.org>
I will pick it up.
Regards,
Adolf.
On 08/07/2025 17:50, Michael Tremer wrote:
> Is anyone happy to grab this one?
>
>> Begin forwarded message:
>>
>> *From: *Jason Ish <jish@oisf.net>
>> *Subject: **Advance Notification of Suricata 7.0.11*
>> *Date: *4 July 2025 at 17:49:10 BST
>> *To: *Victor Julien <vjulien@oisf.net>, Jason Ish <jish@oisf.net>
>>
>> Hello everyone,
>>
>> On Tuesday, July 8, 2025 we plan to release Suricata 7.0.11. This is a bug-fix and security release addressing a few issues.
>>
>> This release will include a minor update to libhtp: 0.5.51
>>
>> For other issues addressed in this release, please see: https://redmine.openinfosecfoundation.org/versions/219 <https://redmine.openinfosecfoundation.org/versions/219>
>>
>> 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>.
>
next prev parent reply other threads:[~2025-07-08 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMYRET_S89cm0f19-aZ9psexTcQdQED_KSR-b2Zfd+6Manp00g@mail.gmail.com>
2025-07-08 15:50 ` Michael Tremer
2025-07-08 15:56 ` Adolf Belka [this message]
2025-07-08 16:04 ` Adolf Belka
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=d8a913a7-9d81-4ee8-9725-0d53aa3c8474@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