Yocto Project Discussions
 help / color / mirror / Atom feed
From: "Armpit" <akuster808@gmail.com>
To: yocto@lists.yoctoproject.org
Subject: [meta-security][zeus][PATCH 8/9] libhtp: bugfix only update 0.5.32
Date: Sun,  5 Jan 2020 15:18:29 -0800	[thread overview]
Message-ID: <20200105231830.5281-8-akuster808@gmail.com> (raw)
In-Reply-To: <20200105231830.5281-1-akuster808@gmail.com>

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
 recipes-ids/suricata/{libhtp_0.5.31.bb => libhtp_0.5.32.bb} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename recipes-ids/suricata/{libhtp_0.5.31.bb => libhtp_0.5.32.bb} (100%)

diff --git a/recipes-ids/suricata/libhtp_0.5.31.bb b/recipes-ids/suricata/libhtp_0.5.32.bb
similarity index 100%
rename from recipes-ids/suricata/libhtp_0.5.31.bb
rename to recipes-ids/suricata/libhtp_0.5.32.bb
-- 
2.17.1


  parent reply	other threads:[~2020-01-05 23:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05 23:18 [meta-security][zeus][PATCH 1/9] cryptsetup tpm incubator: fix installed vs shipped Armpit
2020-01-05 23:18 ` [meta-security][zeus][PATCH 2/9] meta-tpm/recipes-tpm2/tpm2-tss/tpm2-tss_2.3.1.bb: add new udev dir to FILES and append EXTRA_OECONF Armpit
2020-01-05 23:18 ` [meta-security][zeus][PATCH 3/9] checksecurity: use more portable find args Armpit
2020-01-05 23:18 ` [meta-security][zeus][PATCH 4/9] clamav: add tmpfiles.d config Armpit
2020-01-05 23:18 ` [meta-security][zeus][PATCH 5/9] suricata: " Armpit
2020-01-05 23:18 ` [meta-security][zeus][PATCH 6/9] README: update mailing list to new groups.io Armpit
2020-01-05 23:18 ` [meta-security][zeus][PATCH 7/9] libseccomp: upgrade 2.4.1 -> 2.4.2 Armpit
2020-01-05 23:18 ` Armpit [this message]
2020-01-05 23:18 ` [meta-security][zeus][PATCH 9/9] suricata: update to 4.1.6 Armpit

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=20200105231830.5281-8-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