7 ms·
Just on your first suggestion, this also means that if a person or process can drop a file (unknown to you) into your ~/bin/ then they can wreak havoc. Eg they
by alance 7mo ago
Just on your first suggestion, this also means that if a person or process can drop a file (unknown to you) into your ~/bin/ then they can wreak havoc. Eg they can override `sudo` to capture your password, or override `rm` to send your files somewhere interesting, and so on.
Btw on the second suggestion, I think there's a command named `command` that can help with that sort of thing, avoids recursive pitfalls.
- znpy 7mo agoWhile true, what you describe is very unlikely to happen and most definitely won’t happens on systems where i’m the only users.
- functionmouse 7mo agoThat would require someone to already want to sabotage me in particular, learn my private workflows, and also have write access to my home folder. At that point, All is Lost. Don't tell people to sacrifice agency for apocalypse insurance that doesn't work, lol
- latexr 7mo agoIf someone can drop a file in your ~/bin, they can also edit your shell’s startup files to add their malicious command.
- wtetzner 7mo agoI think it's already game over if they have access to your home directory. They can also edit your path at that point.
- dieulot 7mo agoThe issue of rootless malicious command overrides is solved by typing the whole path, such as "/bin/sudo".
- mathfailure 7mo agoNo, don't do that as a precaution. As others have already answered correctly - it's too late to worry about such things if a malicious agent has write access to your ${HOME} dir.