Attack code puts Windows PCs at risk

TalkBack 21 of 117:

Next »

« Previous

• Thread View
• Flat View

Your neurons are misfiring again as in the cited URL

``Quite frankly, I don't really care if there are 144,000,000 exploits that require open ports, I'm protected against every single last one of them

This exploit doesn't require an open port (since the vulnerability is in the client, not the server) and therefore, this scenario is quite obviously handled correctly by my quote.''


And this is exactly WHY yoiu lost the previous argument and you are losing it AGAIN.

In your little un-realistic world, "open ports exist only in the "servers" so your client + FW MUST be OK".

WHO TOLD YOU THAT "client Hosts" have NO Open Ports? Do a

netstat -a -o

in your "client" PC and tell me what U see there.

As I SAID THEN (and if U cannot read, ask your daddy to read it to U) ANY process can OPEN a TCP or UDP port and wait until someone contacts it. Processes "PASSIVELY" opennning the ports are called "servers" in TCP/IP parlance, and those openinng a connection "ACTIVELY" are called "cleints". You can have as many TCP/IP clients and servers as you LIKE IN ANY IP host, whether you consider the host a "client" or a "server". U R confused on VERY BASIC things.

Malicious code (by a drive by installs or a crappy active-X, a vb-script from a donwloaded MS office app that ran and didn't give you any signs of that) can OPEN PORTS and expect to be contacted at them. These processes running with your privilleges can use a "privillege escalation" exploit and escalate their authority to admin and then THE ENTIRE pc is taken over completely. Worse they can install kbd spying code and collect all your passwd info, which is particulary dangerous especially when there is NO sign of compromise.


In your contention "if U use your FW U R OK" because it "protects you from all the defects in the programs with open ports". This is at best WISHFUL thinkinking since clandestine code can open ports and even more so it can HIJACK PORTS used by services in your CLIENT PC and LEAVE OPEN BACK and FRONT DOORS.

A s/w FW can be compromissed by carefully crafted sequences of TCP / UDP / IP / ICMP etc. packets and lead to believe that the incomming packet is inocuous.

In you previous line of talkbacks I CITED to U, you were making the same UNEDUCATED contentions as in your head you are confusing the coloquial definition of a keyword with its TECHNICAL definition. Since U lack the technical part you have created ALL kinds of untenable "explanations" in your head....

But using your uneducate impressions about how things work and insisting on them only gives to people who are educated in this field all the right to call you an obstinate bufoon and feel sorry for you.

So as I told U, I make NO effort to redicule you because this happens NATURALLY as you speak ...

Don't overestimate yor intelligence neither do you underestimate the same of others

Got it Cayble guy?

Posted by: michael_t   Posted on: 07/25/06 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

SponsoredWhite Papers, Webcasts, and Downloads

• Virtualization: Architectural Considerations And Other Evaluation Criteria VMware Of the many approaches to x86 systems virtualization available in the ... Download Now
• Three Steps You Need to Know to Stop Data Loss Varonis Sensitive data exposed to misuse or loss... it is the stuff of nightmares ... Download Now
• Live Webcast: Activate Today! Realize ROI with Intel(r) vPro? Technology and LANDesk Intel Join the team from the Intel vPro Expert Center for an informative Webcast ... Download Now