
post
But those are different
Yeah, not only does +x leave read/write permissions untouched, it also only makes it executable for the user, not for everyone and their cat.
Cat doesn't execute anything tho, it just reads and gives output
The cat command executes the cat program.
Except if you use kitty terminal emulator with unsecure remote access. Issue
Then with cat, you could execute arbitrary commands...
If your cat isnβt the first entry in /etc/sudoers Iβm not sure I want to know you
When I start fucking with chmod, it happens way too often that what I want to do only works after I executed chmod 777...
If you don't add the leading digit (out of respect) for the sticky/setgid/setuid bits, do you even Linux?
700 cause Iβm selfish.
700 is the only sane answer for directories inside $HOME.
Nah, thereβs a lot of config files in there that other programs need to read.
Unfortunately. I really wish $HOME was reserved for files I create myself. I know. I can create my own shit for that. But, I really wish every single random project I download to fuck around with didn't drop a config directory or file in there. ITS MY HOME.
I mean, having config files in there makes a lot of sense. It allows you to move your home to some other machine/install and immediately feel at home, because everything is configured to your liking.
Now, the fact that many apps create their own directory instead of putting their stuff in ~/.config is pretty annoying.
Yeah. That's more my frustration. That it's implented poorly by most people. I don't think that trying to change the standard by "adding another standard" would be helpful. Just minor frustration. Which usually leads me to putting all my organized directories and shit in a dedicated location. And I just let /home be the clutter that it is.
Also for multi user systems it's handy that each user gets their own configs
chmod -R 600 ~/, because I dont trust anyone, not even myself.
I forgor the tilde and its taking a long time. wat do
Nope, +x for life
I don't use chmod nearly often enough to remember these numbers. I know there's a mathematical way to figure it out, but I cba to do that when u+wrx more or less tells me exactly what it does (grant the User Write, Read, and eXecute permissions)
chmod 755 for when setting permissions to directories. chmod +x for making something executable right when I am about to run it.
chmod -R ug+rwX,o=r *
u=rwX,g=rX,o=rX because this won't make every file executable, only folders.
real question is how do you pronounce chmod
not giving a fuck about proper file perms is fine as long as its not a server

top 50 comments