www.eset.com marked red by McAfee Site Advisor

Discussion in 'NOD32 version 2 Forum' started by marty56, Sep 17, 2007.

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

    marty56 Registered Member

    Joined:
    Feb 9, 2007
    Posts:
    9
    I am sure its just a "mistake" but McAfee Site Advisor marked eset.com as a Red site.

    That means they are afraid of your product (and they be should) which means I made the right choice in using it.
     
  2. The One

    The One Frequent Poster

    Joined:
    Mar 6, 2007
    Posts:
    246
    You can choose to send it to McAfee so they can change
     
  3. Niklass

    Niklass Registered Member

    Joined:
    Sep 12, 2007
    Posts:
    11
    Location:
    Buenos Aires, Argentina
    LOL, funny stuff :D


    Yes, a "mistake"
     
  4. Brian N

    Brian N Registered Member

    Joined:
    Jul 7, 2005
    Posts:
    2,174
    Location:
    Denmark
    Looks pretty green to me. Must have been fixed I guess.
     
  5. mrtwolman

    mrtwolman Eset Staff Account

    Joined:
    Dec 5, 2002
    Posts:
    613
    This FP issue was fixed.
     
  6. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,661
    Location:
    Throughout the USA and Canada
    LOL - did it take involvement of the legal department to get it fixed thougho_O
     
  7. ASpace

    ASpace Guest

    The issue was caused by a false positive caused by the McAfee AV engine . It is more technical than legal , I think .

    The FP was caused because while the Site Advisor team tests sites , they use McAfee engine to scan files there . McAfee detected something like a generic threat in a Brontok fix utility , which detection should be a FP . It seems they have now fixed the detection issue in their bases/engine/generic sigs and no more red alarms by Site Advisor
     
  8. webyourbusiness

    webyourbusiness Registered Member

    Joined:
    Nov 16, 2004
    Posts:
    2,661
    Location:
    Throughout the USA and Canada
    my comment about legal being involved has more to do with who within Eset responded - technical issues are normally addressed by Marcos or someone else in technical. Legal issues are generally responded by mrtwolman.
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.