Hacker News Reader

Comment by deadbunny | Hacker News Reader

So let's just set everything to 777? /s

All I am saying is that security is like onion layers, and unix permissions are the last layer probably. If the attacker penetrated through all the other layers, chances are that unix permissions will not save you.

google.com/search?q=defense+in+depth

Former pentester here. It was often the case that we were able to penetrate a box as a low-level user account, and the way we escalated was to search ~/.bash_history of an admin account.

chmod'ing the homedir would've prevented that. Unix happens to be pretty good about directory permissions.

The .bash_history file is mode 0600, regardless of directory permissions. Was this not always the case?

Heh. Looks like I’ve been out of the game longer than I thought. It’s suddenly been 6 years.

Welp. Yes, I misremembered that specific example.

Still, you’d be amazed how often people leave json credentials in their homedir that can be used to pivot to e.g. S3.

The number of bash history files with accidental passwords pasted into them is quite high.

Another reason I don’t sudo and instead ssh

Shell history files for admin accounts should be disabled (or at least kept short) for this reason.

But I really really like shell history files if I have to come behind someone!

Interesting idea - make it so all your passwords start with the same four characters (say Ab54) - (it's hard to get good passwords you can safely type at a prompt anyway) and then have a script that searches your history/log files for strings beginning with the Ab54 characters and replacing them with XXXX or similar.

All sorts of horrible side effects can immediately be identified.

Reply on news.ycombinator.com