Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 9 subscribers
  • Views 1539 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

Exclusion using Junction paths

Ivo Yosifov

Hi ,

I'm trying to make a few exclusions, some programs have issues with how they interact and can inhibit source control utilities like TortoiseHG.
Further more the endpoint users have non-unified work folders. I am trying to make exclusions based on folder path and file types in that folder path.
The issue is that some users have their work folder in C:\ others in D:\
I am trying to make the exclusions once not twice using a custom environmental variable like %MyWorkDir% or Junction paths. It appears that Sophos Central will not accept custom environmental variables 

I am trying to figure out weather excluding the work directory (regardless if the actual work directory is in C: or D:) using a junction path will actually stop sophos from scanning all the content in it.

For example C:\MyWorkDir\**\*.cs 

where MyWorkDir can be the actual work directory or a junction path pointing to anywhere on the computer.
My question is does Sophos exclusion support Junction paths and if so will the files get scanned from the original path i.e. C:\Users\Local User\Documents\MyWorkDir or D:\MyWorkDir ?



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

    Hello Ivo Yosifov,

    Junction paths
    nice idea, but the filter driver doesn't exclude "alternate paths".

    you can only use a limited set of variables, not arbitrary ones. Please note that the corresponding article Note:s further restrictions on their use, specifically that some have no effect for on-access scanning.
    Perhaps you can achieve what you need using wildcards. As I'm not using Central I can't say though whether the GUI imposes restrictions.

    Christian

  • 0 in reply to QC

    Thanks a lot for the prompt answer ! 

    In that case do you know what is the maximum size of this exclusion list as I will have to apply multiple entries in it and without the handling of junction paths and custom system variables this multiplies my work ?

     

    Kind Regards,

     

    Ivo

  • 0 in reply to Ivo Yosifov

    Hello Ivo,

    as said, I don't know if the Central Admin has restrictions. But I guess it permits more entries than you can conveniently handle.

    Normally you shouldn't need exclusions and you should try to do with as few and as specific ones as possible.
    I know there is software that doesn't go together too well with AV. Normally there's some common naming (folder, extensions, name/name pattern) that in conjunction with wildcards permits to define one or two "generic" paths that don't lead to unwanted exclusions (like **\AcmeSoft\Working\, or  **\AcmeSoft\Working**\Temp\).

    Christian

Reply
  • 0 in reply to Ivo Yosifov

    Hello Ivo,

    as said, I don't know if the Central Admin has restrictions. But I guess it permits more entries than you can conveniently handle.

    Normally you shouldn't need exclusions and you should try to do with as few and as specific ones as possible.
    I know there is software that doesn't go together too well with AV. Normally there's some common naming (folder, extensions, name/name pattern) that in conjunction with wildcards permits to define one or two "generic" paths that don't lead to unwanted exclusions (like **\AcmeSoft\Working\, or  **\AcmeSoft\Working**\Temp\).

    Christian

Children
No Data
Unfiltered HTML