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

New user to Sophos for Mac - problems reported in log

I have been evaluating AV products for the Mac. I am disappointed with several of the "star performers" from the Windows world, because they are buggy or unstable. So far Sophos seems the most trouble free.

However, after doing a full system scan, there were several issues that I think are problems with Sophos rather than actual malware. There was one file that I believe is a false positive. I uploaded that file to Sophos and they confirmed it was clean.

The reason I am writing this message is because the full scan also reported several "corrupted files", which I do not believe are corrupted. Typically they are bz2 files, but also some dmg, jar and exe files.

Is there a problem with this version of Sophos where it reports corrupted files that are not in fact corrupted?

:1006919


This thread was automatically locked due to age.
Parents
  • I've heard of some problems using older SuperDuper versions with Mountain Lion -- you need to be at least at version 2.7 for it to operate correctly.  If On-Access is disabled, it won't be monitoring at all, so this is likely not where the problem lies.  Do the console.app logs for SuperDuper, Sophos, Disk Utility and the syslog shed any light on this?

    :1008762
Reply
  • I've heard of some problems using older SuperDuper versions with Mountain Lion -- you need to be at least at version 2.7 for it to operate correctly.  If On-Access is disabled, it won't be monitoring at all, so this is likely not where the problem lies.  Do the console.app logs for SuperDuper, Sophos, Disk Utility and the syslog shed any light on this?

    :1008762
Children
No Data