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

Several new questions

It's a long story and I won't go into all the details, but Sophos was giving me a could not scan, unexpected error, corrupt file message for the Firefox Profiles cache. Turned out that was because the hidden flag had been turned on for that particular file. That's been solved, sort of--I'm no longer getting that error message (It seems Firefox wants to keep that cache hidden, because even after unhiding it, after logging out and back in, it reverted to being hidden.)

Anyway, thinking that this perhaps showed that Sophos was unable to scan hidden files (I know this is very unlikely, since that would be a very major vulnerability for any A-V), I first turned off on access scanning, and placed an eicar malware test file, hidden and with the proper permissions, in /System/Library/LaunchAgents, as a test. I would have expected an alert as soon as I turned scanning back on, but I didn't get the alert until I did a manual/custom scan there. I expected I would have gotten the alert immediately without having to do a manual/custom scan--that was the behavior I got when, earlier, I created a not hidden duplicate of that file (the original is excluded) where I normally keep it. I am running out of a standard account, so was that because the on access scanner doesn't have permission to see into /System/Library?

Second, not sure why this is happening--maybe related to all the different kinds of custom scans I've tried (both ordinary and from root)--I'm sometimes losing the Sophos icon in the menubar and the only way to get it back is to log out and back in.

:1016291


This thread was automatically locked due to age.
  • Hello brvx,

    trying to give you at least one answer.

    the on access scanner doesn't have permission

    On-Access does not scan files "on its own", it intercepts file opens - if the OS doesn't open a file for the user there's nothing for On-Access to intercept. AFAIK it also performs cleanup(/move/delete) actions under the user's context thus if the user doesn't have write permissions the cleanup would fail.

    Christian

    :1016297
  • Thanks, I guess that could be the answer. What threw me was that as soon as I created the duplicate of the eicar in my user (the original is excluded), I got an alert. I didn't have to open it, but I guess that creating that dupe was enough for Sophos to consider that it was "opened."

    By the way, when I try to place an exclusion I usually first get Users/Shared-0, which I have to delete. I've searched around for an answer, including in the version 8 manual--not seeing one for 9. Do you know what's up with that?

    :1016301
  • Hi brvx,

    It's not actually intercepting file opens, it's on-access as the name implies.  Hence, Spotlight will trigger it if it tries to index a threat.  Attempting to move/copy/dupicate an infected file in the Finder also triggers an intercept.

    The disappearing icon seems to be a recurring issue with some users although I have not seen that for a long time myself. 

    I see the Users/Shared-0 text  as well but I don't see that it matters what initially appears in there.  My guess is that it's meant to be an example or template and the "-0"  is an anomoly.

    Regards

    :1016303