|
Smokey, for your CC theory to work in NATS you could only change the post url in the join form. Everything else is to wrapped around nats and would break something big enough you would notice. If we can toss out theories, then a iframe exploit in smarty could do the same thing.
NATS doesn't store, record, pass through, or even see/touch/smell any credit card data.
Paul Markham, your yap doesn't stop does it? You have asked these same questions with a different twist 30 times now, and each time they have been answered for you.
a) Admins are able to see what is being pulled from the databases on connections. No deep cover up here.
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.
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.
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)
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.
Minusonebit posts/article is filled with easily provable lies and slander.
|