Reverse Firewalls As An Anti-Spam Tool 513
An anonymous reader writes "VeriSign's principal scientist Phillip Hallam-Baker believes one answer to stopping spammers and even crackers is by using reverse firewalls. He says reverse firewalls should be embedded in every cable modem and wireless access point for home users. "A traditional firewall is designed to stop attacks from the outside coming in; a reverse firewall stops an attack going out," Hallam-Baker said. Apparently, a reverse firewall would reduce the value of recruiting your home PC as a member of a botnet because "normal users have no need to send out floods of e-mail, which reverse firewalls can stop, but they do allow a normal flow of e-mail. ""
This isn't normal behavior? (Score:2, Informative)
Re:This isn't normal behavior? (Score:2, Funny)
Re:This isn't normal behavior? (Score:3, Informative)
Re:This isn't normal behavior? (Score:5, Insightful)
I know I've had my firewall setup to block outgoing port 25 traffic that doesn't come from the mail server for a long time now. I also log outbound port 25 requests, and twice this has alerted me to when one of my users was infected with a mass-mailing trojan.
Anyone who runs a firewall and does not currently have it set up similar to this should block outgoing port 25 connections that do not originate from your mail server immediately.
If you're running any reasonably modern firewall (or using Linux and iptables for your firewall) this is fairly trivial to setup.
Come on, guys. Let's all do our part to stop spam. Every little bit helps.
Re:This isn't normal behavior? (Score:4, Funny)
Windows XP SP2 will include a reverse firewall that is enabled by default. Unfortunately it will be released, for compatibility reasons, after Duke Nukem Forever.
Principle Scientist for Verisign? The same company with the terrorists/geniuses (what's in a name?) who decided to hijack the DNS system and send it to a search portal that pays them money each time it gets used? Thanks a lot. I'll take advice from a great company like that.
Re:This isn't normal behavior? (Score:3, Interesting)
Sorry, can't do that. I frequently use telnet out of workstations on my network to connect to port 25 on other machines to verify SMTP setups are correct there.
I also use P2P software that has random port assignments, so a small proportion of the users I connect to with that will be on port 25, and I'd rather not interfere with
Re:This isn't normal behavior? (Score:3, Interesting)
Sorry, can't do that. I frequently use telnet out of workstations on my network to connect to port 25 on other machines to verify SMTP setups are correct there.
Okay, so you create exception rules for the *specific* machines that you will be working from. Either that, or you connect to one central machine and do the majority of your testing from there, by remote access (ssh, VNC, whatever).
Personally, I'd suggest the latter, as it allows you to easily set u
Personal firewall setup (Score:3, Funny)
I believe there is a future for this afterall:
"welcome to the setup of your personal firewall. To install some personal settings please anwswer the following questions:
- Do you click on banners.
Yes / no / Banners?
- Do you use floppies and CD's provided by your idiot neighbour.
Yes / no / also from my uncle
- Is your default webpage www.msn.com.
Yes / no / Banners?
- You have created a personal webpage about your hobbies.
Yes / no / with my cat
- Running Outloo
Re:This isn't normal behavior? (Score:3, Informative)
On the mail server front, while many smaller sites send mail from MX listed servers, this isn't always true at larger sites (such as most ISP's) as they use different sending servers than receiving servers. This is what SPF, domainkeys, etc are supposed to take care of. Until they are universally adopted, blocking based on those DNS records (or lack thereof) will not be effect
Re:This isn't normal behavior? (Score:4, Interesting)
Compared to the 900+ viruses/spams/worms that get 550'd every month, I'd call that acceptable.
Re:This isn't normal behavior? (Score:5, Informative)
You mean, like Firestarter?
http://firestarter.sourceforge.net/
It doesn't require any knowledge to configure the firewall.
Wouldn't software firewalls do this as well... (Score:2)
Re:Wouldn't software firewalls do this as well... (Score:4, Insightful)
I'm not sure this is an option that the average windows user (and almost anyone sending out spam on their virus laden pc uses windows) would find simple.
Working as a support tech and dealing with mainly connectivity issues, I've learned that the number one issue blocking users from desirable online actities or access itself is a firewall. It used to be that the first troubleshooting step was to check the connections. Now it's become, check for firewalls.
I'm not sure the average windows user would find this a simple solution.
Re:Wouldn't software firewalls do this as well... (Score:2)
Re:Wouldn't software firewalls do this as well... (Score:3, Insightful)
I know
Re:Wouldn't software firewalls do this as well... (Score:2)
If it's a hardware firewall, it makes it much more challenging for a hacker-program to be able to disable it to "get out".
Virus could disable software firewall (Score:5, Interesting)
No, for a "reverse" firewall to make any sense, the firewall must be on a different machine.
Re:Virus could disable software firewall (Score:2)
Not if the system is set up properly. For example, under Mac OS X the user does not have root privileges by default. Instead the user needs to authenticate himself every time he performs any changes to the root system or anything else outside of his own user account for that matter. This makes it very difficult and much less likely that a virus could get root privileges.
So,
Re:Virus could disable software firewall (Score:3, Interesting)
A 'software' firewall residing on the PC in question does have several merits.
It can check which software is trying to open the connection and filter on application instead of filtering on port and/or adress alone.
It's also simpler to implement since it's just a piece of software to load.
But it also requires the user to accept or reject applications requesting access (and knowing users, they will just click accept all the time).
It is also possible for malware to trick or disable it.
Re:Wouldn't software firewalls do this as well... (Score:3, Interesting)
The problem is not just to monitor the traffic, but to apply uncircumventable precautions against unallowed behaviour. For a similar, yet a lot tougher solution, my cable provider blocks a port(port 80 right now) at the Cable Broadband Router level(the other side of my connection) and similarly, a DSL provider could do the same at the DSLAM level. That most providers don't do this is that
1) it increases the per-user cpu cost at the edge of their network
2) it increases the s
Re: (Score:2, Insightful)
Re:Not just for spam! (Score:2)
Re:Not just for spam! (Score:3, Insightful)
Good Idea (Score:2)
support mandatory default reverse firewalls for
any equipment that so much as touches IP.
And who will control what to control? (Score:3, Insightful)
This looks like yet another way to force us to use the Internet in the way that corporations/governements want us to. No fucking thank you.
Re:And who will control what to control? (Score:5, Insightful)
You do realize that this isn't a discussion about a law to make it illegal to connect to the internet without such a reverse firewall, don't you? How is this guy's (not so hot) idea forcing you to do anything?
Re:And who will control what to control? (Score:3, Insightful)
Did you actually read anything?
He says reverse firewalls should be embedded in every cable modem and wireless access point for home users.
He certainly does think it would be a good idea to require a reverse firewall before connecting to the internet.
Idea becomes discussion ... discussion becomes policy ... policy becomes law. And Dhakbar says "Why, O!, why did this happen?"
Re:And who will control what to control? (Score:5, Informative)
Re:And who will control what to control? (Score:3, Informative)
Re:And who will control what to control? (Score:4, Insightful)
If you want access to a blocked port, i'm shure that you could easily open it. But this is not about "computer experts" or something like that, this reverse firewall aims the average computer user. They are the ones whose computers are beeing used as spam spreaders by someone else.
Re:And who will control what to control? (Score:5, Funny)
Can it it be configured to block port 1984?
Re:And who will control what to control? (Score:3, Insightful)
No, that is the right response to a dumb ass comment. If someone doesn't understand something, that's fine - it probably can be learned - but the assertive attitude combined with utmost stupidity and ignorance goes on most people nerves.
The only "problem" is that he cares and can't take it any more. In the old times most comments (and stories) used to be fairly intelligent. In case you haven't noticed, it's been getting real bad - now about 20% of content is u
A better idea... (Score:5, Insightful)
But that would be silly now, wouldn't it? Sure, it would cost a lot a migrate your mail clients and mail servers to a hypothetical industry-standard "enhanced SMTP" or something like that, but wouldn't we all be better off in the long run?
Re:A better idea... (Score:2)
Re:A better idea... (Score:4, Insightful)
We shouldn't be grafting band-aids and restricting the network model to fix a single broken protocol. SMTP is the problem. Fix it and leave everything else alone. You wouldn't propose mucking around with TCP because any other application layer protocol was broken.
Re:A better idea... (Score:5, Informative)
It seems your proposing the same argument the article does. Basically security needs to be enabled by default. The internet is no longer a place where you can trust. They are suggesting a hardware fix, your suggesting software.
Either way it will most likely require some pretty big players like AOL or Microsoft to implement it before it would achieve critical mass. Designing a different way of doing things isn't hard, it's getting everyone else to agree to it and use it.
AOL started implementing SPF to stop spam. If AOL/MSN/Yahoo all decide to stop accepting mail that doesn't come form SPF using sites, adoption should happen in about a fortnight.
Re:A better idea... (Score:2)
Re:A better idea... (Score:5, Insightful)
We had a password checker for our users (when I was at an ISP) that prevented stupid user dictionary attacks back in 1994/1995. A little user hassle at that bottleneck prevents a world of hurt later on.
Re:A better idea... (Score:3, Interesting)
Not saying I disagree, just playing devil's advocate.
Re:Incorrect analysis. (Score:3, Informative)
Sam
Off by default (Score:5, Interesting)
Similarly, few individuals have a desperate need to run their own mail server, so ISPs should only allow mail connections to their own mail servers unless the user asks otherwise. How hard is that? Someone tell me this wouldn't have a major impact on spam zombies.
You could do the same for pretty much every unpopular service and just have an account page where users can specifically turn on services they need.
Re:Off by default (Score:5, Interesting)
He is right.
ISP's should block port 25, that is a definate yes at this point in time. But, when a user wants port 25, they should be able to ask and recieve.
Your average cable/DSL user is probobly still using their free yahoo or hotmail account to check email. Maybe they made an ISP account now that POP3/SMTP is offered, but they probobly have no need for an external mailserver.
The next guy up--the one who wants the mailserver--is either someone who knows enough about the internet and can deal with the attacks on their system, or some corporate exec who is told that he needs to do this to check his email. They could have a little quiz about security and if you do well, you get port 25, if you dont do well you can either take a little online class or maybe just buy a NAT box (maybe with a reverse firewall).
Re:Off by default (Score:5, Insightful)
1. You can use any domain name(s) you want so you don't every have to change your address as you change ISPs.
2. Your ISP (or anyone else) can't read your mail while it's sitting on your own server. They can read it when it sitting on their server.
3. SPAM prevention. when you run your own server you can alias your account as many times as you wish, and are able to add/delete aliases instantly and at will. When you give a unique address to each entity. If you get spam on an address, you delete it and create a new one.
4. No limits on message content or size. Many ISPs limit the size of attachments. Granted, SMTP is not meant as a file transfer protocol, but that's not a reason to arbitrarily limit the size of messages.
5. Notification. When you own the server and new mail comes in you have have the server forward the mail to multiple places, or run scripts to notify you on a pager, via telephone, etc.
6. Reliability. At least with My ISP, my mail server has a higher availability than theirs. Because of the load on the server from SPAM, it goes down fairly regularly and is frequently backlogged. Sure this is just poor admin on their part, but with my own server it doesn't affect me.
Re:Off by default (Score:3, Insightful)
1. You can use any domain name(s) you want so you don't every have to change your address as you change ISPs.
You can do this easily with email forwarding by your domain registrar. Most charge less than $10/year for the service. As an added bonus, if your mailserver machine goes down for whatever reason, you will still get your mail. If your domain registrar doesn't offer this, you could easily get it from somewhere like
Re:Off by default (Score:5, Insightful)
Many (most?) MTAs now support the STARTTLS SMTP command. Set up your own mail server, create a self-signed certificate, and a remarkable fraction of your email will be automatically encrypted during the transfer. Even much of my incoming spam is encrypted in this way. Since it comes from all over the world, this actually serves as a useful mask for anyone doing traffic analysis.
Your ISP could still intercept your mail with a man-in-the-middle attack, but that's far less likely than browsing your mail files on their server.
Well, mail server unreliability is a problem with many ISPs. Even though my ISP's server works most of the time, I still can't log in and run "mailq". I do that regularly with my own server, and I depend on it.
While I personally avoid sending large attachments, I can't reasonably object when it's done between consenting parties. So I don't see this as a valid argument against personal mail servers, but rather a strong argument in favor since the ISP's mail admin doesn't have to be a consenting party.
Do you really want it to poll every minute? When you run your own mail server, you don't have to decide between overhead and quick notification of incoming email. Maybe you don't see the need to be notified of new email that quickly, but what right do you have to impose your personal preferences on others?
The bottom line is that I feel very strongly that there are many perfectly valid reasons for individuals to run their own mail servers, and no ISP should deny them this right as long as they don't bother anyone else, e.g., by sending spam.
This isn't just about the right to run personal email servers. It's about something much more important and fundamental: preserving and protecting the end-to-end model that made the Internet such a success. If we permit ISPs to encroach on the end-to-end principle for what may appear to the naive person to be "worthy" reasons, it won't end until it becomes almost impossible to innovate with new and useful end-to-end services.
Re:Off by default (Score:3, Interesting)
1. If you host 7 domains (as I do), paying $70 per year for external forwarding services becomes a significant fee. It's certainly unnecessary. My mail server is also my firewall (among other uses) and everyone should be running some sort of firewall.
2. Sure my mail can be read in transit with a sniffer, but this starts to become questionable practice. It also requires some effort. With messages stored on their server anyone with access
Re:Off by default (Score:2)
1)You want all mail logged by your mail server for legal/verification purposes
2)Your ISPs servers are down
3)Your ISPs servers suck
4)Your ISPs servers are on a black list for some reason
I'm sure I couldd think of a dozen or so others
Re:Off by default (Score:3, Interesting)
I've annoyed a few ISP's, by refusing to use my account with them. I have a perfectly good (like, *REALLY* good) mail server where I work. I use that. Why do I have to feel locked into a provider, just to deal with messages that are stuck in their queue for hours or days?
I usually try out the provider's mail server when I change connectivity providers, and then come to the same decision I always do. I don't use their account. Why should I deal with it? When I check back i
Re:Off by default (Score:4, Insightful)
I did exactly that. My mailserver works better for my purposes than that of any ISP I have ever used. I found what works best for me and implemented it. Who are you to say that my solution of running my own mailserver is wrong?
All those other reasons you lumped together as "specious excuses" are valid reasons. An ISP typically has hundreds, thousands, or even tens of thousands of users. They have massive mail servers that are designed to provide service to those vast quntities of users. My mail server is used by only a very few people (4). It is a lot more suitable for my needs than my ISP's server is.
Re:Off by default (Score:2)
And finally, I gain access to that email site via the mail program on my mac. I do this to integrate with my address book, which also integrate
Re:Off by default (Score:2)
Re:Off by default (Score:3, Insightful)
Re:Off by default (Score:2)
Re:Off by default (Score:4, Interesting)
The days of the free, trusted internet are gone. Look at it this way: any competent sysadmin runs a firewall on a box that blocks all incoming ports except those which the admin knows are in use. Doing the same with outgoing traffic is not a bad idea, especially considering that most people whose computers are sending these massive crapfloods have no idea what's going on. We've got to protect the internet from itself or it will render itself practically useless.
Oh yeah, router manufacturers will buy this... (Score:5, Interesting)
I suppose the router manufacturers will take this step, which would certainly generate more tech support calls and higher engineering costs, out of the goodness of their hearts?
The manufacturers are in a beautiful position on the spam/virus issue - they just route the packets, virii are Microsoft's problem. Why rock the boat?
Re:Oh yeah, router manufacturers will buy this... (Score:4, Informative)
"Virii" is, and let me put this gently, not a goddamn word. I say this not just for your sake, but in the hope that at least a hundredth of the people operating under this painful warping of the english language. Read this, I beg you [archive.org], and stop making me - and anyone who knows the word - cringe.
Re:Oh yeah, router manufacturers will buy this... (Score:2, Funny)
The Journey of 1,000 miles (Score:2, Insightful)
Ha! Beat you too it! (Score:2, Funny)
No hackers for me, no siree!
Reverse firewalls? (Score:5, Insightful)
The other article is really describing a completely different thing. They use the same term, reverse firewall, but they talk about firewalling each individual machine inside a lan. Basically, they suggest a firewall on each machine to protect the internal network from attacks that originate inside it. Completely different use of the term.
It sort of looks like the submitter just googled for "reverse firewall" and posted the first match. Or actually it appears to be the 4th match. Anyway, regardless, the two links seem to be talking about different things. Both of them have merit, but neither seems particularly innovative. I do like the first articles idea of rate limiting outgoing email on home router boxes by default. Seems like it would solve a lot of spam problems.
Re:Reverse firewalls? (Score:2)
Great Reverse Firewall for Mac OS X (Score:5, Informative)
A cable modem with a reverse firewall sounds nice but I would rather handle this at the CPU level. I want to choose what to block and accept.
Re:Great Reverse Firewall for Mac OS X (Score:3, Informative)
As long as you make sure requests to "localhost" are allowed, you should be OK.
Nathan
Just had to (Score:2, Funny)
reverse firewall? what? (Score:5, Interesting)
All kidding aside, all capable firewalls do have outbound protection built into them. Consumer software firewalls monitor which programs are allowed to access the internet, for example, and enterprise-level firewalls allow you to define heuristics to block certain traffic patterns.
So, basically, the article is just suggesting a new name for an old concept. Really, the author wants consumer networking devices to have more capable firewalls.
He's missing something: home PCs aren't spam-generators, they are spam relays. The spam has to be getting in somehow, and that is something a normal firewall should be able to stop. On top of that, they have downloaded a trojan or been hit by a worm to turn them into relays in the first place, which is something a firewall + AV should prevent.
Also, it's probably just as easy to educate 75% of the people how not to become a spam relay as it is to get 75% of the people to buy something with a reverse firewall and then train them how to use it (most people I know just put their computers into the DMZ when they play games because they don't know how to forward ports).
Sure, layered security is a good thing, but I see this as likely to generate many headaches with not much benefit
Re:reverse firewall? what? (Score:2, Informative)
Outbound firewall is still firewall, not "reverse firewall" or "anti firewall" or
Re:reverse firewall? what? (Score:4, Interesting)
They are generating the SMTP connections. Once a virus is on a computer, it can communicate out to its source via common ports, like http's port 80. It doesn't need to use a blockable port (although ports like the NetBIOS port should be blocked to avoid trojans). Anti-virus is a client side solution, and clearly, relying on clients does not work. Plus, there is a lag time between a virus being introduced and the AV software catching it.
I'm not sure that the cable modem is the place to make these blocks either. I would think that they could be more sensibly made at the network router/switch.
I undrestand... (Score:3, Insightful)
Worried about outgoing Spam? (Score:2, Funny)
How much will it be useful ? (Score:2, Insightful)
floods of e-mail (Score:2, Interesting)
do a fresh install,
plug in without any firewall,
and watch how fast the damn thing tries to send out mass mailings
Simpler (Score:2)
permit tcp any eq smtp
deny tcp any any eq smtp
permit ip any any
interface
access-group EGRESS_FILTER out
Fixed!
Re:Simpler (Score:2)
ip access-list extended EGRESS_FILTER
permit tcp any [smtp svr ip addr] eq smtp
deny tcp any any eq smtp
permit ip any any
interface [whatever]
access-group EGRESS_FILTER out
Fixed!
Re:Simpler (Score:2)
deny tcp any any eq smtp
Is this a registery hack?
Where do you set that up on my WIN XP box. I don't see any button marked permit and deny.
Just kidding. I know it's not for Windows. However most of the compromised zombies are Win boxes. They are the ones needing the limit.
There seem to be alot of misconceptions. (Score:3, Insightful)
It is different to software "reverse firewalls" such as Zonealarm as it couldn't easily be turned off by viruses and the like. But on the other hand it lets anything through once.
It would be beneficial to prevent the massing hordes of clueless broadband users from being juicy targets to the spammmer - since each zombie could only send out a pathetically tiny number per hour.
security model (Score:2, Funny)
you're kidding..
The downside of free speech. (Score:2)
I recognize that spam is an inconviniece for end recipients, and a serious waste of resources for networks. Regardless, i feel that a rever
Re:The downside of free speech. (Score:3, Insightful)
All well and good, until
And no matter how inane, idiotic, and offensive it may be, I feel it is protected under the 1st amendment.
Then you have no idea what the 1st amendment is all about.
Software firewalls already do this. (Score:3, Insightful)
Only problem is its impractical to disallow common programs from connecting for themselves. So a trojan infecting one of these would make this feature useless. Perhaps what we need is an "allow x number of connections per y time" feature. That would stop floods and DDOS attacks at least.
Re:Software firewalls already do this. (Score:3, Informative)
ZoneAlarmPro (Score:3, Insightful)
I dunno, chief. (Score:5, Funny)
I'm gonna go to reverse sleep now.
Dangerous twaddle (Score:5, Insightful)
If I buy an "Internet" service I have a reasonable expectation of being able to run any service I can encode in IP packets and have that service routed transparently end to end. I *should* be able to run a VPN, remotely mount filesystems, use VoIP or even run a mailserver if I want to. If I can't it isn't an Internet.
Increasingly, ISPs seem to think that providing a link to their web proxy and a POP3 mailbox constitutes an adequate service. It might be for some people, but it's not the Internet, it's CompuServe revisited. It's good for ISPs though, because they can start charging you extra for "services" which simply involve them removing rules from your compulsory firewall.
Re:Dangerous twaddle (Score:4, Informative)
I've run a redhat/dsl box in my basement for four years. Until 6 months ago I had real internet access. Then they blocked outgoing SMTP. I'm running several mailing lists -- High school alumni with about 60 or so people per list. One in particular can get quite active. I also send out newsletters regarding an upcoming event to 100 people or so.
Reworking exim to use the ISP's SMTP server wasn't a problem, until they actually started counting outgoing emails and disabled my account for a day due to >300 emails/hour.
I figured it was time to move from my "grey" basement server to a commercial host. I was amazed at the price for what I wanted -- $8/month or less! I signed up and had things working in a few hours.
It took a few days before problems really started to appear. Lots of people didn't appear to be getting email from the lists. More research showed that, in fact, although they advertised mailman lists, they still limited outgoing emails to ~60/hour or less.
Two months later, I'm still with them. Looking around I've found that just about everyone puts those same anti-spam limits on ougoing email. Not having limits labels a provider as being "spam friendly", and I am the one suffering. The best I could find without limits was $35/month, which is steeper than I would like.
"We have met the enemy, and he is us!"
Michael
Just to be pedantic (Score:5, Informative)
A reverse firewall, then, is just a firewall. It's like the difference between a slash and a forward slash (pet peeve). In fact, if you use an iptables or ipchains firewall, you only need a few extra rules to implement this on your gateway machine.
Re: (Score:3, Informative)
New??? (Score:5, Interesting)
Standard practice at companies? (Score:4, Interesting)
I set up a firewall at a medium-sized company and the only machine which was allowed to connect to some remote machine on port 25 was the mail server. In a similar vein, the transparent proxy was deliberately set up to break LookOut Express HotMail over HTTP.
Simple things like that, default to deny for both inbound and outbound, virus checking on the mail server: they all greatly reduce the risk of these Windows plagues.
And I thought it was all pretty much standard practice.
I personally think that individuals should take more responsibility for their equipment. It's not really the ISP's business to put in firewalls - perhaps if the users were to pay for the additional service, then the ISP can provide... The individual can always put in a firewall themselves which would only allow port 25 connection to their ISP's mailserver.
Perhaps - a "manditory" additional fee for a firewall for those who do not have an operational firewall?
Just thinking aloud....
So... just crack the firewall (Score:3, Interesting)
Arguing that we should use reverse firewalls to stop exploited PCs sending out traffic to the network is an admission that expecting security on the PC itself is doomed and we should rely on something, anything else - that doesn't run Windows. I think it would be better to attack the real problem and try to make the typical PC as hard to crack as the typical consumer firewall. For those stuck with insecure systems (or systems which make it very hard for a naive user to keep his PC secure) a reverse firewall might be a useful sticking plaster.
Yeah right... (Score:3, Insightful)
This is nothing new (Score:3, Interesting)
Further, any effective hardware implementation will have to keep logs or send alerts because personally, I want to know what's being prevented from going out.
How about "Egress" instead? (Score:3, Interesting)
I wouldn't trust stateful packet inspection on my "modem" as far as I could throw it. The firewall built into my old (not-so)Efficient 5861 DSL router was horrible. It had no statefuly packet inspection, so you were letting in packets on ports outside the realm of established connections. The firewall built into my Cayman 3546 is smarter, but not very configurable at all. It's either on or off and I could map some ports, but it's not nearly as configurable as others.
The only thing I trust is my PF/IPF firewalls in place around the crappy DSL modem firewalls.
Built in to the cable modem? (Score:3, Interesting)
With a firewall in the cable modem itself, the cable company will be able to remotely configure it, and conceivably stop any kind of traffic they want to stop. Don't want you using P2P applications? Just firewall those ports! It's not like you "own" the cable modem anyway (most people just lease one). And even if you do own, they can just write a clause into the contract giving them rights to remotely configure it.
Before you know it, cable modems without such firewalls will be banned from the network.
Sorry, I'm not installing any piece of hardware that I don't own, is under direct control of the cable company, and can be used to filter my outgoing traffic. Not in a fucking million years. And definitely not in the name of "stopping spam."
"Stop spam" has become the cyber equivalent of "Save the children." It seems we're willing to throw away far too much in return for too little benefit.
Re: (Score:2)
Re:Are they user proof? (Score:2)
Sure. Setup a basic word filter to look for "enlarge" and "penis." Stop all e-mail that matches.
Re:Are they user proof? (Score:2, Insightful)
Re:Are they user proof? (Score:2)
ZoneAlarm software firewall already checks... (Score:2)
ZoneAlarm software firewall already checks for unreasonable outgoing email, and asks the user if it is okay. ZoneAlarm check time, number of recipients, and attachment reasonability.
Re:Obligitory form-letter post (Score:5, Informative)
(x) Users of email will not put up with it
Actually if implemented properly (allowing people to configure it) people WILL put up with it..
(x) Requires immediate total cooperation from everybody at once
No. Every user that gets one of these things helps.
(x) Lack of centrally controlling authority for email
Huh?
(x) Open relays in foreign countries
No. Every user that gets this helps.
(x) Ideas similar to yours are easy to come up with, yet none have ever been shown practical
I think this is practical. Just like a regular firewall is practical. (Might as well make this thing a proper full blown hardware firewall)
(x) Countermeasures should not involve sabotage of public networks
(x) Countermeasures must work if phased in gradually
Pardon?
(x) This is a stupid idea, and you're a stupid company for suggesting it.
Yes - very amusing. We're all laughing at your stupidity.
This is not a fix-all solution. But it's a simple solution that would help to alleviate some of the spam problem.
Re:Egress filtering (Score:3, Interesting)
For example, from our webproxy we allow connects to certain ports only. The proxy can connect to ports like 80 and 443 (and some high port ranges).
This works well 99% of the time, but sometimes sites setup a second server on a port like 81 and it cannot be connected.
There could be some magic like "the proxy software is allowed to do it but another process on that machine isn't". That is like ZoneAlarm.
However, I question the utilit