From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Fwd: Advance Notification of Suricata 7.0.8
Date: Thu, 12 Dec 2024 18:08:28 +0100 [thread overview]
Message-ID: <085abcc2-5a82-4043-a195-1d42515af800@ipfire.org> (raw)
In-Reply-To: <D62E38E2-23D0-483D-ADAE-FE1BAA63DAEE@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
Hi Michael,
On 12/12/2024 17:53, Michael Tremer wrote:
> It is out, would anyone like to grab this?
>
I will pick it up, no problems.
> Looking at the security fixes, we might want to rebuild c190 for this:
>
> https://github.com/OISF/suricata/blob/97e69ffb1bc2b7358115ee59f460a924893664e8/ChangeLog
>
Oh wow. Yes that doesn't look so healthy from the security point of view.
Regards,
Adolf.
> -Michael
>
>> Begin forwarded message:
>>
>> *From: *Jason Ish <jish(a)oisf.net>
>> *Subject: **Advance Notification of Suricata 7.0.8*
>> *Date: *11 December 2024 at 19:08:13 GMT
>> *To: *Victor Julien <vjulien(a)oisf.net>, Jason Ish <jish(a)oisf.net>
>>
>> *
>> Hello everyone,
>>
>> On Thursday, December, 12 we plan to release Suricata 7.0.8. This is a bug-fix and security release addressing several issues.
>>
>> For other issues addressed in this release please see: https://redmine.openinfosecfoundation.org/versions/214
>>
>> Please note that Suricata 6.0.x went end of life on August 1st, 2024 and there will be no more security or bug fix releases.
>> Regards,
>> The OISF Team
>> *
>>
>> To unsubscribe from this group and stop receiving emails from it, send an email to oss-advisories+unsubscribe(a)openinfosecfoundation.org.
>
next parent reply other threads:[~2024-12-12 17:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D62E38E2-23D0-483D-ADAE-FE1BAA63DAEE@ipfire.org>
2024-12-12 17:08 ` Adolf Belka [this message]
2024-12-12 17:28 ` 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=085abcc2-5a82-4043-a195-1d42515af800@ipfire.org \
--to=adolf.belka@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