5 ms·
An important safety note about chown and symlinks (also chmod and chgrp)
- mehrdadn 7y agoRelated pro tip that no one ever explained to me: In POSIX commands (like 'find'), -P means perform this operation on the physical hierarchy. (What does that mean? Physical stuff can't be recursive. So that implies symlinks aren't dereferenced.) -L means perform it on the logical hierarchy (i.e. where links are followed), and -H (not sure what it might stand for? hard links?) behaves like -P during recursion and like -L at the top level. Unfortunately these don't explain what happens on mount points. Turns out there's also sometimes a -x or -xdev option (on Linux at least) that means "don't go across mount points". So on a command like 'find' on Linux, you probably always want -xdev in addition to -P.
- jackewiehose 7y ago> So on a command like 'find' on Linux, you probably always want -xdev in addition to -P. No, why? A default of -P is fine but a default of -xdev would mean you couldn't search everything like find / ... edit: Not sure where you got "physical" hierarchy. Here is the debian explanation of -P: -P Never follow symbolic links. This is the default behaviour. When find examines or prints information a file, and the file is a symbolic link, the information used shall be taken from the properties of the symbolic link itself.
- mehrdadn 7y agoDo you really want to go down /dev and /proc and /mnt mounts with find /?
- BenjiWiebe 7y agoI do want to go down /mnt, /home and /var.
- mehrdadn 7y agoThen you can add them explicitly. And what about /proc and /dev? And /sys? And /run? You usually know which mounts you want to go into, but don't have a list of every single one you want to stay out of. Most people want a whitelist here, not a blacklist.
- the_pwner224 7y agoMost people don't want to give a thought to whitelists or blacklists, they just want to find the files relevant to them. Most people are using grep or another command piped from find, and doing 'sudo find /' (sudo to get rid of all the errors from /proc) is the easiest way to search everything. 99% of the time sys and proc and run and all that stuff won't even show up in the filtered results, and if something does, its an easy 'grep -v ^/sys' to exclude.
- colinhb 7y ago> Not sure where you got "physical" hierarchy. Here is the debian explanation of -P: What's the relationship between the letter P and the behavior of the option -P? Same for the letter L and the behavior of -L, and the letter H and the behavior of -H? That's the point the parent is making.
- yread 7y agoWhy would you do find / ... instead of locate ... ?
- usefulcat 7y agoProbably either because the locate database could be out of date, or because you want to do any number of things that find can do that locate can't (-mtime, -executable, -fstype, -links, etc).
- pnutjam 7y agoLocate requires a database that needs to be updated. Find does an actual search of the system.
- mehrdadn 7y agoI would be terrified if you wrote a script that used locate in place of find.
- userbinator 7y agoH is for Hybrid.
- mehrdadn 7y agoAhhh! Thank you.
- marcosdumay 7y agoMy system's manpage explains it as "half-logical".
- hacker_newz 7y agoThis isn't a safety note, it's a warning not to use flags that you don't fully understand.
- jackewiehose 7y ago-flags+commands I can say I've never heard of -h/-H and never thought much about symlinks vs. chmod and I never had a problem with it because I've never thought that a symlink can have its own permission (I didn't even know such systems exist). So for me the default of -H is fine.
- recursive 7y agoWhy is it not both?
- gruez 7y ago>it's a warning not to use flags that you don't fully understand. and how many people were told to do chown -R from stackoverflow?
- jlgaddis 7y agoI suppose people blindly following suggestions on the Internet will eventually learn a hard lesson -- don't. Corollary: Learn to RTFM. Unless you've went out of your way to avoiding installing the documentation (man pages, etc.), all the answers you need (well, most of them) are right there on your own system.
- loopz 7y agoThere should be sane defaults though, instead of expecting everyone to have to learn the same thing.
- greglindahl 7y agoUnix is user-friendly. It also has high expectations of its users.
- deleted 7y ago[deleted]
- jlgaddis 7y agoFrom a follow-up article [0]: > As it happens, I was mistaken about some aspects of the situation with chown. --- [0]: https://utcc.utoronto.ca/~cks/space/blog/sysadmin/ChownSymlinkSafetyII https://utcc.utoronto.ca/~cks/space/blog/sysadmin/ChownSymli...
- philsnow 7y agoThe article doesn't say what to do if you only have gnu chmod. find dirname \! -type l -exec chmod a+r {} \; Could do what you want. Maybe there should be more exclusions? Are symlimks the only dangerous thing?
- wicket 7y agoI found it interesting to compare the four chown manuals (POSIX, GNU, FreeBSD and OpenBSD) and can see why the author may have been confused about the -h switch. The POSIX manual is the only one that explicitly states that -h applies to each file operand (as opposed to files encountered during the traversal from -R). The SYNOPSIS section also makes it clear how it differs. FreeBSD kind of gets it right, but without the word "operand" it could easily be misinterpreted. GNU uses the word "referenced" which could also be open to misinterpretation. The OpenBSD manual doesn't really make it clear at all, but kind of implies it with the comment about -h and -R options being mutually exclusive.
- renewiltord 7y agoClearly I have been doing completely unsafe things for some twenty years now. This blows my mind.
- inopinatus 7y agoBack in the day you could write a core dump through a symlink. In conjunction with other bugs this made a very exploitable privilege escalation. You’d think modern tooling would know better, but no. Chef can happily write templates through a symlink, and this will, bizarrely, even be the default in future.