Thanks for the prompt reply!
Well, I can say two things:
1) I'm installing a whole new guix over the old one -- I'm still
trying Guix out -- so, I can't look inthere any more. (not sure if
that was smart)
2) I didn't add a `(setuid-programs ...)` to the config; I tried
to afterwards, but that pesky error wasn't allowing me to
reconfigure. So perhaps this was the culprit.
What I can do, I can recreate my setup and see I get the error
again and report back.
Still, why wasn't I able to go back to a working config? That just
seems contrary the "transactional" concept, because my first
installation worked. I suppose user ownership persists as in a
regular linux system. If this is the case, would this be a
security issue? right now, it so far is only a nuisance.
On 2024-02-19 at 21:40, Carlo Zancanaro <[email protected]>
wrote:
Hi Mauritz,
I don't know that I can help solving your problem, but I do have
one
relevant thing to add.
On Mon, Feb 19 2024, Mauritz Stenek wrote:
Now, however, running a program with sudo ... throws this error
sudo: /run/current-system/profile/bin/sudo must be owned by
uid 0 and have the setuid bit set
I get this on my servers when I try to run a command directly
through
ssh, but when I login I can run sudo fine. The key difference in
my case
is PATH. It only works when PATH contains /run/setuid-programs/.
Can you check whether your PATH has /run/setuid-programs/? If
not, can
you try running the sudo binary from there, rather than the one
in the
system profile?
I haven't had a change to investigate why this is occurring for
me, so I
can't give you a real solution, but hopefully this can get you
somewhere.
Carlo
--
Mauritz Stenek <[email protected]>
