Did you switch from insecure sudo to run0 yet, anon?
>>106965381Redhat pottering can suck my dick
>>106965434he literally works for microsoft, yet redhat gets all the praise for systemd's success
>>106965381Didn't this fuck ruined Linux with his systemd shit and then ran to Microsoft?
>>106965381I'm tempted to switch back to su - -c desu.
This is a fundamental problem with Unix systems: needing a "root" user who can do everything.
>>106965538System administration is impossible without this. You're a moron.
>>106965538>needing
>>106965381>pedo bear as the profile picture
>>106965576Real operating systems can give users authorization to specific things without forcing them to be or become a "root" user.
>>106965625Oh yeah, and how would you grant that permission to a user without also having all permissions as well?
>>106965538Doesn't Windows basically do the exact same thing with Administrator accounts and UAC?
>>106965625What are those real operating systems? Android? You can't do shit because of how limited your access is. Windows? You run as a "root" user 24/7.
>>106965381Shut the fuck up Lennart
>>106965381I'm dumping any distro that removes sudo
>>106965625>give users authorization to specific thingsThis is exactly what sudo does. Just because you have ALL=(ALL:ALL) ALL in your sudoers doesn't mean that it's supposed to be like that.
>>106965381This seems weird to me. Almost like systemd is a backdoor
>>106965926Then it's not bad, but most people just have normal users with normal privileges vs root who can do anything instead of specific users with additional authorization and privileges.
>>106965625>give users authorization to specific things without forcing them to be or become a "root" user.That's exactly what sudo does, you nuclear dipshit.
suid isn't a big deal. Having a large number of suid binaries is a bad idea, but having a single program that is known to be well written and needs suid for it's core functionality isn't an issue. There are only a few issues eg env vars that specifically relate to being suid, instead of being exposed by any program that lets unprivileged users control a root process. Eg any time a user can tell a root program to write a file you have to make sure it won't overwrite /etc/passwd. This really has nothing to do with suid, but it's frequently discovered in random programs that only need suid for some incidental functionality. Replacing sudo with something simpler is a good idea, run0 is a crap replacement that adds a bunch of security theatre for no benefit. I was on board, because I have systemd anyways I might as well let it handle sudo, until I discovered that.
>>106965381>OpenBSDs sudo replacement called doasBut sudo is also still an OpenBSD project
>>106965625Haha, why are you here?
