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

Quick question regarding Exclusions and Wildcards...

One of our clients are running Sophos on their client PC's and on the server hosting our Software solution and Firebird database. We have a very big speed issue when our application is executed from a share on the server and where it then calls its own DLL's... Even a menu item that has a sub-item that points to a DLL takes about 10-20 seconds to show but it is almost instant when Sophos is disabled.

I am not on site and just need some clarification on wildcards and exclusions.

From the Sophos help document I know the following limitations:

  • The wildcard ? can be used only in a filename or extension. It generally matches any single character. However, when used at the end of a filename or extension, it matches any single character or no characters. For example file??.txt matches file.txt, file1.txt and file12.txt but not file123.txt.
  • The wildcard * can be used only in a filename or extension, in the form [filename].* or *.[extension]. For example, file*.txt, file.txt* and file.*txt are invalid.
  • You can specify a folder and filename, and Sophos Anti-Virus excludes any folder and filename that match. For example
    logs\log.txt causes Sophos Anti-Virus to exclude log.txt in any folder called logs on any drive or share.

Seeing how very limited Sophos handles wildcards, I just need to know whether adding a file exclusion as folder\*.ext will work or will I need to create an folder\differentname.ext entry for every filename even if the ext is the same?

Thanks in advance

:8023


This thread was automatically locked due to age.
Parents
  • Sorry I didn't reply earlier. But maybe it could help in the future.

    A folder\file pattern will work but you have to specify the path from the root (with or without s drive/share). Assuming your software is on \\Someserver\software\thisone then in order to exclude the DLLs from being scanned you'd use \software\thisone\*.dll. If you have any subfolders which also contain DLLs then you'd need another exclusion. Did some tests with SAV9.5 and patterns like \software\thisone\*.??? also work.

    If on-access is enabled on the server and the files on the share are usually only read you could simply exclude share - as the files are not re-scanned when they don't change it shouldn't have much impact (except for the "first" one who opens them).

    HTH

    Christian

    :8153
Reply
  • Sorry I didn't reply earlier. But maybe it could help in the future.

    A folder\file pattern will work but you have to specify the path from the root (with or without s drive/share). Assuming your software is on \\Someserver\software\thisone then in order to exclude the DLLs from being scanned you'd use \software\thisone\*.dll. If you have any subfolders which also contain DLLs then you'd need another exclusion. Did some tests with SAV9.5 and patterns like \software\thisone\*.??? also work.

    If on-access is enabled on the server and the files on the share are usually only read you could simply exclude share - as the files are not re-scanned when they don't change it shouldn't have much impact (except for the "first" one who opens them).

    HTH

    Christian

    :8153
Children
No Data