public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Fabio Berton <fbberton@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [kirkstone][PATCH v2] shadow: backport patch to fix CVE-2023-29383
Date: Wed, 6 Mar 2024 12:41:31 +0000	[thread overview]
Message-ID: <5f06f07b-fd27-4c84-b6e9-4d28123975ef@gmail.com> (raw)
In-Reply-To: <17BA048F79699A0A.32420@lists.openembedded.org>

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

Hi,


The error message is caused because the 
0001-Disable-use-of-syslog-for-sysroot.patch applied to the native 
recipe disables syslog support and the native tool does not recognize 
SYSLOG_SU_ENAB.

On 3/6/2024 12:13 AM, Fabio Berton via lists.openembedded.org wrote:
>
> Hi,
>
> I checked on kirkstone using OE-Core with DISTRO="nodistro" and when 
> running bitbake useradd-example I can see this:
>
> configuration error - unknown item 'SYSLOG_SU_ENAB' (notify administrator)
> configuration error - unknown item 'SYSLOG_SG_ENAB' (notify administrator)
>
> in the log.do_prepare_recipe_sysroot.
>
> The same happens without CVE-2023-29383.patch and 
> 0001-Overhaul-valid_field.patch patches. I didn't understand why the 
> SYSLOG_SU_ENAB is not supported.
>
> What is the correct approach here, remove SYSLOG_SU_ENAB and 
> SYSLOG_SG_ENAB from login.defs_shadow-sysroot?
>
> To use the useradd-example.bb was needed to add this change 
> https://lists.openembedded.org/g/openembedded-core/topic/kirkstone_patch/104757004
>
> Thanks
>
> On 2/26/2024 5:14 AM, Pawan Badganchi wrote:
>> Hi,
>>
>> Could please help here?
>>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#196655):https://lists.openembedded.org/g/openembedded-core/message/196655
> Mute This Topic:https://lists.openembedded.org/mt/98361235/6083838
> Group Owner:openembedded-core+owner@lists.openembedded.org
> Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub  [fbberton@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

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

      parent reply	other threads:[~2024-03-06 12:41 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
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 [this message]

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=5f06f07b-fd27-4c84-b6e9-4d28123975ef@gmail.com \
    --to=fbberton@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