From: sanjayembeddedse@gmail.com
To: yocto@lists.yoctoproject.org
Cc: Martin.Jansa@gmail.com, Sanjay Chitroda <sanjayembeddedse@gmail.com>
Subject: [meta-security][PATCH] *.patch: fix CVE and Signed-off-by tag
Date: Sun, 2 Jul 2023 10:47:04 -0700 [thread overview]
Message-ID: <20230702174704.58235-1-sanjayembeddedse@gmail.com> (raw)
From: Sanjay Chitroda <sanjayembeddedse@gmail.com>
* as reported by openembedded-core/scripts/contrib/patchreview.py -v .
Missing Signed-off-by tag (./recipes-scanners/clamav/files/oe_cmake_fixup.patch)
Missing CVE tag (./recipes-security/ecryptfs-utils/files/ecryptfs-utils-CVE-2016-6224.patch)
Signed-off-by: Sanjay Chitroda <sanjayembeddedse@gmail.com>
---
recipes-scanners/clamav/files/oe_cmake_fixup.patch | 2 +-
.../ecryptfs-utils/files/ecryptfs-utils-CVE-2016-6224.patch | 4 +++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/recipes-scanners/clamav/files/oe_cmake_fixup.patch b/recipes-scanners/clamav/files/oe_cmake_fixup.patch
index c9c88b9..692be72 100644
--- a/recipes-scanners/clamav/files/oe_cmake_fixup.patch
+++ b/recipes-scanners/clamav/files/oe_cmake_fixup.patch
@@ -3,7 +3,7 @@ Issue with rpath including /usr/lib and crosscompile checkes causing oe configur
Use oe's cmake rpath framework and exclude some of the cmake checks that fail in our env
Upstream-Status: Inappropriate [configuration]
-Singed-off-by: Armin Kuster <akuster808@gmail.com>
+Signed-off-by: Armin Kuster <akuster808@gmail.com>
Index: git/CMakeLists.txt
===================================================================
diff --git a/recipes-security/ecryptfs-utils/files/ecryptfs-utils-CVE-2016-6224.patch b/recipes-security/ecryptfs-utils/files/ecryptfs-utils-CVE-2016-6224.patch
index a457d79..02105f5 100644
--- a/recipes-security/ecryptfs-utils/files/ecryptfs-utils-CVE-2016-6224.patch
+++ b/recipes-security/ecryptfs-utils/files/ecryptfs-utils-CVE-2016-6224.patch
@@ -14,9 +14,11 @@ the patch comes from:
https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2016-6224
https://bazaar.launchpad.net/~ecryptfs/ecryptfs/trunk/revision/882
-Upstream-Status: Backport
+CVE: CVE-2016-6224
+Upstream-Status: Backport [https://bazaar.launchpad.net/~ecryptfs/ecryptfs/trunk/revision/882]
Signed-off-by: Li Zhou <li.zhou@windriver.com>
+Signed-off-by: Sanjay Chitroda <sanjayembeddedse@gmail.com>
---
ChangeLog | 9 +++++++++
src/utils/ecryptfs-setup-swap | 10 ++++++++--
--
2.35.6
reply other threads:[~2023-07-02 17:47 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=20230702174704.58235-1-sanjayembeddedse@gmail.com \
--to=sanjayembeddedse@gmail.com \
--cc=Martin.Jansa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.