From: "akuster" <akuster808@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: [meta-security][PATCH] suricata: update to 4.1.8
Date: Sun, 5 Jul 2020 18:40:31 +0000 [thread overview]
Message-ID: <20200705184031.20674-1-akuster808@gmail.com> (raw)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
recipes-ids/suricata/{libhtp_0.5.32.bb => libhtp_0.5.33.bb} | 0
recipes-ids/suricata/suricata.inc | 5 ++---
.../suricata/{suricata_4.1.6.bb => suricata_4.1.8.bb} | 0
3 files changed, 2 insertions(+), 3 deletions(-)
rename recipes-ids/suricata/{libhtp_0.5.32.bb => libhtp_0.5.33.bb} (100%)
rename recipes-ids/suricata/{suricata_4.1.6.bb => suricata_4.1.8.bb} (100%)
diff --git a/recipes-ids/suricata/libhtp_0.5.32.bb b/recipes-ids/suricata/libhtp_0.5.33.bb
similarity index 100%
rename from recipes-ids/suricata/libhtp_0.5.32.bb
rename to recipes-ids/suricata/libhtp_0.5.33.bb
diff --git a/recipes-ids/suricata/suricata.inc b/recipes-ids/suricata/suricata.inc
index 3adbcf6..c9dd9aa 100644
--- a/recipes-ids/suricata/suricata.inc
+++ b/recipes-ids/suricata/suricata.inc
@@ -2,8 +2,7 @@ HOMEPAGE = "http://suricata-ids.org/"
SECTION = "security Monitor/Admin"
LICENSE = "GPLv2"
-VER = "4.1.6"
+VER = "4.1.8"
SRC_URI = "http://www.openinfosecfoundation.org/download/suricata-${VER}.tar.gz"
-SRC_URI[md5sum] = "da5de1e8053f05cbd295793210117d34"
-SRC_URI[sha256sum] = "8441ac89016106459ade2112fcde58b3f789e4beb2fd8bfa081ffb75eec75fe0"
+SRC_URI[sha256sum] = "c8a83a05f57cedc0ef81d833ddcfdbbfdcdb6f459a91b1b15dc2d5671f1aecbb"
diff --git a/recipes-ids/suricata/suricata_4.1.6.bb b/recipes-ids/suricata/suricata_4.1.8.bb
similarity index 100%
rename from recipes-ids/suricata/suricata_4.1.6.bb
rename to recipes-ids/suricata/suricata_4.1.8.bb
--
2.17.1
reply other threads:[~2020-07-05 18:40 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=20200705184031.20674-1-akuster808@gmail.com \
--to=akuster808@gmail.com \
--cc=yocto@lists.yoctoproject.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