paula185

Q: Warning: SUID file "System/Library/CoreServices" has been modified and will not be repaired.

Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.

 

<Subject Edited by Host>

iMac, Mac OS X (10.6.8)

Posted on Jun 8, 2013 2:43 PM

Close

Q: Warning: SUID file "System/Library/CoreServices" has been modified and will not be repaired.

  • All replies
  • Helpful answers

Previous Page 2 of 7 last Next
  • by anthonybperez,Helpful

    anthonybperez anthonybperez Dec 29, 2012 9:40 AM in response to anthonybperez
    Level 1 (15 points)
    Dec 29, 2012 9:40 AM in response to anthonybperez

    crap my mac pro has the same issue.

  • by Kurt Lang,Helpful

    Kurt Lang Kurt Lang Dec 29, 2012 12:44 PM in response to anthonybperez
    Level 8 (37,815 points)
    Mac OS X
    Dec 29, 2012 12:44 PM in response to anthonybperez

    As has been noted more than once, it is not an issue of any kind. Ignore it.

  • by anthonybperez,Helpful

    anthonybperez anthonybperez Dec 29, 2012 8:19 PM in response to Joseph Kriz
    Level 1 (15 points)
    Dec 29, 2012 8:19 PM in response to Joseph Kriz

    Ok so I did what you said but it wont let me read or write even after unlocking each file.

  • by anthonybperez,

    anthonybperez anthonybperez Dec 29, 2012 8:20 PM in response to Kurt Lang
    Level 1 (15 points)
    Dec 29, 2012 8:20 PM in response to Kurt Lang

    but if it can be fixed why not? I see no harm.

  • by anthonybperez,Helpful

    anthonybperez anthonybperez Dec 29, 2012 9:19 PM in response to Joseph Kriz
    Level 1 (15 points)
    Dec 29, 2012 9:19 PM in response to Joseph Kriz

    Just figured it all out, and it worked.

    And my repair also fixed some permission that cant on coming back.

     

    Thanks.

  • by rschwabe,

    rschwabe rschwabe Jan 7, 2013 6:28 PM in response to paula185
    Level 1 (20 points)
    Jan 7, 2013 6:28 PM in response to paula185

    Ignore...ignore...ignore....

     

    Resolution

    You can safely ignore these messages. You can also usually ignore any "ACL found but not expected..." message. These messages can occur if you change permissions on a file or directory; they are accurate, but generally not a cause for concern.

  • by Priestmonk Bartholomew,

    Priestmonk Bartholomew Priestmonk Bartholomew Jan 8, 2013 1:23 PM in response to paula185
    Level 1 (10 points)
    Jan 8, 2013 1:23 PM in response to paula185

    Ok....I need to fix this on white MacBook....have to "repair" permission several times daily particularly after connecting to net.   I get

    Warning: SUID file “System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent” has been modified and will not be repaired.

    Permissions differ on “System/Library/PreferencePanes/.Displays/V1/Displays.prefPane/Contents/Resourc es/Dutch.lproj/DisplaysPref.nib”; should be -rw-r--r-- ; they are -rwxr-xr-x .

     

    then I get various repairs …a few examples

     

    Permissions differ on “System/Library/PreferencePanes/Displays.prefPane/Contents/Resources/French.lpr oj/DisplaysPref.nib”; should be drwxr-xr-x ; they are -rw-r--r-- .

     

    Repaired “System/Library/PreferencePanes/Displays.prefPane/Contents/Resources/hr.lproj/D isplaysPref.nib”

     

    Repaired “System/Library/PreferencePanes/Displays.prefPane/Contents/Resources/hr.lproj/D isplaysPref.nib”

     

    Permissions differ on “System/Library/CoreServices/Menu Extras/Displays.menu”; should be drwxr-xr-x ; they are lrwxr-xr-x .

     

    Permissions differ on “System/Library/MonitorPanels/Arrange.monitorPanel”; should be drwxr-xr-x ; they are lrwxr-xr-x .

  • by jelger,

    jelger jelger Mar 10, 2013 4:35 AM in response to varjak paw
    Level 1 (4 points)
    Mar 10, 2013 4:35 AM in response to varjak paw

    Well the word 'usually' sets me on edge. It does mean not all the thime. Alo at the end of the statement 'but generally not a cause for concern.' Is a nice one. generally hmmm not very precise.

     

     

    So when can you ingore these kind of messages and when not. That is the question.

  • by Klaus1,

    Klaus1 Klaus1 Mar 10, 2013 5:16 AM in response to jelger
    Level 8 (48,821 points)
    Mar 10, 2013 5:16 AM in response to jelger

    As long as the report ends up with 'Permissions repair complete' then, as far as permissions go, you are fine. You can ignore the various statements in the report:

     

    Permissions you can ignore on 10.5 onwards:

     

    http://support.apple.com/kb/TS1448

     

    Using 'should be -rw-r--r-- , they are lrw-r--r--' as an example, you will see the that the permissions are not changed, but the | indicates a different location. This is because an update to Leopard onwards changed the location of a number of system components.

     

    Poster rccharles has provided this description of what it all means:

     

    drwxrwxrwx
     
    d = directory


    r = read

    w = write


    x = executeable program

     

    drwxrwxrwx

    |  |  |

    |  |   all other users not in first two types

    |  | 

    |  group

    owner


    a little more info

    Before the user had read & write. A member of the group had read.

    After, only the user had read & write.

     

     

    If you are running Panther or Tiger:

     

    http://support.apple.com/kb/TA21090

  • by carole204,Helpful

    carole204 carole204 May 3, 2013 6:44 PM in response to Klaus1
    Level 1 (5 points)
    May 3, 2013 6:44 PM in response to Klaus1

    Keep going back to MacWorld Jun 26, 2008 – The recently-revealed ARDAgent security hole is a fairly bad one. There are, however, some simple things you can do to minimize your risks.

     

    Everyone should read.  I hate to ignore this one.

  • by AmazonWoman1,

    AmazonWoman1 AmazonWoman1 Jun 2, 2013 2:37 PM in response to Joseph Kriz
    Level 1 (0 points)
    Jun 2, 2013 2:37 PM in response to Joseph Kriz

    Thank you very much for posting that.Those of us with that error message that have tried everything including several reformats to fix that error KNOW there is some problem.If it was a message that was meant to be there it would always be there on every Mac.I do not understand though how did you get a new copy of the OS though if you are installing it to a hardrive already infected by whatever problem?

  • by 3dbatics,

    3dbatics 3dbatics Jun 8, 2013 2:04 AM in response to Joseph Kriz
    Level 1 (0 points)
    Jun 8, 2013 2:04 AM in response to Joseph Kriz

    i have resolved  equal problem eliminat the directory System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent

    I installed the program Apple Remote Desktop 3.

    and since then I came out of the error.

    now it's all white

    sorry for my english

  • by Kurt Lang,

    Kurt Lang Kurt Lang Jun 8, 2013 8:13 AM in response to 3dbatics
    Level 8 (37,815 points)
    Mac OS X
    Jun 8, 2013 8:13 AM in response to 3dbatics

    For the umpteenth time, there's no need to do anything about these messages. They're normal.

    eliminate the directory.../RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAgent

    All you've done is broken an element of OS X because you're worried about a benign message. If you need to use it, and attempt to turn on Remote Login in the System Preference, it now won't work.

  • by 3dbatics,

    3dbatics 3dbatics Jun 8, 2013 11:34 AM in response to Kurt Lang
    Level 1 (0 points)
    Jun 8, 2013 11:34 AM in response to Kurt Lang

    Ok thanks,

     

    I don't  will connect the mac on remote

  • by Roger Wilmut1,Helpful

    Roger Wilmut1 Roger Wilmut1 Jun 8, 2013 2:40 PM in response to Joseph Kriz
    Level 9 (78,198 points)
    iTunes
    Jun 8, 2013 2:40 PM in response to Joseph Kriz

    Joseph Kriz wrote:

     

    I know this question has been sort of answered but not properly in my opinion.

     

    There should be no permissions to repair once they have been repaired.

    There should also be no permissions that can't be fixed especailly by Apple.

    For the thousandth time: the issue is that some changes were made to the location of some System files and a few other things; but Disk Utility was never updated to reflect these changes and so throws up these errors.

     

    They are not a problem, and all these workarounds people keep posting are not only unneccesary but likely to cause real problems (see above).

     

    As already said, as long as at the bottom of the list it says 'Permissions repair complete' there is no problem.

Previous Page 2 of 7 last Next