Secure.log always need permissions repaired?

If I ever have any permissions to repair on both my iMac and Macbook pro its always this:
Repairing permissions for “Macintosh HD”
Determining correct file permissions.
Permissions differ on ./private/var/log/secure.log, should be -rw------- , they are -rw-r-----
What is the secure.log and is there an action I can prevent this from re-occuring?
Any help would be appreciated.

What is the secure.log and is there an action I can prevent this from re-occuring?You won't always get this error, only after the weekly maintenance run. You can find details here: Spurious Permission errors in OS X 10.4

Similar Messages

  • ITunes Resource files seem to always need permissions repair.

    Hey All,
    The subject says it all; when doing a permissions repair, Disk Utility finishes with a very long list (31 pages) of iTunes files and resources that have been repaired. This includes files in differing languages (Dutch, English, French, German, Japanese, Spanish) as well as CD settings (I don't burn CD's with iTunes). Many other file types are included in the list.  This happens repeatedly. Seemingly everytime that I do a permissions repair.
    On the last permissions repair, there were also a couple of iChat files and a Java file (not that it makes any difference, but I'm sure someone would ask).
    iTunes version 11.1 (126)
    Thanks in advance for any assistance.

    I just saw this post:
    https://discussions.apple.com/message/23192166?tstart=0#23192166?tstart=0
    if it's any help.

  • No issues, but curious..why do I always get permissions repaired when I click on 'repair permissions in Disk Utility......it usually has to do with core permissions and it's happened since i got this MacBook Pro in 3/11..it continues with 10.7

    No issues, but curious..why do I always get permissions repaired when I click on 'repair permissions' in Disk Utility ??......it usually has to do with core permissions and it's happened since i got this MacBook Pro in 3/11..I'll try this every 2/3 wks and always get repairs.....yet, I don't really have issues....it's been weird.......it continues with 10.7 and the update to 10.7.1.. a sample:
    Permissions differ on “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/da.lproj/UIAgent.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
    Repaired “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/Rem ote Desktop Message.app/Contents/Resources/da.lproj/UIAgent.nib”
    Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/da.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
    Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreen.app/Contents/Resources/da.lproj/MainMenu.nib”
    Permissions differ on “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”; should be -rw-r--r-- ; they are drw-r--r-- .
    Repaired “System/Library/CoreServices/RemoteManagement/AppleVNCServer.bundle/Contents/Su pport/LockScreenLeopard386.app/Contents/Resources/da.lproj/MainMenu.nib”
    Group differs on “Library/Preferences/com.apple.alf.plist”; should be 80; group is 0.
    Repaired “Library/Preferences/com.apple.alf.plist”
    Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.

    As described in this article, don't worry about it:
    http://support.apple.com/kb/TS1448?viewlocale=en_US

  • Permissions for secure.log

    Every time I repair permissions, there's one item that always needs its permissions repaired, the secure.log. I understand that its permissions are changed by some maintenance script, and the whole issue should be harmless. But what I don't understand is why doesn't that same maintenance script reinstate the original permissions after it has run. Or else, why doesn't Disk Utility just let them be?
    We now have a situation where the secure.log has certain permissions. Some OSX-native software (maintenance script) changes them, and another OSX-native software (Disk Utility) thinks that's wrong and changes them back. The next time the maintenance script runs, it changes them again, which Disk Utility again thinks is wrong, and so on in a perpetual cycle. It seems pretty pointless to me. It also seems like an easy thing to "correct". It's not like it's a malfunctioning third party software involved.
    Is there some obscure technical reason for why this is so?

    jofima wrote:
    Every time I repair permissions, there's one item that always needs its permissions repaired, the secure.log. I understand that its permissions are changed by some maintenance script, and the whole issue should be harmless.
    See toward the end of this User Tip for an explanation:
    Spurious Permission errors in OS X 10.4.
    The weekly maintenance script is ever so slightly more permissive in that it allows group read access. If you're at all worried you can change the script, but it really isn't worth it.
    Is there some obscure technical reason for why this is so?
    Basically it was low in the list of changes, I assume.
    It was still there in early releases of 10.5, but appears now to be gone in 10.5.7. I know it was still there last February.

  • Repair permissions - always has to correct secure.log

    I've noticed that every time I repair permissions the ./private/var/log/secure.log is corrected from -rw-r----- to -rw-------
    I'm curious to know why this is happening - is it something I should be worried about?
    Cheers
    Steve

    It happens because the "weekly" maintenance task has a different (and better) idea of what the permissions for this file should be. See the tail end of this User Tip: Spurious Permission errors in OS X 10.4.
    So, in a way, you are more secure without running Repair Permissions!

  • Permissions always need repair

    My model identifier is iMac12,2 and my OS version is 10.6.8
    When I do a permissions repair, one minute later I can do another repair with the same permissions repaired. In other words, it doesn't seem as though the repair actually works. Is there anything I can do about this? Should I do another clean install of the OS?

    No, and it is working. Any remaining messages are due to having the current software installed; repeated runs of repair permissions won't fix anything which the first run didn't and are a waste of time.
    (62208)

  • Private Secure Log Permissions being changed by someone????

    I have been having to repair the permissions on my ibook often. How do these get changed, by who, and what threat is it to me? How much control over my computer can one get????
    Below is the repair I just had to make.
    Repairing permissions for “Macintosh HD”
    Determining correct file permissions.
    Group differs on ./private/etc/authorization, should be 80, group is 0
    Owner and group corrected on ./private/etc/authorization
    Permissions corrected on ./private/etc/authorization
    Permissions differ on ./private/var/log/secure.log, should be -rw------- , they are -rw-r-----
    Owner and group corrected on ./private/var/log/secure.log
    Permissions corrected on ./private/var/log/secure.log
    Permissions repair complete
    The privileges have been verified or repaired on the selected volume
      Mac OS X (10.4.9)  

    The permissions on the secure.log file are being changed by the weekly cron task, which is being run by Mac OS X itself as opposed to someone accessing the computer locally or over the network.
    (21837)

  • Need help fixing my safari.  have already done files perms repair to no avail.  Only thing that happens when I select Safari is the screen changes color.

    I Need assistance repairing my browser "Safari" on my MacBook Pro.  The only thing that happens when I select it is that the Icon does bounce up and down.  I've already tried to repair the files perms to no avail. I have also created another user and tried to use Safari when logged on as them and it didn't work then either.
    Help!!  I'm new to Apple but have loads of PC experience...

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
    Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Test while in safe mode. Same problem?
    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • Permissions fix for secure.log and iTunes frameworks

    Aperture 1.5
    PBG4 showed minor to considerable performance improvements. Once my main library finished running on the Quad, with 6600 traction engine, I started to do some real work.
    The following is in Project View on some images with patches/healing and straighten applied.
    IT WAS UGLY. SBOD every time I touched anything (yes, all previews completed). 45 secs to open the first image (8Mb RAW from Canon 20d). 5-6 secs. for any touch on Levels or Exposure. IMPOSSIBLE.
    Switched off and reduced res. of JPG's in Preferences. No difference.
    BTW Apple Devt. Spank time> There is NO way to turn off Preview creation and run as batch later that I can see. Please fix. Agreed they render in background but why not wait until you leave focus on that image .... it's recreating a preview after every adjustment I make. C'mon guys, get real, that should be fixed asap.
    Quit Aperture, restarted. Just as bad. Aperture is the only app. running, and Activity Monitor shows 319% CPU with 480Mb RAM just with a Levels change ... sounds high. 6-7 sec. response time for anything I do and 20-40 secs for image rendering, except adjacent images. Quit Aperture.
    Decided to run Repair Permissions (RAID = 0 drive). Fixed iTunes frameworks and secure.log. I believe secure.log to be the culprit.
    Restarted Aperture and performance improvements obvious. Sliders now work real-time and image rendering a couple of seconds. Reapplied Preferences setting for Previews and no significant performance degradation (though it is interesting watching the task list pause the preview generation when you make further edits.)

    It sounds like you should just turn off Maintain Previews for the project you are on (selct prj and change state in top level gear menu in prj pane) - then make your adjustments ( your previews won't be up to date then of course) but the when you are ready to make into previews just select all the images and choose Update Preview manually from the context menu.
    LC, Classic, 8500, DP2.5, MBP2.1   Mac OS X (10.4.7)   i have a cool mousepad

  • I have iPhoto 11, 9.4.1 installed. When my library was upgraded, I got a message the photos couldn't be imported and I need to repair iPhoto permissions. How do I do that? My photos are there, but I can no longer drag them to the photo stream.

    I have iPhoto 11, version 9.4.1 installed. When my library upgraded, I got a message that the photos couldn't be inported and I need to repair iPhoto permissions. How do I do that? My photos are there, but I can no oonger drag them to the photo stream.

    Disable Photo Stream in iPhoto's preferences and then go back and reenable it. See if that will jump start the process.  If that doesn't help try this:  make a temporary, backup copy (if you don't already have a backup copy) of the library and try the following:
    1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your
         User/Home()/Library/ Preferences folder.
    2 - delete iPhoto's cache file, Cache.db, that is located in your
         User/Home()/Library/Caches/com.apple.iPhoto folder. 
    Click to view full size
    3 - launch iPhoto check its preferences to meka sure all is as you expect and try again.
    NOTE: If you're moved your library from its default location in your Home/Pictures folder you will have to point iPhoto to its new location when you next open iPhoto by holding down the Option key when launching iPhoto.  You'll also have to reset the iPhoto's various preferences.
    NOTE 2:  In Lion and Mountain Lion the Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and hit the Enter button - 10.7: Un-hide the User Library folder.
    OT

  • Do I need to repair permissions with a SSD?

    Do I need to repair permissions with a SSD?

    Repairing permissions is only potentially helpful once for each problem with your computer you may experience. As it's a software-only function, it doesn't matter that the computer has an SSD instead of a hard drive.
    (77406)

  • After updating to Yosemite, I updated iPhoto. Alert said to convert my library to new iPhoto. Then alert said I needed to repair permissions. Then a freeze. Then iPhoto won't find and show my library. How do I fix this?

    After updating to Yosemite, I updated iPhoto. Alert said to convert my library to new iPhoto. Then alert said I needed to repair permissions. Then a freeze. Then iPhoto won't find and show my library. How do I fix this? I can see the library icon on my external drive, but it doesn't show as a library in iPhoto. When I double click on the icon, nothing happens. When I choose it from alternate menu, doesn't open. Where do I get help?

    Peter
    Do you have a back up? What version of iPhoto do you have? Assuming 09 or later:
    Option 1
    Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Repair Database. If that doesn't help, then try again, this time using Rebuild Database.
    If that fails:
    Option 2
    Download iPhoto Library Manager and use its rebuild function. (In early versions of Library Manager it's the File -> Rebuild command. In later versions it's under the Library menu.)
    This will create an entirely new library. It will then copy (or try to) your photos and all the associated metadata and versions to this new Library, and arrange it as close as it can to what you had in the damaged Library. It does this based on information it finds in the iPhoto sharing mechanism - but that means that things not shared won't be there, so no slideshows, books or calendars, for instance - but it should get all your events, albums and keywords, faces and places back.
    Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.  
    Regards
    TD

  • Clean Install needs Disk Permissions Repaired?

    I have just performed a clean install of ML 10.8.2 and performed a Disk Verify which reported back OK.  Then I did a Verify Disk Permissions and it found several items that needed repair.  I rebooted and ran it again but the same items came back.  So I repaired the permissions.
    I also had this same problem when I did a clean install of 10.8.1 and both times that was all that was on the disk.
    Is this normal?  Should I have to do a permissions repair after installing a new OS?

    Should I have to do a permissions repair after installing a new OS?
    No, and you don't have to. You never need to repair permissions unless you have an indication of a permission error involving system files, which you probably never will unless you do something very unusual. The warning messages are spurious.
    Permission repair is an immensely popular, time-wasting ritual that is rarely, if ever, necessary. The one time you can be absolutely sure you don't need to do it is right after installing or reinstalling OS X.

  • Need to Repair Disk Permissions Everyday? Same errors each time.

    I have a White MacBook 4,1 - 2.1 Ghz 3 MB Cache, 800 MHz Bus. It seems like I need to repair the permissions everyday. Every time I do I get the exact same errors, when I start up off the Mac OS X dvd I get no errors under repair disk, but the same errors under repair permissions.
    This is what I get:
    Repairing permissions for “Macintosh HD”
    Reading permissions database.
    Reading the permissions database can take several minutes.
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/CoreServices/RawCamera.bundle/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "Applications/iTunes.app/Contents/CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents/ CodeResources", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeResou rces", should be -rw-rw-r-- , they are lrw-rw-r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeRe sources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResourc es", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/CubeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DissolveTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/DropletTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/FlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PageFlipTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/PushTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/RevealTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/SepiaEffect.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/TwirlTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions differ on "System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/P lugins/WipeTransition.IAPlugin/Contents/CodeResources", should be -rw-r--r-- , they are lrw-r--r-- .
    Permissions repair complete
    Anyone know what's wrong?

    There is no error. You could repair permissions continuously and these same notifications will show up.
    Recent updates to iPhoto, Front Row, and an update for RAW compatibility have resulted in these permissions differences. Rather than replacing the old permissions with a new one, the system sees a symbolic "link" (the L you see in front of the permissions).
    Nothing is wrong with your machine--we're all getting these notifications. Hopefully a system update will change the permissions for us in the future.
    ~Lyssa

  • Why does my 10.6.8 need constant permissions repair?

    When I have a slowdown on my OS or hangs on an app, I typically run Disk Utility and repair permissions. I have found that there's always a lengthy repair required... no matter how recently I repaired permissions.
    Today I did a repair, then tried one again immediately after. It still  required a lengthy repair, on seemingly the same files (typically "System/Library/Frameworks/JavaVM.framework..." etc. and "System/Library/CoreServices/Menu Extras/RemoteDesktop.menu"...)
    Don't know why this happens...

    Because the permissions on or structure of those files was intentionally modified after the repair permissions database was compiled. Ignore them. Repairing permissions repeatedly is a waste of time.
    (63912)

Maybe you are looking for