AltGrendel wrote: > On Tue, 2004-01-20 at 18:28, Fred wrote: >> >> I can not imagine what it would be like to work for an abuse dept. at >> an internet company and receive hundreds or thousands of complaints >> about customers computers being hijacked or turned into spam zombies. >> > Non-original joke: > > I think that job is usually assigned to /Dave/Null.
<grumble> That's what I'm all worked up about. If these large broadband providers were more pro-active a lot of things would be different. Take the following events for example: Massive DDOS attacks which take down large sites like yahoo.com and many others. Massive Habeas forgery causing mass-confusion on why people are seeing spam. (majority cable / dsl zombies) Preventing those people who choose to use our computers without our permission and knowledge. Most people I know have to pay for their cable & DSL connection and they pay way too much money for it. Maybe a simple solution would to be making the cable / dsl customers receive a new IP address every 2 hours? I am sure this will anger many but would make spam advertised sites go down much faster. Give all cable / dsl a private IP address and allow real IP if requested. Those who are not familiar with the internet tend to get themselves into trouble by accident. Protected behind a private IP would protect them from many of the issues I'm upset about. That alone would have helped to prevent spread of Blaster type worms. Why leave un-knowing people in front of the defenses when they don't even know a war is being waged. >From a litle research I find that cable & dsl are being used for hosting the spam content as well as DNS hosting for their domains and also for sending the spam messages. If we take out that massive source of zombies the spammers would be in deep trouble. They would be force to pay for hosting, or hack into companies / schools which would make them more likely to be caught. Or funnier yet, hack modems for hosting, that'll be the day! If I'm going after a website for spamming me I target the following in order: Step 1: Whois records, against valid contact information. Many registrars say they will suspend a domain for invalid contact records. Step 2: Next comes DNS servers. Check the domain name on the dns servers and attempt step 1. Step 3: Netblock of website. Most times I find a massive listing of cable / dsl zombies used for hosting website. Step 4: Netblock of DNS provider. Same results of step 3 found. Step 5: Get mad and give up. Re-think attack and plan new methods. </grumble> Frederic Tarasevicius ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
