Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Mac OS X 10.9 "Mavericks" and SAV for Mac

Apple released Mac OS X 10.9 "Mavericks" today, free for everyone with Snow Leopard or newer.

We've been testing our product with this release for many months now and had made numerous changes in version 9.0.3 (the version published about a month ago). The significant changes required were to change how we were building, codesigning, and installing our kernel extensions. You will now find two copies of our kext: one in /System/Library/Extensions and another in /Library/Extensions. This follows Apple's recommendation to support people transitioning from 10.8 to 10.9.

The kexts in /System/Library/Extensions are present for compatiblity with versions of Mac OS X prior to 10.9. Starting in "Mavericks" the location is /Library/Extensions. We are codesigning the kexts in /Library/Extensions to conform to Apple's security requirements.

If you have issues, please report them in this thread.

:1013899


This thread was automatically locked due to age.
Parents

  • cashxx wrote:
    I got the same "w u h 0 0" after about 5 seconds or so.   Repeated attempts where immediate.   Wait a minute then try again it will take 2 or 3 seconds.

    That is bad news, it means something upstream is filtering and slowing those requests. The quick response on successive attempts likely means some caching, but once the cache expires then it takes a long time again.

    I will let our operations team know about this. There is a chance its something wrong on our end, although less likely only because we'd be getting all sorts of misery about it from our business customers (you are sharing the same global infrastructure for SXL lookups).

    :1014225

    ---

    Bob Cook (bob.cook@sophos.com) Director, Software Development

Reply

  • cashxx wrote:
    I got the same "w u h 0 0" after about 5 seconds or so.   Repeated attempts where immediate.   Wait a minute then try again it will take 2 or 3 seconds.

    That is bad news, it means something upstream is filtering and slowing those requests. The quick response on successive attempts likely means some caching, but once the cache expires then it takes a long time again.

    I will let our operations team know about this. There is a chance its something wrong on our end, although less likely only because we'd be getting all sorts of misery about it from our business customers (you are sharing the same global infrastructure for SXL lookups).

    :1014225

    ---

    Bob Cook (bob.cook@sophos.com) Director, Software Development

Children
No Data
Share Feedback
×

Submitted a Tech Support Case lately from the Support Portal?