05a59e5af5
I just noticed this while reading the code. Right now we're actually following links (since `AT_SYMLINK_NOFOLLOW` isn't implemented), which could definitely lead to bad things if e.g. one has a symlink pointing to a file which shouldn't be executable or world-readable etc. (Also I noticed our hardlink-breaking-only-if-regular logic is now broken; I added a TODO) Closes: #677 Approved by: jlebon |
||
---|---|---|
.. | ||
app | ||
daemon | ||
lib | ||
libpriv |