They will suffer the same fate as BF. All they are doing is escalating the war by attacking the spammer's systems and in a way justifying the counter DoS the spammers launch.

They are not going to tell anyone where the servers are? I think the spammers will get clue as to who/where when the attacks start coming in. Hell, sign your name to this project and have it piss off the wrong criminal organization who then comes gunning for you.

Problem is technological, you can not deal with a DoS at the receiving end by simply firewalling since the bandwidth is eaten even if you drop the connects as they come in. The squelch has to happen further upstream preferably right above the ISP hosting the source of the attack. A distributed DoS is nearly impossible to deal with unless all the backbone providers agree to shutdown sources of traffic which I highly doubt they will do (unless is nets them profit).

Now entice ISP's (like colleges do AFAIK) to proactively deal with zombies on their subnets that can/are being used by spammers as relays for whatever traffic and you go a long way to solving 3 problems: spam, virus replication & botnet's. But alas I think ISP's care more about impeding P2P & simply filtering ports than truly solving problems.

The more I think about it the more I think the Govmnt. should have wasted less money on carnivore, etc... and more on getting laws passed giving specific powers to force or entice the participation of ISP's to be able to coordinately filter certain aspects of the Internet quickly. After all, reading packets is not going to stop a child porn creator in some country we have no agreements with but we could shutdown that countries ability to communicate across the major pipes into the US if even temporarily, never mind it could also solve the spam issue.

Bottom line: We are a long way from a real solution and the cure may be worse than the disease.

Stan Zaske wrote:
Possible superior replacement for Blue Frog (Blue Security). Keep your fingers crossed!

http://news.com.com/2100-1029_3-6076617.html

Reply via email to