public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Pawan Badganchi" <badganchipv@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [kirkstone][PATCH v2] shadow: backport patch to fix CVE-2023-29383
Date: Fri, 09 Feb 2024 03:09:45 -0800	[thread overview]
Message-ID: <3891.1707476985725014543@lists.openembedded.org> (raw)
In-Reply-To: <13917.1707390777082340913@lists.openembedded.org>

[-- Attachment #1: Type: text/plain, Size: 596 bytes --]

Hi,
The issue does not seems to fix, getting below warning. Could you please check.

We are using this shadow library in our application.
When we compile our application we get below warning in log.do_prepare_recipe_sysroot

"configuration error - unknown item 'SYSLOG_SU_ENAB' (notify administrator)"
"configuration error - unknown item 'SYSLOG_SG_ENAB' (notify administrator)"

above warning is observed though below CVE is already available in our code kirkstone branch.

CVE-2023-29383 ( https://github.com/advisories/GHSA-p9w4-8hh8-crcx ).patch
0001-Overhaul-valid_field.patch.

[-- Attachment #2: Type: text/html, Size: 1699 bytes --]

  reply	other threads:[~2024-02-09 11:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19  6:17 [OE-core][kirkstone][PATCH v2] shadow: backport patch to fix CVE-2023-29383 Xiangyu Chen
2023-04-19 16:38 ` Steve Sakoman
2024-02-08 11:12   ` [kirkstone][PATCH " Pawan Badganchi
2024-02-09 11:09     ` Pawan Badganchi [this message]
2024-02-09 11:12       ` [OE-core] " Martin Jansa
2024-02-09 11:23         ` Pawan Badganchi
2024-02-12 13:02           ` Pawan Badganchi
2024-02-15 11:55             ` Pawan Badganchi
2024-02-26  5:14               ` Pawan Badganchi
2024-03-06  0:13                 ` [OE-core] " Fabio Berton
     [not found]                 ` <17BA048F79699A0A.32420@lists.openembedded.org>
2024-03-06 12:41                   ` Fabio Berton

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=3891.1707476985725014543@lists.openembedded.org \
    --to=badganchipv@gmail.com \
    --cc=openembedded-core@lists.openembedded.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