3 ms·
First step: # Take ownership of /usr/local so you don't have to sudo sudo chown -R `whoami` /usr/local Hell no, bad idea, do not want.
by pquerna 17y ago
First step:
# Take ownership of /usr/local so you don't have to sudo
sudo chown -R `whoami` /usr/local
Hell no, bad idea, do not want.
- jrockway 17y agoYeah, now an attacker will be able to delete the binaries you downloaded from the Internet, in addition to all of your personal files. If your single-user system is compromised to the point where it matters what files you can and can't write, you've already lost. And the "low hanging fruit" in this attack scenario was the files you actually cared about. (Also, this is a dupe of the top-rated comment. Maybe read one comment before replying?)
- JadeNB 17y ago> single-user system Am I missing something in the grand-parent that suggests that his is a single-user system? Even if it is the case, then, as you pointed out elsewhere (http://news.ycombinator.com/item?id=1096327 http://news.ycombinator.com/item?id=1096327), the solution's still sub-optimal: better `~/bin` than `/usr/local` (right?).
- deleted 17y ago[deleted]
- rufo 17y agoPut it in a directory in your home folder instead. (Also: this doesn't address the security concerns, but by default on a clean install of SL there is no /usr/local, so you're really not hurting anything.)