Yuck.
Well, anything involving a
link we can probably just ignore. I see two types above...
should be lrwxr-xr-x , they are lrw-r--r--
Even if DURP is "right" (and i wouldn't bet on it), it doesn't matter there... because both items are links in that line... and perms on links are almost totally irrelevant (especially the execute bits it seems to want). A link's purpose is simply to transport us to the target. [i.e., it's only the perms on the target that really matter.]
should be -rw-r--r-- , they are lrwxr-xr-x
That's the classic DURP burp right there: should be a file, but found a link. Well good luck... because there is no (simple) "command" which can transform a link into a file. One would need to remove the link and then copy some file in. [i.e., requires a change of file type (structure), not a 'permissions' change.] And behind all that noise is that DURP is simply referencing outdated information... thus it just doesn't realize that Apple recently redesigned the layout, by replacing the file with a link.
So... ignoring every item involving a link, you have five left:
- two: should be 0, user is 95
- two: should be 95, user is 0
and - one: Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent" has been modified and will not be repaired.
That SUID one (which bugs me no end) is another DURP boo-boo. [or so we HOPE... because the day that hackers discover they can safely modify that file because Mac users typically ignore any warning about it, well... then we'll wake up i guess.] Anyway, that one tells us explicitly "
will not be repaired"... so we can expect it to persist, until some update cleans up DURP's database. (there's more to say about how poorly suid items are mishandled, but i'll skip it this time).
The remaining four with 95 and 0 mixed up... idunno. They look new to me, but right now i'm not up to the
hassle of checking them manually. [uid 95 is "_update_sharing" for whatever that's worth.]
With DURP's batting average these days, my assumption is: if DURP can't fix it then it must not need fixing in the first place. I haven't repaired perms in a few months, so maybe i'll just check and see what kind of "report" my MBP produces this weekend sometime.
