Thanks but I wanted John to anwer it. However.
Quote:
Originally Posted by TheDoc
a) Admins are able to see what is being pulled from the databases on connections. No deep cover up here.
|
So when they investigated this they saw what was being pulled, could they see how the user was getting in and the IP address?
Quote:
Originally Posted by TheDoc
b) The problem a few months ago was "DIFFERENT" but yes, it was unknowingly related. I'm not sure why that is hard for you to understand or get.
|
Seems to me it was the same problem, this investigation was not good enough. The posters on GFY found it fast enough.
Quote:
Originally Posted by TheDoc
c) Since they didn't know the extent of the problem at that time they only notified clients with the current related problem and not the unknown one.
|
Did they notify people they thought "at risk" or people who had already told them about the problem? We have yet to see anyone step forward and say "TMM alerted me to this without me asking them about it."
Quote:
Originally Posted by TheDoc
d) Clients are told about the IP lock feature and admin accounts during setup. It's the first thing in the config admin of nats. And it "CAN NOT" be forced on by NATS since NATS can be locked fully out of the system, just by turning the account off. (FYI, most clients used it)
|
I would say they should of found the problem and TOLD their clients how it was to proceed. Then changed the safer method to the default. By not doing so they left the door open.
Quote:
Originally Posted by TheDoc
e) I think John threated to send a C&D, that isn't the same thing as legal action. Unless he recently said something different, the last I saw it was a C&D threat.
|
Do you think sending a C&D to people you know are telling the truth is right? Or maybe he did not know they were telling the truth that his program was compromised.
You see the problem goes a bit deeper than you think. In my opinion. Either TMM were not able to find the problem that others found in minutes or they did not want to.