is: tcp/ip vuln, not?... was: WSCRIPT.EXE , CSCRIPT.EXE replacement for *.vbs

[11a () GMX NET (Bluefish)]

Ehm. In what way did shortcommings of TCP/IP have any specific impact upon
the DDoS attacks? The attack was dependent upon two issues:
  1. ability to fill up the physical bandwith (alas network hardware)
  2. ability to overload local resources (RAM, processor etc)

None of these attacks were directly related to any TCP/IP vulnerability.

Regarding the existing problems in TCP/IP, it simply wasn't designed for
the actuall conditions upon todays internet. Once IPv6 becomes the
main internet protocoll, some problems related to IPv4 will remain only as
a memory. But since huge distributed attacks doesn't rely on bugs to
function, no protocolls will solve that problem.

> camp would have us believe that Microsoft is to blame. But who was to blame
> for the attacks a few months ago against CNN, Yahoo, etc? The attacker took
> advantage of shortcomings of TCP/IP. Ones that can not be corrected without
> serious threats to the capabilities of TCP/IP that we all have come to know
> and love.

..:::::::::::::::::::::::::::::::::::::::::::::::::..
     http://www.11a.nu || http://bluefish.11a.nu
    eleventh alliance development & security team