To quaranteen or not to quaranteen... that is the question?

Discussion in 'NOD32 version 2 Forum' started by windstrings, May 22, 2005.

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

    windstrings Registered Member

    Joined:
    Oct 20, 2004
    Posts:
    337
    Above is a quote from blackspears configuration page for nod32 v2.5

    It sounds like in order to prevent any viruses from getting in the system.. that quaranteen is not secure and therefore should not ever be enabled?

    If this is true... I can't see putting myself at risk just so I can send them to nod32?
     
  2. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    No, not at all, Quarantine simply makes a secure copy of the infected file, it does NOT removed/isolate the infected file as per the meaning of the word "quarantine". It allows you to delete the infection while having a secure copy of the file to submit to Eset, in the event of a False Positive it allows you to restore the file from Quarantine.

    Hope this helps...

    Cheers :D
     
  3. windstrings

    windstrings Registered Member

    Joined:
    Oct 20, 2004
    Posts:
    337
    thanks blackspear.. I thought I understood that, but the wording threw me.. I thought that maybe you knew something I didn't about the inner workings of nod that made quaranteen unsecure to keep around...

    The wording "secure copy" I like better... thanks...
     
Thread Status:
Not open for further replies.