Will Eset add detection for Sony's "rootkit"?

Discussion in 'NOD32 version 2 Forum' started by sir_carew, Nov 4, 2005.

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

    DonKid Registered Member

    Joined:
    Jun 27, 2004
    Posts:
    566
    Location:
    S?o Paulo, Brazil
    Good Day,

    I know that, but Sony´s rootkit it isn´t so difficult to find right ?:D
     
  2. Smokey

    Smokey Registered Member

    Joined:
    Apr 1, 2002
    Posts:
    1,514
    Location:
    Annie's Pub
    Didn't Ronjor already answered the questiono_O?
     
  3. Mele20

    Mele20 Former Poster

    Joined:
    Apr 29, 2002
    Posts:
    2,495
    Location:
    Hilo, Hawaii
    I hate to have to say this but it is Symantec and Computer Associates that I now have to respect more than Kaspersky (KIS 2006 beta I use) and other AV companies including Eset. Symantec has made a removal tool as has CA. Kaspersky is still discussing the matter like Eset. I suppose smaller AV companies are afraid of Sony. Symantec is so huge they don't fear Sony. Kaspersky does detect and remove the first backdoor that utilizes the Sony rootkit but has not classified XCP, from First 4 Internet Ltd., as a security risk that should be detected and removed. Never thought I'd see the day when I actually had to say that Symantec (and CA) have been the most responsible AV vendors of all in their response to this threat. (Of course, I have ProcessGuard so I am protected but for all those who need protection most AV vendors have failed their customers miserably).
     
  4. DonKid

    DonKid Registered Member

    Joined:
    Jun 27, 2004
    Posts:
    566
    Location:
    S?o Paulo, Brazil
    Hi Mele20,

    I agree with you.
    Let´s wait to see what will happen.
    Kaspersky will include that rootkit as a riskware.
     
    Last edited: Nov 12, 2005
  5. ronjor

    ronjor Global Moderator

    Joined:
    Jul 21, 2003
    Posts:
    163,883
    Location:
    Texas
    I think anyone reading this thread will agree it has gone beyond a support question concerning Eset.
    Rather than split it apart, I will close it for the time being. In the event an Eset moderator wishes to reply, he can do so.
     
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.