Slashdot Mirror
Comcast Thinks About Stopping Zombies
LehiNephi writes "Comcast has finally admitted that its users are responsible for a large amount of spam, and they are thinking about how to stop it. Apparently they haven't been turning a blind eye to the problem after all. The simple, blanket approach of blocking all traffic on port 25 would have too many side effects, particularly for users running their own mail servers. However, they can block that port on individual cable modems-a sort of surgical strike. As far as I'm concerned, the sooner they implement this, the better!"
This clearly violates the right to maintain your own SCO-attack zombie.
"We're the biggest spammer on the Internet," network engineer Sean Lutner said at a meeting of an antispam working group in Washington, D.C., last week.
Seconds later, bangs, thrashes, and pleads for mercy in a very Lutner-like voice could be heard from outside the conference room.
The coolest voice ever.
However, they can block that port on individual cable modems-a sort of surgical strike.
Bit like Whack-A-Mole, then?
The coolest voice ever.
Won't someone please think of the zombie child processes?
"You shot the zombie flanders!"
"He was a zombie?"
What did the vegetarian zombie say?
"Graaiiiinnnnsssss"
http://www.brains4zombies.com
Old unix hackers don't die, they just turn into zombie processes.
I'm sure I'm missing a ton.
no
Research has shown that stopping zombies requires blowing their brains out. It's them or you, so don't hesitate. BTW, more recent research suggests that the FZVA is a front for the vampires, so you're on your own when you stake 'em and bake 'em. We've got a SOLASER to destroy the biters, but the shamblers still require brute force.
--
make install -not war
No, it's not too harsh. Suspend their service, send them a note saying that they've been compromised, and they need to clean up their PCs.
Restrict their accounts to only allow port 80 to known good spyware/malware cleanup vendors, and go from there. AdAware + SpyBotSD + Symantec (Corp Edition) seals up a box nicely, or at least cleans it up temporarily.
I've been slowly teaching the other firefighters in my volunteer fire dept, and they're learning. They're not the most computer literate, but you give them a few links, and they can download what they need, and go back to viewing pr0n with less worries than before, or can at least clean up the computer afterwards...
can at least clean up the computer afterwards...
Somehow I don't think you meant what I interpreted this as...
Now, now. Don't you know it's some kind of divine right to have your own server. If you're educated and all it's OK. You know what you're doing. It's the OTHER people that are at fault. Blame them, Joe and Jane "We have unlimited service. We can do whatever we want". I even think it's in the Constitution somewere. If not? Well all the geeks can organize (something like a union) and get a majority of the states to make it OK to have your own server on a consumer-grade (at consumer prices) broadband connection. WE ARE GEEKS, HEAR US ROAR!
Get an axe.
That's right. All your base.
Ironically enough, he didn't need to win any election to get his seat in the first place...
I envy your optimism.
Them: "How may we help you?"
You: "Please unblock TCP port 25, both ways"
Them: "Um, what?"
You: "I need you to unblock TCP port 25. It's blocked on your network."
Them: "Oh. Okay, um, what version of Windows are you running?"
You: "It doesn't matter what I'm running, I just need you to unblock a port."
Them: "Can you right click on 'My Computer' and select 'Properties'?"
You: "No, I'm not going to do that. All I need is for you to unblock a port. My mail isn't getting through because TCP port 25 is blocked."
Them: "Oh! I understand now. *flip flip* Our mail server runs on port 110, not 25. That must be your problem."
You: "I know that, but I'm not trying to connect to your POP3 server. I just need you to open TCP port 25 so that my SMTP server will work."
Them: "Uh... We don't support SMPT mail. Only POP."
You: "Look. There is a port blocked on your network. I need it unblocked. Is there anybody there who can help me?"
Them: "Your port isn't working?"
You: "Yes. It isn't working and I need it fixed."
Them: "I don't think I can help you. Maybe you should take your computer to a technician and get that port fixed."
You: "I don't think you --"
Them: *click*
This would be a whole lot funnier if I hadn't had that exact conversation with a phone monkey at Bell last year when they thought it would be a great idea to quietly block port 25 inbound for all of their customers. It took me three calls to even get transfered to somebody who knew what a TCP port was and even he was surprised to find that it was being blocked.
My new ISP has clue.