933
Just a PSA
(lemmy.zip)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Dec 2023
933 points (98.0% liked)
linuxmemes
19717 readers
422 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
Let me rephrase my question:
Why would I not want to open nano as root?
No offense, but that sounds like more OCD behavior. ๐ I don't need or want protection against myself, and I even loath the whole "that's not how you're supposed to do it"-mentality of linux (where when commands know very well what you want, instead of doing it, just tell you you forgot something). ๐
It's probably to protect against any potential security vulnerabilities in the text editor program itself, not to protect you from yourself.
Wouldn't that logic count for anything, including sudo itself?
Sure, but sudo is specifically designed with security in mind as a security program, whereas text editors are not (although I am more likely to trust vim than vscode). Running a malicious program as the user and not as root can help mitigate the impact it could do, even though it will still be able to do a lot as a user.
You assume this malicious code is lame enough not to gain root itself with a modified su.
What do you mean get root itself with a modified su? A program that has been run as a user cannot just get root permissions, that's called a privilege escalation attack and is a serious vulnerability in the kernel which gets fixed quickly when found.
Any attack is usually non-intended vulnarabilities. Same argument applies to any software, like nano, if it can open doors to your system.
Of course it applies to any software, but some programs are more vulnerable than others. For example, when you want to have cryptography in your program, you use an established library, not write the algorithms yourself, because those libraries were written with security in mind (i.e. have protections against different kinds of attacks, for example, side channel attacks, in addition to being implemented properly). The whole point is to minimize the surface of attack, so that your system is more secure. And one way of doing so is to not give root permissions to programs that don't need it (such as text editors like nano).
Yeah, well, as you said: it's probably fixed by now, but I used to have a universal su that would work on any armv7 linux (so basically every phone back then, but also on my armv7 little laptop I had at the time...) with which I was able to easily root any phone by putting it in /data/local and making it bootable, then using full path to move any Android root files in place (though I did also just copy that su itself to /system/bin for root on cheaper phones sometimes, which is just playing with fire as it basically makes any root action unseen and allowed. ๐). That did work for years though, but that's probably cause Android minimizes the linux and never actually updated the kernel so much, and the laptop's flashed OS was something altered with also very little updates. And ARM was still quite new to the public too. ๐คทโโ๏ธ
I remember I came across it in the rooting package for my Kindle Fire and only found out it could do that by accident,... ๐ It couldn't change user, though, it had only 1 use without parameters, which resulted as if you do a 'sudo su' if you remove the sudo password-requirement.
Hence why I used the example. I wasn't being limitative to it, though. There's so many things that could screw you if it has a vulnerability, if it happens I very much doubt it'll be through nano, though.