How to exclude Mercurial's .hg repository folders?

Discussion in 'ESET NOD32 Antivirus' started by adejones, Nov 15, 2010.

Thread Status:
Not open for further replies.
  1. adejones

    adejones Registered Member

    Joined:
    Nov 15, 2010
    Posts:
    1
    Location:
    Birmingham UK
    Hi all,

    I have a bunch of developers using Mecurial version control software with network shares on various file servers. Mercurial creates .hg (dot hg) folders containing the repository and it's recommended to be excluded from anti virus scanning. I want to improve performance and this seems like sensible approach to investigate, and not my only approach.

    We're running NOD32 Anti Virus Business Edition v4.2.64

    I want to know if there is a way to exclude Mercurial's .hg folders from scanning?

    I've tried using wildcards, i.e.
    *.hg
    *.hg*
    .hg*

    I've tested with the eicar file by scanning with the in file in the .hg folder, and of course these don't work.

    What might work, if this was a valid exclusion format, is: *\.hg\*

    Does anyone have any ideas or comments on this scenario?

    Thanks in advance,

    adejones
     
  2. ThomasC

    ThomasC Former ESET Support Rep

    Joined:
    Sep 8, 2008
    Posts:
    209
    Hello,

    There is a way to accomplish what you are trying to do with that exclusion. However this is not the only consideration for running a network application.

    I would suggest configuring the ESET NOD32 client, on the file servers, in accordance with our KB article for ESET’s recommended server settings. This will help to ensure that the files are not only excluded from the real-time protection module but the web access protection module as well. On the server make sure that the desired file types are not included in the extensions to scan section, under the appropriate ThreatSense settings. The ThreatSense settings are outlined in the article above.

    For the clients you will want to: Turn off the scanning of network drives; ad file type exclusions in the same ThreatSense area that we adjusted on the server. You will also need to exclude the application file for Mercurial from beings scanned by the Web Access Protection module on the clients. The follow ESET KB article explains how to enter exclusions.

    Cheers,
    -Tom
     
Thread Status:
Not open for further replies.