pseudo issue in kirkstone

pseudo issue in kirkstone

[Belisko Marek]

Hi,

I have a class where I create a custom image with cryptsetup and for
that purpose I'm using sudo. AFAIK using sudo in image creation should
be OK as it runs in pseudo. sudo calls works fine in dunfell releases
but while on kirkstone I'm getting:

| sudo: error in /etc/sudo.conf, line 0 while loading plugin "sudoers_policy"
| sudo: /usr/lib/sudo/sudoers.so must be owned by uid 0
| sudo: fatal error, unable to load plugins

Is there any workaround available or it's a pseudo issue?

Thanks and BR,

marek

-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com

Re: pseudo issue in kirkstone

[apoplawski]

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

Hi,

I have a similar problem. First, you need to disable pseudo before executing.
On begin of the line containing sudo cryptsetup add environment variable
definition: PSEUDO_DISABLED=1. This, however, does not solve the problem
of executing sudo. I've noticed from the recipe point of view, all files you don't own
are nobody:nogroup. This happens whether the task is in fakeroot or not.

--
Adam Popławski

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

Re: [yocto] pseudo issue in kirkstone

[Belisko Marek]

Hi,

On Wed, Nov 23, 2022 at 9:41 AM apoplawski via lists.yoctoproject.org
<apoplawski=kan-therm.com@lists.yoctoproject.org> wrote:
>
> Hi,
>
> I have a similar problem. First, you need to disable pseudo before executing.
> On begin of the line containing sudo cryptsetup add environment variable
> definition: PSEUDO_DISABLED=1. This, however, does not solve the problem
> of executing sudo. I've noticed from the recipe point of view, all files you don't own
> are nobody:nogroup. This happens whether the task is in fakeroot or not.
OK so adding PSEUDO_DISABLE=1 doesn't solve an issue. It's the same like before.
Any idea what was changed and why it was working in dunfell and not in
kirkstone?
>
> --
> Adam Popławski
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#58622): https://lists.yoctoproject.org/g/yocto/message/58622
> Mute This Topic: https://lists.yoctoproject.org/mt/95191553/900721
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [marek.belisko@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

BR,

marek
-- 
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com

Re: pseudo issue in kirkstone

[apoplawski]

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

On Wed, Nov 23, 2022 at 10:25 AM, Marek Belisko wrote:

> 
> Hi,
> 
> On Wed, Nov 23, 2022 at 9:41 AM apoplawski via lists.yoctoproject.org
> <apoplawski=kan-therm.com@lists.yoctoproject.org> wrote:
> 
>> Hi,
>> 
>> I have a similar problem. First, you need to disable pseudo before
>> executing.
>> On begin of the line containing sudo cryptsetup add environment variable
>> definition: PSEUDO_DISABLED=1. This, however, does not solve the problem
>> of executing sudo. I've noticed from the recipe point of view, all files
>> you don't own
>> are nobody:nogroup. This happens whether the task is in fakeroot or not.
> 
> OK so adding PSEUDO_DISABLE=1 doesn't solve an issue. It's the same like
> before.

In my case, adding PSEUDO_DISABLE=1 makes /etc/sudoers.conf problem go away.
However, I am left with an error about running sudo:

| sudo must be owned by uid 0 and have the setuid bit set

I think main problem is ownership of files in task perspective. I don't know why files are nobody:nogroup.
I spent some time on that but not found solution.

> 
> Any idea what was changed and why it was working in dunfell and not in
> kirkstone?
> 
>> --
>> Adam Popławski
> 
> BR,
> 
> marek
> --
> as simple and primitive as possible
> -------------------------------------------------
> Marek Belisko - OPEN-NANDRA
> Freelance Developer
> 
> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> Tel: +421 915 052 184
> skype: marekwhite
> twitter: #opennandra
> web: http://open-nandra.com

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