public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jason Taylor <jtfas90@proton.me>
To: git-commits@fedoraproject.org
Subject: [rpms/suricata] f43: upstream security/bugfix release
Date: Sun, 02 Aug 2026 02:38:48 GMT [thread overview]
Message-ID: <178563832855.1.1336717805965572821.rpms-suricata-a402886d9dd4@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/suricata
Branch : f43
Commit : a402886d9dd47ff11bd87cd8ac726d4b0a17b483
Author : Jason Taylor <jtfas90@proton.me>
Date : 2026-08-01T22:38:05-04:00
Stats : +6/-2 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/suricata/c/a402886d9dd47ff11bd87cd8ac726d4b0a17b483?branch=f43
Log:
upstream security/bugfix release
---
diff --git a/.gitignore b/.gitignore
index 3e19940..26aff24 100644
--- a/.gitignore
+++ b/.gitignore
@@ -97,3 +97,4 @@ suricata-1.0.0.tar.gz.sig
/suricata-7.0.13.tar.gz
/suricata-7.0.15.tar.gz
/suricata-7.0.16.tar.gz
+/suricata-7.0.17.tar.gz
diff --git a/sources b/sources
index e000258..bc6e376 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (suricata-7.0.16.tar.gz) = 2fa908e324fd28f9fc68f9ed35062b43681cfcacf331839b54e3e2741e9c9cc569f2e150c9fdc2bcaf162c552f9b458173dbc7b1b715e7fc035fe4bbabeb5652
+SHA512 (suricata-7.0.17.tar.gz) = a0c67e31d10fae685b36bcda0be1450264dbb2de148e8599cb342ad007eddd3e309c426d15a9f59f333537aec1ab45b0a65a3c71b91a08aa17046fc9b623f184
diff --git a/suricata.spec b/suricata.spec
index fa8eaaa..1d99622 100644
--- a/suricata.spec
+++ b/suricata.spec
@@ -1,6 +1,6 @@
Summary: Intrusion Detection System
Name: suricata
-Version: 7.0.16
+Version: 7.0.17
Release: 1%{?dist}
License: GPL-2.0-only
URL: https://suricata.io/
@@ -205,6 +205,9 @@ fi
%endif
%changelog
+* Sat Aug 1 2026 Jason Taylor <jtfas90@proton.me> 7.0.17-1
+- Upstream bugfix/security release
+
* Sat May 23 2026 Jason Taylor <jtfas90@proton.me> 7.0.16-1
- Upstream bugfix/security release
reply other threads:[~2026-08-02 2:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178563832855.1.1336717805965572821.rpms-suricata-a402886d9dd4@fedoraproject.org \
--to=jtfas90@proton.me \
--cc=git-commits@fedoraproject.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