Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 6 subscribers
  • Views 2913 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

New user to Sophos for Mac - problems reported in log

jasimon9

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
  • 0

    I am having the same issue with Sophos for Mac and SuperDuper. The thing is, the problem isn't with SuperDuper but Disk Utility trying to create the image file before running the backup. It appears that Sophos may be causing a timeout to occur during the file creation while it scans the file. I have disabled On-Access and get the same error. Since the file isn't created yet, how can it be added to an exclusion list? I guess I could exclude the whole folder where the backups are saved. This still would not help when On-Access tries to scan the file during backup.

    One note, I am now using a "clean install" version of OS X 10.8 Mountain Lion. I didn't have this issue previously, but, I have only upgraded everytime since 10.5, not a clean install. Even after my upgrade from 10.7 to 10.8 it was still working correctly. I had to do a clean install due to an issue with Java, then when I went to do my first backup I ran into this issue.

    :1008752
Reply
  • 0

    I am having the same issue with Sophos for Mac and SuperDuper. The thing is, the problem isn't with SuperDuper but Disk Utility trying to create the image file before running the backup. It appears that Sophos may be causing a timeout to occur during the file creation while it scans the file. I have disabled On-Access and get the same error. Since the file isn't created yet, how can it be added to an exclusion list? I guess I could exclude the whole folder where the backups are saved. This still would not help when On-Access tries to scan the file during backup.

    One note, I am now using a "clean install" version of OS X 10.8 Mountain Lion. I didn't have this issue previously, but, I have only upgraded everytime since 10.5, not a clean install. Even after my upgrade from 10.7 to 10.8 it was still working correctly. I had to do a clean install due to an issue with Java, then when I went to do my first backup I ran into this issue.

    :1008752
Children
No Data