Re: Apology to Symantec

Hi Noel

Please forgive me for not forwarding that wordpad doc (I will finish it and
send send it as soon as I get the sick box up and running again). It was
actually your suggestion do write out a chronology that allowed me to make
sense of all of this. I had got two thirds of the way through and realised
from my own notes that Norton was not the problem.

Please DO NOT apologise to Symantec (and especially to Norton). They are
wholly responsible for their own ineptitude where Win ME is concerned.

If I accuse somebody in the wrong then I apologise. It is simply good
manners. In my opinion, ME and 98SE are more vulnerable to this trojan than
XP because of the amount of DOS based stuff there is in the startup process.

I still doubt (but I may be wrong - wouldn't be the first time!) that your
problem was caused by a Trojan .......

It is caused by a trojan

......... - and certainly many people's problems in the
ME group CANNOT be ascribed to such a Trojan (have you
managed to find ANY references to it? - links please!!).

I'm not stating categorically that the problems faced by Norton users
running ME are the result of trojan code. What I am saying is that this
machine was affected by it. I have found no references to such a trojan
anywhere.

Even assuming that the problem is as you describe - they should have had
some means to remove the infection (is there a dedicated cleaner
available? - link??) and should have publicised it widely.

Why should Norton already know about it?

Have you had the 'Trojan' you found analysed by the AV companies? - could
you send me a link to it - or the original infector??

I have not been able to capture the trojan (what do you think I've been
trying to do for the last three days?). I obviously do not have the
technical expertese to find it. I have tried, and tried to find it, but I
can't. What I can do though, is by process of illimination, work out what is
happening. Indeed, it was your suggestion for me to produce a chronology
that allowed me to do this. Take the counterfeit error message as an
example. When I look at it now, it's so obvious. The logo is fuzzy (a copy),
the font is wrong, the text just wraps (it is not nicely spaced out). It's a
fake. It's like seeing a pair of Nike trainers at a very low price on a
market stall. If you really look at them closely you realise that they are
not the real McCoy.

I am of the opinion that the user inadvertently downloaded a malwarez
version of a valid IT Security product, rather than the real thing. It is an
opinion, I cannot prove it.

Greg

Clarence (Lancy) Howard
nutz7777@xxxxxxxxxxxx (remove one of the 7s)


.

Relevant Pages

  • Re: BIOS disabled HD "safe" from viruses?
    ... If you can't write to it, a virus or trojan can't either. ... I'd class this as opinion rather than fact, ... I'm not sure that I'd go to the trouble of BIOS disabling it--or even if my ...
    (microsoft.public.security.virus)
  • Re: 2 files titled Systray.exe? Worm maybe?
    ... installed version of Norton didn't find any infected files. ... I installed a firewall over the weekend and there have been ... Try running a trojan scanner like ... install the free Sygate ...
    (microsoft.public.win2000.security)
  • Re: RE: Andrew Z Carpenter:
    ... I cleaned a trojan from a client on ... So, they've paid norton, Norton has named the critter and told them it can't ... vendors databases to get the best removal instructions. ... > people that have major problem expect a TV commercial to ...
    (microsoft.public.security.virus)
  • Re: Danger warning! to the public and note to Databaseben
    ... you were correct about the Norton and McAffee virus scans. ... I did run another Ad-Aware SE full scan last night, and it did not find any ... more traces of a Trojan Horse. ... You mentioned that the trojan downloader was quarantined, so do ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Local Security Settings / secedit.exe
    ... Interesting that although I carefully keep my Norton up to date, ... >>of the machines that is set to permit access to my hard ... >>suspected a trojan or other bad actor, ... >>is secedit.exe and it only runs at boot and then closes ...
    (microsoft.public.win2000.security)