If I’m using the CLI, it tends to be for things that require root access. Can’t properly skull fucm my system without root
sudo wineTell this to my cousin (though he probably does this to gaslight me).
Blasphemy!!!
Don’t need sudo if you’re always root.
Now excuse me. I need to call the bank and find out why my checking account is suddenly $0.
And yet half the time when I’m root I preface with sudo. I can’t stop myself!
root ~# sudo fdisk -l
I normally disable root, so I don’t think su would work. Never tried, so maybe I am using it wrong.
I once did a HackTheBox where the privilege escalation weakness was a cronjob running a script. I’m not sure if I correctly remember all the details, but I think it read some parameters from a file and fed them to some other script. Since it had something to do with the webserver the user was administrating, they needed write access to the file, granted via ACL. That took me a while to spot, actually. Not sure why, but ACL is a constant blind spot for me. As for passing the parameters, you can just append the contents of the file to the command and pipe it to bash.
I don’t recall what the normal script did, but it needed writing permissions for something. The proper way to do this would be ACL, but I guess I’m not the only one with a blind spot. The easy way to ensure the script can do whatever it needs to is to
sudothe whole thing.So what do you do if you have a script running every ten minutes, reading the first line of a file you can edit, then executing it with superuser privileges?
Whatever the fuck you want.
Huh. I might need to take a peek at one of my cronjobs now. 😂
You mean we shouldn’t have a ‘while true; eval $file’ job running as root??? Goddammit, someone help me fix my remote admin script!!!
Sudo !!
👌👌👌 perfection
I came here to look for this.
IMO the “year of the Linux desktop” will come when distros are designed for people who shouldn’t even be allowed to use sudo.
Let me introduce you to atomic distros.
I moved my father on Bluefin 1.5 years ago from his antique MacBook Air. He doesn’t know
sudoexists. He has never heard ofujust. He doesn’t even command line. He hasn’t had to do a single update because it all happens in the background. He just… uses it.doesn’t even have to be atomic, I rescued my wife’s shit laptop using Ubuntu Mate (snaps booing in background) and she has never seen the command line unless I open it. It’s been like that for over a year at least.
Yes, but contrary to atomic distros, it’s not explicitely designed to be as administration free as possible.
Yeah I only use sudo once, for the su.
Straight to jail.
… but why? “sudo -i” is a thing. Why get another program involved?
Some people just want to watch the world burn.
Some people think before they type. They also do not think mindlessly typing “sudo” before every fucking line in bash is a valid substitute for knowing what they do. Many of them have been doing so for decades on HPUX, Solaris, BSDs and IRIX on their own and other people’s/companies machines, not just on their single bedroom machine.
I don’t think many people know about this feature
Personally it’s because my fingers are already on “s” and “u”.
It’s easier to just call su once and run every single command as root rather than having to randomly use sudo for some commands and not for others (/s if it’s not obvious)
But you can do that without involving ‘su’.
I don’t use sudo.
Ever.
It’s disabled by default in slackware, and I don’t know why it’s even there.Tell me how you can run rm rf / no preserve root without su, I’m waiting.
Is this some kind of joke going over my head or something?
Run “sudo -i” then run “rm -rf --no-preserve-root”
Yeah I’m just joking around. I pretty much never use su except in rare cases
I just delete every user but root.
How else will the OS know I’m serious ?
“Yes, Do as I say!”
doas
Shut the front door!
In a lot of situations it’s actually bad to use sudo because it can impact settings that make programs or file ownership go to root instead of the user.
sudo -i -u user -s /usr/bin/bashmakepkg won’t even run as root iirc
You’ve got to be a damn idiot jumping over his own shadow to get that done. How would you even do that? Running
chown -R root.rootover directories or mount points? Deleting files in /dev or /run and recreating them using “touch” without looking up ownerships before? I wrote “touch” because anyone proceeding to “mknod” would at least have read some man pages. BTW, you’d need su for that rather than sudo.
fakesudo exists for a reason
