This morning, I was doing some routine monthly maintenance on my MacBook with Mac OS X 10.5.8 (Leopard).
I launched Apple's Disk Utility and started "Repair Permissions" in the "First Aid" tab.
The repair was taking a while ... when I viewed the log all of this came up:
Warning: SUID file "Applications/Utilities/ODBC Administrator.app/Contents/Resources/iodbcadmintool" has been modified and will not be repaired.
Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrwxr-xr-x .
Warning: SUID file "System/Library/Filesystems/AppleShare/afpLoad" has been modified and will not be repaired.
Warning: SUID file "sbin/umount" has been modified and will not be repaired.
Warning: SUID file "bin/rcp" has been modified and will not be repaired.
Permissions differ on "Applications/Front Row.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "Applications/Image Capture.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
Permissions differ on "System/Library/CoreServices/Menu Extras/RemoteDesktop.menu/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
Warning: SUID file "usr/bin/quota" has been modified and will not be repaired.
Warning: SUID file "usr/bin/rlogin" has been modified and will not be repaired.
Warning: SUID file "usr/bin/rsh" has been modified and will not be repaired.
What does all that mean?
I found the following information:
• This is a common problem in Leopard (although I've never had it until today)
• Definition: SUID (Set User ID):
The SUID permission causes a script to run as the user who is the owner of the script, rather than the user who started it. It is normally considered extremely bad practice to run a program in this way as it can pose many security problems. Later versions of the Linux kernel will even prohibit the running of shell scripts that have this attribute set.
• It seems this may be a Time Machine error that causes these "settings" to be modified
• There's no cause for alarm, as it mostly seems to be a Disk Utility reporting error
I found this website to have detailed answers:
http://macsolvers.wordpress.com/2009/01/21/suid/
2 comments:
You're a bit off on what "SUID" does.
At anyrate, seeing the differences, you're right that it's time machine.
That wasn't my definition but from another website ... can you help me clarify because I thought it was better than I could explain it in laymen terms.
Post a Comment