Skip navigation

crsud process with security update 2013-001

36841 Views 168 Replies Latest reply: Sep 8, 2013 9:10 AM by MadMacs0 RSS
  • MadMacs0 Level 4 Level 4 (3,320 points)
    Currently Being Moderated
    Sep 7, 2013 2:27 PM (in response to Apple a day)

    Apple a day wrote:

     

    That screenshot is for OS X 10.8.x

    That's what I thought.

     

    So my guess would have to be that your 2013-003 wasn't properly installed the first time.

  • Apple a day Calculating status...
    Currently Being Moderated
    Sep 7, 2013 2:34 PM (in response to MadMacs0)

    MadMacs0 wrote:

     

    What did you mean by "both"?

    One is the plug in block list and the other is the malware list

     

     

     

     

    MadMacs0 wrote:

    "So my guess would have to be that your 2013-003 wasn't properly installed the first time."

     

    I think it was a security or Java Update in April for me, I was stuck at May 1 until the June security update and then I got a date of May 16 and that is where I had been stuck at till last night

     

    My thought was maybe trying to reapply the patch might get it fixed right (I know some updates get rerelased (things fixed in an update))

  • tingotanca Level 1 Level 1 (0 points)
    Currently Being Moderated
    Sep 8, 2013 5:17 AM (in response to MadMacs0)

    Same Aug 29 here on 10.6.8. Tried to update again today, got an error from the server that says "[...] Ignoring new signature plist: Not an increase in version". At this point, I'm updating manually once every3-4 weeks, and hoping for the best.

  • MadMacs0 Level 4 Level 4 (3,320 points)
    Currently Being Moderated
    Sep 8, 2013 9:10 AM (in response to tingotanca)

    tingotanca wrote:

     

    Same Aug 29 here on 10.6.8.

    Ignore the date, just go by the version number. Yours is up-to-date with version 65.

    got an error from the server that says "[...] Ignoring new signature plist: Not an increase in version". At this point, I'm updating manually once every3-4 weeks, and hoping for the best.

    That's not really an error, it's exactly what you should see every day. You shouldn't need to manually update unless you hear about an update and 24 hours have passed without your seeing it.

1 ... 8 9 10 11 12 Previous Next

Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.