Error: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid

berat703 · 2018-03-25 14:46:47

Hello everyone.

I got this error when i use sudo.I installed nodejs after i did a

 sudo chown -R $(whoami) $(npm config get prefix)/{lib/node_modules,bin,share}

to allow for npm install -g without needing sudo.

Then i got " sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set " error

 ls -l /usr/bin/sudo

print this

 
-rwsr-xr-x 1 arc root 132408 Oca 21 19:06 /usr/bin/sudo

ewaller · 2018-03-25 14:52:20

How did the owner of sudo become arc?
Use su to start a root shell (you will need the root password). As root, change the ownership of sudo back to root. Exit the root shell with ctrl-d.
Don't do this again

Slithery · 2018-03-25 14:54:52

Welcome to the forums berat703

What on earth led you to believe that the first command you ran was a good idea?
You might be able to recover by logging in as root and running...

chown -R root /usr/{lib/node_modules,bin,share}

eschwartz · 2018-03-25 15:14:06

This happened because the nodejs programming language is a toxic environment that habitually suggests you mutilate your operating system for the sake of npm's convenience...

Fun fact: recently npm had a bug where they ran that chown command for you automatically if you used npm via sudo: https://github.com/npm/npm/issues/19883

They fixed it quite fast and issued an emergency patch release. Unfortunately no one can create a patch release for the many morons on the internet who suggest doing this manually and by offering this bad advice cause many people to inadvertently break their systems.

Oh well, now you know not to do that again. Have fun reinstalling your Arch Linux installation.

Slithery: simply chowning everything to root is not a solution, as there are files which are owned by different users. I wouldn't want to guarantee that this will catch everything even though it didn't also mutilate /var

OTOH with some care one might be able to use paccheck (from pacutils) to triple-check the ownership of all files on the system. At least the OP's command did not modify the group as well as the owner as many files e.g. commands in /usr/bin use setgid to run as some special per-software system user...

Last edited by eschwartz (2018-03-25 15:17:38)

berat703 · 2018-03-25 16:59:39

Slithery wrote:

Welcome to the forums berat703
What on earth led you to believe that the first command you ran was a good idea?
You might be able to recover by logging in as root and running...
chown -R root /usr/{lib/node_modules,bin,share}

i'm glad to be here .Thank you .

I tried this code then print is

 
-rwxr-xr-x 1 root root 132408 Oca 21 19:06 /usr/bin/sudo

But if arc user write "sudo su" , the error display again.

Last edited by berat703 (2018-03-25 17:05:02)

berat703 · 2018-03-25 17:03:38

Eschwartz wrote:

This happened because the nodejs programming language is a toxic environment that habitually suggests you mutilate your operating system for the sake of npm's convenience...
Fun fact: recently npm had a bug where they ran that chown command for you automatically if you used npm via sudo: https://github.com/npm/npm/issues/19883
They fixed it quite fast and issued an emergency patch release. Unfortunately no one can create a patch release for the many morons on the internet who suggest doing this manually and by offering this bad advice cause many people to inadvertently break their systems.
Oh well, now you know not to do that again. Have fun reinstalling your Arch Linux installation.
Slithery: simply chowning everything to root is not a solution, as there are files which are owned by different users. I wouldn't want to guarantee that this will catch everything even though it didn't also mutilate /var
OTOH with some care one might be able to use paccheck (from pacutils) to triple-check the ownership of all files on the system. At least the OP's command did not modify the group as well as the owner as many files e.g. commands in /usr/bin use setgid to run as some special per-software system user...

You are definitely right for all your said.Especially about in npm.So i don't wanna reinstall OS.Have i another way this problem's solution?

loqs · 2018-03-25 17:32:20

berat703 wrote:

Eschwartz wrote:
Oh well, now you know not to do that again. Have fun reinstalling your Arch Linux installation.
OTOH with some care one might be able to use paccheck (from pacutils) to triple-check the ownership of all files on the system. At least the OP's command did not modify the group as well as the owner as many files e.g. commands in /usr/bin use setgid to run as some special per-software system user...
You are definitely right for all your said.Especially about in npm.So i don't wanna reinstall OS.Have i another way this problem's solution?

Emphasis added

seth · 2018-03-25 17:49:03

berat703 wrote:

But if arc user write "sudo su" , the error display again.

 ... and have the setuid bit set ..

chmod u+s /usr/bin/sudo

Still run paccheck - and purge npm....

berat703 · 2018-03-25 18:41:05

seth wrote:

berat703 wrote:
But if arc user write "sudo su" , the error display again.
 ... and have the setuid bit set ..
chmod u+s /usr/bin/sudo
Still run paccheck - and purge npm....

It's worked! Thanks!

Arch Linux

#1 2018-03-25 14:46:47

Error: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid

#2 2018-03-25 14:52:20

Re: Error: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid

#3 2018-03-25 14:54:52

Re: Error: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid

#4 2018-03-25 15:14:06

Re: Error: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid

#5 2018-03-25 16:59:39

Re: Error: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid

#6 2018-03-25 17:03:38

Re: Error: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid

#7 2018-03-25 17:32:20

Re: Error: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid

#8 2018-03-25 17:49:03

Re: Error: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid

#9 2018-03-25 18:41:05

Re: Error: sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid

Board footer