Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 6 subscribers
  • Views 13003 views
  • Users 0 members are here
Options
Suggested
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

v8.0.6C constantly writing to LaunchDaemons folder

Duke

One A/V technique is to employ an Applescript that monitors the /Library/LaunchDaemons & /Library/LaunchAgents folders, and posts an alert whenever a program tries to add something there. Since v8.0.6C was released, Sophos A/V for the Mac is constantly writing a new com.sophos.autoupdate.plist, com.sophos.intercheck.plist & com.sophos.notification.plist to the LaunchDaemons folder, triggering an alert.  This appears to be happening as part of the auto-update process.

Please STOP this behavior on the part of Sophos A/V for the Mac.

Thank you!

:1009684


This thread was automatically locked due to age.
Parents
  • 0

    While the more elegant solution suggested would be fine for really technically inclined people, I would argue that this is beyond the scope that most users would want to tackle.  A better approach would be for Sophos to check it's plist files during auto-update, and only replace the plist file IF & WHEN corruption is detected; not constantly.

    Thanks for the dialog. 

    :1009780
Reply
  • 0

    While the more elegant solution suggested would be fine for really technically inclined people, I would argue that this is beyond the scope that most users would want to tackle.  A better approach would be for Sophos to check it's plist files during auto-update, and only replace the plist file IF & WHEN corruption is detected; not constantly.

    Thanks for the dialog. 

    :1009780
Children
No Data