Slashdot Mirror


Reverse Firewalls As An Anti-Spam Tool

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. ""

513 comments

  1. This isn't normal behavior? by Anonymous Coward · · Score: 2, Informative

    I have Kerio Personal Firewall on my Windows machine and it prompts me about every outgoing connection (to learn it, or allow it, or block it).

    1. Re:This isn't normal behavior? by Anonymous Coward · · Score: 2, Funny

      thank you for reminding me how good it is not using windows.

    2. Re:This isn't normal behavior? by Reverant · · Score: 3, Informative

      It's normal, but it's also very annoying having to click yes/no everytime a process wants to create an outgoing connection. What the author suggests, is a hardware-based firewall (ie one that can't be switched off by a new generation virus - the current ones will terminate for instance any antivirus software they find running), that limits how many emails you can send per minute or hour.

    3. Re:This isn't normal behavior? by Anonymous Coward · · Score: 0

      The software can "learn" what you want allowed and what you want blocked. It's easier than going into your iptables script and specifying the outbound you want.

    4. Re:This isn't normal behavior? by JPriest · · Score: 1
      Comcast started filtering outgoing 25 on "problem machines" a while back. Personally, I like the way AOL blocks mail from all dynamic IP addresses.

      My mail exchanger should be able to _only_ accept mail from IP addresses that are listed in that domains "MTA" records. This stops trojaned PC's from being used as spam relays.

      --
      Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
    5. Re:This isn't normal behavior? by Christopher+Cashell · · Score: 5, Insightful

      Even for LAN firewalls, this is, or should be, normal behavior.

      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.

      --
      Topher
    6. Re:This isn't normal behavior? by shadowmas · · Score: 1

      there is a advantage in windows firewalls that i cant see in iptables. most windows firewall apps allow you to set application specific rules like Mozilla can intiate outgoing HTTP trafic but some other application cant. that drastically reduces the damage done spyware and even helps you find them.

      ofcuz i dont think there are spyware for linux machines yet so its not much of a problem. but still it would be a pretty usefull feature.

    7. Re:This isn't normal behavior? by Reverant · · Score: 2, Interesting

      What if a spyware is packaged like a plugin for your app? For example, most "search bars" for Internet Explorer proxy their traffic through Internet Explorer. That kinda defeats this scheme. Also, what if I rename "my spyware" app to iexplorer.exe? Do Windows check the MD5 hash of the .exe app that claims to be "iexplorer.exe"?

    8. Re:This isn't normal behavior? by halowolf · · Score: 1
      Thats why these types of firewalls, are trainable and learn which processes require network access and which ones don't, so you don't have to click a button everytime a process uses a connection.

      Because of the user interaction, its quite a nice way to learn, which processes are trying to phone home without you knowing. Of course you can set them up so that they block without any user prompts whatsoever, and you add the programs that you wan't to have network access manually. Its really up to the user how they want to use the firewall.

    9. Re:This isn't normal behavior? by Aneurysm9 · · Score: 1

      When I was using Norton Personal Firewall it would reverify everytime an executable changed. Therefore, if you get another prompt and you haven't updated, you can assume something untoward is going on.

      --
      There was Cowboy Neal at the wheel of a bus to never-ever land.
    10. Re:This isn't normal behavior? by luferbu · · Score: 2, Informative

      Kerio Personal Firewall does, when the MD5 change it prompts the user to confirm or reject even an already created permanent rule.

    11. Re:This isn't normal behavior? by Anonymous Coward · · Score: 1, Interesting

      A. You don't use Internet Explorer if you're concerned about security. B. Most of the current software firewalls do keep a hash of the .exe (including the path) and notify/ask about the replacement.

    12. Re:This isn't normal behavior? by luferbu · · Score: 1

      Yes, in practice you should accept anything (check RBL and so on...) if you don't want to lose lots of legitimate mail :)

    13. Re:This isn't normal behavior? by nametaken · · Score: 1


      Even for LAN firewalls, this is, or should be, normal behavior.

      I agree. And this is the most insightful and noteworthy product of "VeriSign's principal scientist". Wow.

    14. Re:This isn't normal behavior? by shadowmas · · Score: 1

      "What if a spyware is packaged like a plugin for your app"

      one of the firewalls that i tested (either kerio or outpost) even checks dll's that run inside a application thereby stoping search bar type spyware.

      but personally i use firefox so i dont have that searchbar problem only standalone spyware that somehow sneak in when you install adware programs.

    15. Re:This isn't normal behavior? by korthof · · Score: 1

      McAfee online seems to do a good job of outgoing monitoring. But it wont find a single good trojan .. grr.

    16. Re:This isn't normal behavior? by obeythefist · · Score: 3, Funny

      Couple of relevant things:

      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.

      --
      I am government man, come from the government. The government has sent me. -- G.I.R.
    17. Re:This isn't normal behavior? by Trejkaz · · Score: 1

      Just remember to open back up port 25 to mail servers that people actually need to get to. :-)

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    18. Re:This isn't normal behavior? by geminidomino · · Score: 3, Interesting

      Eh, when I stopped accepting direct-to-mx mail from dynamic IP addresses, I had exactly 1 legitimate mail get blocked in the first six months, and that was because the sender forgot he'd been playing with Mercury.

      Compared to the 900+ viruses/spams/worms that get 550'd every month, I'd call that acceptable.

    19. Re:This isn't normal behavior? by Purdah · · Score: 2, Interesting

      There is a security flaw with everything that runs locally on a windows machine configured by a home user, and that is simply that once infected all firewall / spam / virus software can theoretically be disabled by a program running.

      The articles point out that if we have some limits set into a hardware product (ie the cable / adsl modem) then we limit the effectiveness of the attack. This is based upon the fact that the spam relay software is to be run on a badly configured system (aka casual home user).

      I like the idea of a reverse firewall, and have throught for a long time that it is about time that something like Smoothwall should be altered to provide functionality as described in the articles.

      By that I mean that home users need something that is simple to setup, has the ability to tell them about typically suspect activity (outgoing port X access, where X is a port known to be used by some unwanted program) and allow the user to define certain limits for users on their home network. And I do mean home network, after all, a corporate network should have a profficient IT person administering it all day and they can set up whatever is required to protect their network.

      A home user needs something that will aid them to set limits for their own use of the internet. For example, if my mom installed such a product and the product asked her "1, Do you use email? 2, Do you use the web? 3, Typically how many emails do you send a day? 4, etc, etc surely this would setup a modem whereby a lot of untoward activity would be reduced by a spam relay infected machine.

      Personally I would like to see a firewall that lets me define which applications are to be allowed on a per machine basis / port set basis. So you could define that the set of ports used by say unreal tournament, would be allowed on machine A, but not on machine B.

      Another example would be if I have two machines, one for myself and one for my child, I would certainly want to only allow me to play violent games online eg RTCF: Enemy teritory which is free to download and install by my child, but I would be warned that they are using it as it would be rejected and logged on the firewall. This would happen for any other product that tried to get out of my lan.

      There are a few flaws, the main one being if all the products started using port 80 (or read the computers configuration and used the proxy). In this case you would need to filter the port 80 requests, but still, it would be a good step to prevent a lot of abuse of infected machines.

      Of course the firewall would also need to have email filters and a net nanny, but such a product should sell well to any parent who is worried about the internet and their childs use of it, assuming of course the manual is in PLAIN english and simply says something to the effect "To get email protection up and running do A, B, C then D".

      It is strange that people working for free, I am talking open source here, do not produce something that is useful for home users. All the OSS firewalls I have looked out require you to have a good to expert knowledge (depending on firewall) of networking in order to effectivly use them. They all seem to be just creating replacements for professional products rather than somehting that is useable by the average Joe.

      Perhaps if they grasped this usabilitly problem, then OSS might finally create a linux distro that is good for the desktop.

    20. Re:This isn't normal behavior? by .+visplek+. · · Score: 1

      I use Kerio too. I use the free version for home users. It also monitors and reports changes to the Windows register and there's extensive logging. It's easy to configure and I had no problems whatsoever. Settings can be exported so it's easy to configure multiple machines. This is a really nice tool to shut up your highly communicative Windows machine.

      --
      - Save a tree, eat more woodpeckers
    21. Re:This isn't normal behavior? by WebCrapper · · Score: 1

      Technically speaking, there are several ISPs that do this. For instance, Earthlink blocks port 25 on all of its connections and refuses mail from dynamic IPs...

    22. Re:This isn't normal behavior? by essreenim · · Score: 1

      Yeah I use Outpost on my Windows OS (very rarely).
      I dont think they are talking about the fact that a reverse firewall would block outgoing traffic - rather that it would detect and prevent the type of outgong traffic of a spam / virus nature etc.
      This might give Microsoft ideas. Longhorn that prevents users on a LAN in work from sendin certain types of data. Hang on nothing new there either???

    23. Re:This isn't normal behavior? by parksie · · Score: 1

      You should be able to do similar things using systrace.

    24. Re:This isn't normal behavior? by walt-sjc · · Score: 2, Informative

      Blocking outbound port25 from dynamics is good. Clients that need to use alternative mail servers can use the submission port (587).

      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 effective.

    25. Re:This isn't normal behavior? by walt-sjc · · Score: 1

      Or use port 587 which is the new MUA standard. Port 25 should be for MTA's only. Since most residential AUP's don't allow servers, people shouldn't be running MTA's anyway. For those that do, they can Still set it to smarthost via port 587.

    26. Re:This isn't normal behavior? by Anonymous Coward · · Score: 0
      "This is what SPF, domainkeys, etc are supposed to take care of."

      Can someone elaborate on this? How do these standards specificially address blocking rogue windows machines used as spam relays? I have only read a small amount of info on those, and aparrently missed that part.

    27. Re:This isn't normal behavior? by 13Echo · · Score: 4, Informative

      It is strange that people working for free, I am talking open source here, do not produce something that is useful for home users. All the OSS firewalls I have looked out require you to have a good to expert knowledge (depending on firewall) of networking in order to effectivly use them. They all seem to be just creating replacements for professional products rather than somehting that is useable by the average Joe.


      You mean, like Firestarter?

      http://firestarter.sourceforge.net/

      It doesn't require any knowledge to configure the firewall.
    28. Re:This isn't normal behavior? by zogger · · Score: 1

      firestarter is Ok but it still gives false positive "hit to your machine" readings, and it's random,not consistent, behavior. Well, at least that's how it happens on my machine, and I've read some other users get that too. A new user could still get confused with it. It's getting closer for a raw beginner but not quite there yet, IMO.

      If firewalling in general was easy to do, we wouldn't see these problems nor need IT security people. It's a difficult art, it takes sophisticated software and an even more sophisticated admin to get it setup right and to keep it setup right, even with GUI clicky tools, on any OS. It's the totality of what you have to do,and what you have to know in advance of going online, and for a noob it is fairly daunting. Just look at "processes running". How is a noob supposed to know what all these various running processes are and what are necessary to keep running and what aren't? "Permissions" in general are fairly complex. Ports listening. If that ain't arcane, a noob is supposed to know what his machine is supposed to be listening to and for what reason, when 95% of what is there to read is written in acronyms based on port numbers? Blocking ports, "stealthing" ports, allow this number, but not that number, block this host or not that host based on IP numbers or a host that looks like giberish-24.089.obscure.cz ? How is a noob supposed to know if that is part of a legitimate web request they just did, is it the ads downloading, is it a hack attempt, is it one of the desktop applets running, or what? The way it is setup now, you still need a bit more than just sit down and use a GUI tool.

      I think what would be nice for casual surfing for the home user would a way to instantly create a virtual OS image,sort of like a knoppix disk does when you boot from it off a CD, while you are online,mash a button it gets created, it is only in cache jailed off completely from the rest of the machine, it still allows you to surf, but no writing to disk by default.

      I think the biggest problem with stand alone machines and desktop computing comes in trying to integrate the networking aspects of it. Your casual user has not a lot of need to have full computer read/write functionalty while online, the computer should drop back to a completely safe mode as soon as you go online, and only open itself back up to full computing power and uses when off-line. Trying to keep both aspects of computing functional at the same time is quite a problem, but if they were really segregated it would be a lot easier.

    29. Re:This isn't normal behavior? by Anonymous Coward · · Score: 0

      no answer, huh?

    30. Re:This isn't normal behavior? by CryptoLogica · · Score: 1

      On a Cisco PIX ... from the wee little 506 to the desktop size 535 for BIG enterprises... its called an outbound access list... nothing new...

      Checkpoint, Netscreen, they all support it...

    31. Re:This isn't normal behavior? by julesh · · Score: 2, Interesting

      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.

      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 it.

      Nice suggestion, though.

    32. Re:This isn't normal behavior? by f0rt0r · · Score: 1

      This is normal firewall behavior. A good firewall setup defaults to blocking all traffic and then you open it up from them. I admit it takes a lot of trial and error ( and google-searching ) to all of your various network apps working, but onces it is working, you just save your settings and can reuse them if you ever have to rebuild/move your firewall.

      Oh, the more popular of a firewall. you use, the easier it will be to find the correct setting to get a network app functioning properly, as there will be more online documentation.

      I am talking about a standalone software firewall...I myself run iptables on my Linux router that handles the three network connections I have at home ( secure network, wireless LAN, and Internet ). Most of the computers run Linux, but the one Windows box I have does run an additional software firewall and Antivirus program...because it is Windows it needs that extra protection :)

      --
      I can't afford a sig!
    33. Re:This isn't normal behavior? by mdamaged · · Score: 1

      > there is a advantage in windows firewalls that i cant see in iptables

      Besides your glaring ommision of stateful vs. nonstateful...

      http://l7-filter.sourceforge.net/

      There goes your "advantage".

      --
      Someone asked me the difference between ignorance and apathy, I told them I don't know and I don't care.
    34. Re:This isn't normal behavior? by mdamaged · · Score: 2, Interesting

      > Sorry, can't do that.
      If you are indeed an/their admin you should easily be able to configure the server to open the submission(or any other) port to test your smtp servers that way. Is that not what ssh is for? ssh in, telnet localhost 25, test away.

      > and I'd rather not interfere with it.
      The amount of users who bind their p2p onto port 25 I can count on one hand, any p2p software worth its merit won't bind to anything below 1024 unless told to anyways.

      This attitude is one of biggest reasons why there are so many infected machines, people won't comply because it breaks their 'Kaaza' and crap, yet they complain when there is no security.

      --
      Someone asked me the difference between ignorance and apathy, I told them I don't know and I don't care.
    35. Re:This isn't normal behavior? by kraut · · Score: 1

      A principle scientist would be someone inve
      stigating principles - in other words, a philosopher. Or maybe a physicist.

      A principal scientist, on the other hand, is the chief scientist.

      Sorry, but sometimes bad spelling just distorts the meaning...

      --
      no taxation without representation!
    36. Re:This isn't normal behavior? by 13Echo · · Score: 1

      I don't have the "false hit problems" because I checked the box in the options that said "ignore hits meant for other machines".

      Have you tried that?

    37. Re:This isn't normal behavior? by bahamat · · Score: 1

      I'd love to get some info from you on setting this up.

    38. Re:This isn't normal behavior? by Zeinfeld · · Score: 1
      On a Cisco PIX ... from the wee little 506 to the desktop size 535 for BIG enterprises... its called an outbound access list... nothing new...

      Nope, nothing new, but when you have 750 words for the complete article you can hardly express every last nuance. Its hard enough to do that in the book where I have 50,000 words. The original article was twice as long.

      Sure others have pointed out the same thing, I was discussing the problem with Vint Cerf a few weeks ago. But there is a big difference between having the original idea and turning that into a reality. I had the piece placed in CNET because I wanted the idea out there, to start the ball rolling.

      The real point I was trying to make here is that we need to put limits on outgoing traffic, its the old firehouse model, fire regulations are not there to protect your house from fire, they are there to stop the fire at your house spreading to the next one along.

      How that is achieved is not important. Port 25 blocking stops spam, but there are also DDoS attacks and other nasties that I would like to stop. Blocking port 25 completely is a serious loss of functionality for some, when I lobby ISPs to put these checks in place they start to whine about the load on their routers. So pushing out the task to the cable modem or the wirless gateway / router box is a way to counter the whine.

      When you look at the behavior of a zombie performing an attack and the behavior of an uncompromised system the difference between the two is usually very clear. There is no reason for any machine on the Internet to be sending spoofed source address packets, no reason for any machine to perform a SYN flood, no reason for any machine to DDoS a DNS server. Spam is actually the hardest case since there are machines that legitimately send out hundreds of thousands of emails a day. But even if someone was hosting the cypherpunks mailing list on his broadband connection they would probably use far less resources than a spammer would.

      Sure Checkpoint and Cisco have this functionality in $2000++ firewalls. What I am proposing is putting the technology in $70 wireless routers and turning it on by default.

      I will be speaking at BlackHat next week on phishing which is one of the nastier criminal scams taking place on the Internet. One of the effects of the phishing scam is that it has forced people to act with whatever security is available here and now, there is no time to wait to develop perfect systems. In the process it has become clear that simple systems with flaws are much more effective than cryptographically perfect but unusable systems.

      The academics have taken us on a ride the past 20 years. Even if they were deployed today IPSEC and DNSSEC would do absolutely nothing against the phishing attacks. OK thats not what they are designed to do, but then again what is there that can be used? S/MIME and PGP don't really deliver the goods here either.

      We need iPod security, security that serves the 98% of Internet users who are not technical or don't want to spend their time doing sysadmin work. So far its been security for gearheads, not security for real users.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
    39. Re:This isn't normal behavior? by rawg · · Score: 1

      Setting up IPTables is not trivial. I'm still trying to figure it out on my Linux routers. I've been put on two DNS block lists already because of it. I guess I'm just going to have to make time to learn IPTables now... As if I don't have enough to do.

      --
      The above is not worth reading.
    40. Re:This isn't normal behavior? by Christopher+Cashell · · Score: 2, Interesting

      No offense, but these are rather poor excuses.

      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 up automated testing scripts that can be run from anywhere.

      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 it.

      Any program that randomly binds to port 25 is BAD[1], and you should get rid of it in favor of a decent program. Applications that need a random port to use should take the first available port that is greater than 1024. On many operating systems, this is enforced by the OS.

      I'd be curious as to which P2P software you're describing, so I can make sure I avoid it.

      [1] Broken As Designed

      --
      Topher
    41. Re:This isn't normal behavior? by Wintermancer · · Score: 1

      Here's one:

      www.turtlefirewall.com . Works well with webmin.

    42. Re:This isn't normal behavior? by sg3235 · · Score: 1

      It's sad that the only technical solution we can come up with for the spam problem is one which limits valid uses of the internet. I don't recall seeing anything in the RFC that restricts who can use the SMTP protocol. My provider does not restrict my ability to have a server and it isn't a small ISP. I do have a static IP, though.

    43. Re:This isn't normal behavior? by adric · · Score: 2, Informative

      Take a look at Shorewall. Much easier to setup (IMHO) than using the raw iptables commands, and works quite well in my experience.

      --
      not plane, nor bird, nor even frog...
    44. Re:This isn't normal behavior? by gi-tux · · Score: 1

      What the author is suggesting is a firewall that someone else would be able to control that would prevent me from doing what I might want to do. It is bad enough that I can't run my own SMTP server (properly configured and secured) to send email straight to others, but what would they impose next.

      If your ISP wants to block your ability to send email, they can block port 25 already on their routers and it is blocked. They do not need to be able to block it at my residence.

      Come on, an ISP can turn off anyone they wish at anytime they wish. But instead of taking a chance of hurting someones feelings, and then possibly having to face some liberal, bleeding-heart judge in the court system, they decide to kill flys with wrecking balls and sledge hammers. It is better to beat the masses into submission than to discipline the guilty party.

      And we wonder what is wrong with our society!

      --
      I have no sig, does anyone have one to spare?
    45. Re:This isn't normal behavior? by zogger · · Score: 1

      yes, I have, sometimes it works, sometimes it doesn't, like I said, it's random, and yes, I've cleaned it out and re installed it. I have also seen this behavior in every version of it I have used going back to rh 7.1. I read it on one of their forums as well, other people have seen it happen. Right now it's playing nice, last week I was getting a buhzillion hits it *appeared*, and I always check off that "ignore redundant hits and hits not meant for your machine". I don't know how to reproduce it other than sometimes I turn my machine on and it happens, other times it seems to act normally like it should.

    46. Re:This isn't normal behavior? by catscan2000 · · Score: 1

      If your P2P software uses dynamic ports, which is likely the case, then those random port assignments will always be greater than or equal to 1024, making it safe to block port 25.

    47. Re:This isn't normal behavior? by Anonymous Coward · · Score: 0

      there is a advantage in windows firewalls that i cant see in iptables. most windows firewall apps allow you to set application specific rules like Mozilla can intiate outgoing HTTP trafic but some other application cant.

      I don't feel like reading through the docs to confirm, but I'm pretty sure that was added to iptables somewhere along the line.

    48. Re:This isn't normal behavior? by glassgnost · · Score: 1

      Windows XP SP2 will include a reverse firewall that is enabled by default.

      Useless, IMO, if UPNP allows apps to open ports at will...

    49. Re:This isn't normal behavior? by cayenne8 · · Score: 1
      "It is bad enough that I can't run my own SMTP server (properly configured and secured) to send email straight to others, but what would they impose next."

      Hmm....I'd suggest you look into upgrading your ISP connection then. I just got the basic business connection from Cox cable...nice fast connection, basic guarentee of services with a SLA...no blocked ports...no limits I read about for traffic...and talk about nice when you need help, no waiting on phone for hours on end. I get pretty quick answer, they take my info, and a service tech calls ME back.

      Only about $67/mo....also with static IP. My earthlink DSL with static IP was only about $5 less a month..and nowhere near this good.

      Seriously, look into this...no problem with running any kind of server you want...

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    50. Re:This isn't normal behavior? by fritmebufstek · · Score: 1

      So he should do extra work because some other assholes can't keep their pc secure ? I agree with him. The irritating thing about admins and firewalls is that it gives them power. A lot of these "admins" cannot handle it, so why create a situation to give them even more power ? ISP's do enough damage to the internet on their own, let's not compound the problem. Oh and another issue : I assume you are going to pay for all those extra support calls too ?

    51. Re:This isn't normal behavior? by v01d · · Score: 1

      Sounds good. Are you able to send email to AOL? WideOpenWest doesn't block my SMTP server, bu at least AOL and Adelphia won't accept email from me because I use cable.

    52. Re:This isn't normal behavior? by mountiealpha · · Score: 1

      Me, too!

    53. Re:This isn't normal behavior? by Anonymous Coward · · Score: 0

      This is a legit question, and if nobody can answer it, then perhaps the parent poster needs to be moderated down for being incorrect.

    54. Re:This isn't normal behavior? by will3477 · · Score: 1

      Maybe the comment is from a company whom we might not like all their suggestions, but this one is very valid. I'm a student worker for a department at a large univeristy, and I know our firewall it setup so outgoing requests are allowed unless they meet certain criteria (one being port25 not from our mail server), so they idea isn't new, and therefore we don't have a fear of them trying to collect any sort of royalties. So we have nothing to loose from this its a good idea and the more publicity it gets the better. So what's your problem?

    55. Re:This isn't normal behavior? by Trejkaz · · Score: 1

      It's funny though, I don't see port 587 in /etc/services. It can't be very "standard." And how long would it be until the spammers learn about the new port anyway? (As for not allowing us to run servers, yes, our access provider doesn't permit it either, but since ours doesn't permit connection from the outside it's supposedly not considered by them to be a server.)

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    56. Re:This isn't normal behavior? by Anonymous Coward · · Score: 0

      No in fact it won't. My company spent a lot of time and energy investigating XP SP2. We've had pre-release candidates for months now. WF (Windows Firewall as ICF will be called under SP2) will only do inbound port blocking. There is no way to specify outbound traffic or program rules. MS's feeling is that the WF will prevent worm infections (some, but not anything over MS networking whose ports will be open on corporate desktops), but they've apparently never heard of Trojans...

      This is anonymous, since it would be the type of info that might be under an NDA, and I'm not sure if it is or not.

    57. Re:This isn't normal behavior? by Anonymous Coward · · Score: 0

      "Investigating" is one word not two. The fragment "Or maybe a physicist" should be part of the previous sentence.

      Why insist on increased precision in this context, especially in a message forum environment? You clearly arrived at the correct interpretation. What makes you think others would have a problem?

      Employ the same disambiguation skills one would use in oral communication, where both words in question are pronounceable in the same way. Would you ask for clarification in an oral discussion?

    58. Re:This isn't normal behavior? by geminidomino · · Score: 1

      I wish I could act like it was some bit of deep Sendmail wizardry, but the fact is that it is just a combination of dul.dnsbl.sorbs.net (SORBS' Dial-up / Dynamic IP list), reinforced with a local dnsbl from un-listed dynamic IPs that I find myself in received spam, or found by others in NANAE (google groups has some nice posts on the subject.)

      If you want a hand in running your own local-use dnsbl, you can get my email from the whois of the domain linked in my signature. I'll be happy to help.

    59. Re:This isn't normal behavior? by walt-sjc · · Score: 1

      They don't. You are misreading what I wrote. What those proposed standards basically do is say that server X and Y are the legit senders for domain Z. That takes care of the lack of *sending* DNS records. MX records are only for *receiving* servers. That's it.

      How this would theorietically be used is if spammer sends as blah@domainZ from a comcast PC, the receiving server says "you don't present the right crypto credentials / and/or are not server X or Y", and rejects the mail.

      Again, unless DK or SPF is near universally adopted, it won't be effective as spammers will just use blah@domainT which doesn't have SPF / DK records. Adoption is THE key. Anyone claiming DK or SPF will eliminate spam is talking out of their ass. It only says who is legit. It CAN be used as a scoring tool in SpamAssassin however.

    60. Re:This isn't normal behavior? by walt-sjc · · Score: 1

      See RFC 2476. That's standard enough. If you read the spec, servers are required to use SMTP Auth. That solves the spammer issue.

    61. Re:This isn't normal behavior? by Anonymous Coward · · Score: 0
      Sorry, but sometimes bad spelling just distorts the meaning...

      Come on, we are talking about Phill Hallam-Baker here, the original PHB, the guy who was responsible for mis-spelling the 'referer' field.

      As for sitefinder, it might not be a coincidence that it happened a few months after the IETF and PHB had a mighty falling out over the DNSSEC specification. The PHB was arguing that it would be a good idea to change the spec to something that the large registrars were willing to deploy. Some folk thought it a good idea to prove that they were the only ones who had a say that counted.

      Redirecting the core DNS to prove a point is exactly the sort of thing PHB would do. He may have the geeks of the world mad at him, but he would probably say "oderint dum metuant" and point out that sitefinder made the ICANN suit possible.

    62. Re:This isn't normal behavior? by Trejkaz · · Score: 1

      Well, I do require SMTP Auth on the internal mail server I run. If all those servers in the outside world also required authentication, maybe we wouldn't be so worried about having to lock down our own networks to prevent spam. :-/

      --
      Karma: It's all a bunch of tree-huggin' hippy crap!
    63. Re:This isn't normal behavior? by obeythefist · · Score: 1

      Still, ever so slightly more useful than the current XP "firewall" that blocks "some" incoming traffic. Oh well.

      --
      I am government man, come from the government. The government has sent me. -- G.I.R.
    64. Re:This isn't normal behavior? by gi-tux · · Score: 1

      No, I don't actually have any blocked ports right now. However, like others on dynamic IP addresses, I can't send to AOL. Big deal, there are two or three people on AOL to which I ever send email.

      I was simply commenting that if the ISPs got this in, they would start blocking other things as well. The real answer isn't to block ports universally, the real answer is to lose the losers that abuse the system. Get the folks that are the root of the problem.

      --
      I have no sig, does anyone have one to spare?
    65. Re:This isn't normal behavior? by cayenne8 · · Score: 1
      So far, so good, I've not been blocked from sending email to anyone I know. I just made sure and learned how to set up my MX record and all for my site...

      I'm running postfix as my MTA...and I"m as sure as I can be now (always learning) that it is pretty secure, and not an open relay....

      --
      Light travels faster than sound. This is why some people appear bright until you hear them speak.........
    66. Re:This isn't normal behavior? by JPriest · · Score: 1
      "spammers will just use blah@domainT which doesn't have SPF / DK records"

      "Anyone claiming DK or SPF will eliminate spam is talking out of their ass"

      Which was exactly my point, DK and SPF do not prevent direct client to MX mail transfers. even if every domain in the world added the proper records, spammers would just have "an associate" register a domain and "forget" to add said records so that it can be used in the from: header.

      You can make valid mail servers as secure as you'd like, but until a technical solution is put in place, people to simply not use them. Any and all attempts to secure them will just increase the rogue to valid SMTP server ratio.

      This places the administrative responsibility on Joe Users to protect their PC's from getting 0wn3d and being used as mail relays. I don't know about you, but this makes me sleep better at night.

      --
      Saying Java is nice because it works on all OS's is like saying that anal sex is nice because it works on all genders.
  2. Wouldn't software firewalls do this as well... by mobiux · · Score: 1

    since they monitor traffic going in and out of the PC.

    1. Re:Wouldn't software firewalls do this as well... by Mistlefoot · · Score: 3, Insightful

      Absolutely.

      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.

    2. Re:Wouldn't software firewalls do this as well... by MMaestro · · Score: 1

      True, but ultimately the problem comes back to the millions of Joe Averages out there with broadband connections and cheap yet overpowerful computer system any geek will tell you they just plain don't need. There are people who still send out and forward chain letters (not to mention open up suspicious, no-doubt-virus-ridden, e-mails) which already adds to the problem of spam messages. What are the chances of these Joe Averages collectively thinking 'hey, maybe I should stop leaving my computer on 24/7 and ask tech support why my computer always seems to slow down whenever I surf the net.'

    3. Re:Wouldn't software firewalls do this as well... by Nogami_Saeko · · Score: 1

      Part of the problem with software firewalls are that if the user has a problem wherein they let a spambot or other virus into their machine, that program could have the ability to disable a software firewall as well.

      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".

      --
      "Nothing strengthens authority so much as silence." - Charles de Gaulle
    4. Re:Wouldn't software firewalls do this as well... by AndroidCat · · Score: 1
      The problem is isolation. If the malware is running with admin rights, then it can attempt to switch-off/bypass the software firewall on the same machine. Apparently some malware tries to do this now.

      Another problem is that apps on Windows can piggyback on IE's permissions for HTTP connections.

      --
      One line blog. I hear that they're called Twitters now.
    5. Re:Wouldn't software firewalls do this as well... by perlchild · · Score: 2, Interesting

      *trying not to feed the troll*

      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 support calls(as not a single one of them has had the balls(yet) to my knowledge to announce it in public fora(and they are similarly afraid to announce it to their users, despite that it could actually be marketed as a good thing: we protect you from this, so your bills are more likely to stay low)
      Putting it on the other side of the demarc is putting provider policy control on the client's side of the link, which is generally a bad idea.

    6. Re:Wouldn't software firewalls do this as well... by halowolf · · Score: 2, Insightful
      This is a good point, because for Joe Average they maybe able to use their computers, but they certainly do not understand how they work. And to keep a computer running well, you need to understand how they work, or have someone close to them that knows how they work to maintain them. When it comes to firewalls and such, a more advanced computing topic, its hard enough for Joe Average understand why its desirable to have one let alone how to configure one effectivly to protect them on the internet.

      I know there are products like ZoneAlarm and such to try and make it easier for non technical users to use them, but Joe Average people will be baffled by them since they don't understand how networks work and everything that goes with that.

      There is research into making computers self maintainable and repair themselves and such but its a long way away from making the Joe Average safe to use a computer on the internet. Alot more work needs to go into transparent computer adminstration systems that free Joe Average (and their administrators, family computer lackeys etc) from having to deal with computer problems that could be solved or avoided, with what we would consider common sense.

    7. Re:Wouldn't software firewalls do this as well... by Condor7 · · Score: 1


      Another problem is that apps on Windows can piggyback on IE's permissions for HTTP connections.

      That's why I use Mozilla. I use a rules based firewall, and IE has no permissions at all except for access to Windows Update.

      With all the software these days that phones home without telling you, it just seems to make sense for broadband users to have a hardware router/firewall to protect against external threats as well as a software firewall to keep unauthorized communication from getting out.

    8. Re:Wouldn't software firewalls do this as well... by msim · · Score: 1

      By default my isp (iinet.net.au) has blocking of inbound (to the user) ports, from memory 80, 25 13x and a couple of others (as well as possibly some outbound ports, im not exactly sure).

      To configure if you wish to have this port blocking enabled or disabled for yourself you need to go to what they refer to as your "user toolbox" on their website, this has your account details, as well as usage as well as "firewalling", which allows you to let them block most requests on "bad" ports for you, or if you wish to let your setup do it itself.

      Sometimes the quantities of shit out there amazes me, but then again with all these people offering to 3nL@rg3 my P3n!s and so forth, why should i really be suprised.

      --

      Life is like a box of chocolates, you never know when your gonna get food poisoning.
    9. Re:Wouldn't software firewalls do this as well... by Anonymous Coward · · Score: 0

      I wasusing ZoneAlarm, up untill recently.

      I had found for years that it helped. It might be able to bebypasse, hoever, the updates, seem to be able to get around that.

      The only issuee I had was it was crashing against a copy of my virus checker.

      But, it would pop up and ask you as yu ran a program,that it wanted this kind of access.

      It was rated by (gibbs?) security site as the better free software options out there.

      The only thing I dont like is how hard the push for upgrading tothe pro version becomes.

      They seem to be following RealPlayer, and obfuscationg the free dl link, as well, as after you yopuownload it,and start the install it will ask you again. Give me abreak.

    10. Re:Wouldn't software firewalls do this as well... by SlamMan · · Score: 1

      The answer isn't always to create an uncircumventable solution. The answer is to create a good solution, and be able to adapt it when some is able to circumvent it.

      --
      Mod point free since 2001
    11. Re:Wouldn't software firewalls do this as well... by JuggleGeek · · Score: 1
      I know there are products like ZoneAlarm and such to try and make it easier for non technical users to use them, but Joe Average people will be baffled by them since they don't understand how networks work and everything that goes with that.

      Disagree.

      Last christmas, I cleaned up my parents computer, ran spybot, adaware, and that kind of thing. Nothing major found, but lots of small stuff. After I did that, I DL'd ZoneAlarm and installed it. Being a geek, I did this in the middle of the night, so I hadn't explained it to my parents.

      My dad is about the least technical person you can imagine. And I hadn't told him about it. But the next morning, he got up, started to check Email, and ZoneAlarm is promting him about "Do you want to allow this program to access the internet". He figured it out on his own, no problem. He realized that I must have added something to the machine, and correctly configured it to allow his mail program to work.

      When we talked later, I explained that if ZoneAlarm popped up asking about a program he hadn't heard of, especially if he hadn't intentionally added any software that should connect over the net, that he should say no, and why. And I think he got it.

      If my dad can figure out how to use ZoneAlarm, then anyone can.

  3. Comment removed by account_deleted · · Score: 1, Insightful

    Comment removed based on user account deletion

  4. It would just create problems... by flamechocobo · · Score: 0

    Having a firewall required would hinder gaming efforts by making it harder to connect to servers.

  5. Good Idea by Compuser · · Score: 1

    So long as I can edit firewall settings I would
    support mandatory default reverse firewalls for
    any equipment that so much as touches IP.

  6. And who will control what to control? by jrockway · · Score: 3, Insightful

    Ahh, and who will control what defines an attack? Is using Freenet an attack? Bittorrent? Kazaa?

    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.

    --
    My other car is first.
    1. Re:And who will control what to control? by dhakbar · · Score: 5, Insightful

      Force?

      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?

    2. Re:And who will control what to control? by black+mariah · · Score: 0, Troll

      Look, fucking idiot, do you even know how a fucking firewall works? You select which ports you want to allow traffic on, then all others are stopped. IT IS USER CONFIGURABLE YOU FUCKING IMBECILE.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    3. Re:And who will control what to control? by Anonymous Coward · · 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?"

    4. Re:And who will control what to control? by Capt'n+Hector · · Score: 4, Informative

      Put away that tin foil hat. Would you say the same thing about normal firewalls? After all, normal firewalls don't allow traffic from Bittorrent, most online games, etc etc etc without configuration. So.... "Who will control what defines an attack?" The answer is, as always, you.

      --
      Quid festinatio swallonis est aetherfuga inonusti?
      Africus aut Europaeus?
    5. Re:And who will control what to control? by Anonymous Coward · · Score: 1, Interesting

      Go uncap a cable modem. Oh wait in some cases a hard thing to do. Also against your Terms of Service. What is to stop manufactures from hindering the users ability to configure this reverse firewall in a similar manner. What is to stop your provider from doing the same for your and the providers network and other customers protection?

      It comes down to this, if they cannot trust the users computers, why should they trust them to configure a reverse firewall?

      What if you only have one choice of broadband provider?

      Personally I think the best place for activation of such things is at NOC level not user level and on a case by case basis.

    6. Re:And who will control what to control? by bhima · · Score: 4, Funny
      Sorry I can't help myself....

      Can it it be configured to block port 1984?

      --
      Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
    7. Re:And who will control what to control? by Donny+Smith · · Score: 2, Insightful

      > Outbreak of mental illness: Anger problem

      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 useful/informative/worthwile and 80% is indistinguishable from any other forum.

    8. Re:And who will control what to control? by black+mariah · · Score: 1

      Having broadband isn't a right. When you use any network, you are bound by their terms of service wheter you like them or not. Don't like them? Then don't use that ISP. Don't have another broadband provider? Tough shit. Either quit your bitching or stay on dialup. Be sure to tell the ISP why you didn't choose them though. They love to hear about lost business due to their own stupidity.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    9. Re:And who will control what to control? by hoferbr · · Score: 3, Insightful

      IMHO, I think you're missing the point. The article states that the reverse-firewall would block traffic from specific ports that used the computer as, quoting the article, "a group of "zombie" machines hijacked to distribute huge amounts of fraudulent e-mail or launch denial-of-service attacks without being traced directly."
      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.

    10. Re:And who will control what to control? by AuMatar · · Score: 0

      If you're forced to use one to use your ISP, its still being forced. The governnmentt does not need to be involved.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    11. Re:And who will control what to control? by AuMatar · · Score: 2, Informative

      Except they're discussing an external firewall in the cable modem. The ISP would control that. So you'd be stuck with RoadRunner's (Comacast, etc) definition

      --
      I still have more fans than freaks. WTF is wrong with you people?
    12. Re:And who will control what to control? by dj42 · · Score: 1

      Once something becomes a standard, it is much easier to discuss making it law / required.

      --
      We are one consciousness experiencing itself subjectively. Back to you with the weather, Bob!
    13. Re:And who will control what to control? by frovingslosh · · Score: 1

      It's even worse than what you say. Anyone who reports/forwards the spam they receive to another site would be stopped by this technique. So the first effect this would have would be to inflict a blow on those fighting spam.

      --
      I'm an American. I love this country and the freedoms that we used to have.
    14. Re:And who will control what to control? by Anonymous Coward · · Score: 0

      Basically what you're trying to say is that Linux is teh sux0r.

    15. Re:And who will control what to control? by SenseiLeNoir · · Score: 1

      who said this is a LAW?

      Actually i think it is the right thing to set up a reverse firewall as a DEFAULT setting for routers and DSL modems. This wil protect the majority joe sixpack user who are the usual owners of zombie machines.

      Experienced users who are more adept at internet security are more liekly to have the knowledge to disable the reverse firewal, or even change its parameters.

      I know the average slashdot user goes about with the "bah, i dont need this/waste of time" attitude, but the average user is not a slashdot reader.

      And I for one dont want to spend countless hours explaining to my friends why their zombie computers are a menace to the internet, ususally their response is like "so what, its my computer, whats it to you?", and trying to explain the fact taht bandwidth issues and the risk of being cut off by their ISP causes a spontaneous core dump in their brain.

      --
      Have a nice day!
    16. Re:And who will control what to control? by shaitand · · Score: 1

      If every device includes the feature on by default, your average user IS forced. Law isn't the only method of force you know, it's one of many.

      The average user doesn't have the knowhow to turn this off, he is in reality not capable of distinguishing between products that will or won't give the option to turn it off, or even being aware this exists before it causes a problem for him.

      And it's inevitable, the cheaper products the average consumer will be purchasing will NOT allow you to turn it off.

    17. Re:And who will control what to control? by shaitand · · Score: 1

      No this is a seperate hardware device, it's no more configurable than it's interface allows. They are already hardly configurable in routers.

      This actually proposes putting blocking of outgoing ports into the MODEM, which in most cases is provided by the ISP and not user configurable at all.

      In the router, it's likely the consumer affordable (read under $50) model is unlikely to provide the option to turn this off, the vendors will reserve that for more expensive models. Even if the option is there in the web interface, your average user would not be competent to turn it off. And even he was competent to turn it off, he still wouldn't be competent enough to know it existed and therefore to look for a way to turn it off in the first place.

      Please ALWAYS remember, the average user who controls the fashions of the industry (like providing the option to turn things off) is computer ignorant, and usually stupid besides.

    18. Re:And who will control what to control? by shaitand · · Score: 1

      "i'm shure that you could easily open it"

      Their proposing doing this in the modem, NOT in the router. Generally the ISP controls how the router is configured, not the user. My ISP doesn't even allow you to purchase a modem from someone other than them.

      Computer experts? Most linux users use their own system to send email, ignorant and expert alike, since the capability is builtin and configured by default. Further, this is a good thing, taking the load off the ISP's central servers. If all computers were setup this way by default blocking lists would be far superior, allowing grainular blocking of spammers and zombies rather than whole ISP blocks.

    19. Re:And who will control what to control? by shaitand · · Score: 1

      "Experienced users who are more adept at internet security are more liekly to have the knowledge to disable the reverse firewal, or even change its parameters."

      Not in the modem they aren't or at least not without violating their TOS. In the router sure, but the modem is configured and usually owned by the ISP.

      My argument isn't against this at all, in fact I think ALL uncommon outbound ports should be blocked by default, in addition to 25. But NOT by the ISP and NOT in the modem.

      After all, everyone should be sending mail from their own system and not the ISP's mailserver anyway. It distributes the load for starters, and it allows for granular blacklisting rather than blocking entire IP ranges. That is why superior systems like linux distro's include this capability by default.

      It's not like it's presence makes things easier for the spammers. A smtp daemon is a trivial thing (as the spammers have already proven). If the system already has one it doesn't make it much easier for the spammer... in fact it will cost them a great deal of cash and time to remove it recode their exploits to use it instead.

      Although that is all this solution would result in as well, after all the spammers would just use the port of a common service that is needed enough to leave open on your typical firewall but not enough that most users would notice it usurped. The ports for realplayer would be good, or vnc. Especially since these aren't always in use and should cause any problem with the spamamatic relay port already being in use.

    20. Re:And who will control what to control? by c0p0n · · Score: 2, Funny

      Force?
      Say that to Obi Wan.

      --

      Your head a splode
    21. Re:And who will control what to control? by Secrity · · Score: 1

      If the average user can figure out how to configure his own firewall to open port 25, or be capable of distinguishing between products with this capability, how can he be assumed to have the "knowhow" to properly run a computer with a mail server? Consider the figuring out of how to configure or hack their own firewall to allow them to open port 25 to be a sort of proficiency test. If a user doesn't know how to turn off a feature in their own firewall then I don't want him to be willy-nilly connecting to my mail server.

    22. Re:And who will control what to control? by Secrity · · Score: 2, Informative

      Port 1984 is registered by IANA to an actual product named "Big Brother".

      bb 1984/tcp BB
      bb 1984/udp BB

    23. Re:And who will control what to control? by Anonymous Coward · · Score: 0

      Don't forget that normal firewalls block (non-passive) FTP too. Darn that port 20.

    24. Re:And who will control what to control? by OgreChow · · Score: 1

      Just because it's defaulted on doesn't mean you can't turn it, or parts of it, off.

    25. Re:And who will control what to control? by xenocide2 · · Score: 1

      I thought we threw out the inalienable right to free speech the minute we decided that spam (ie criminal speech) was inherantly criminal.

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

    26. Re:And who will control what to control? by Anonymous Coward · · Score: 0

      Yes it does.

      These things can be hardwired in. ISPs can run random checks.

      If it can be turned off by the user, it can be turned off by a spambot virus infecting the user's machine, so the hardware will be made so that it WILL NOT be able to be turned off.

      Whether or not this is a bad thing, is another thing entirely.

    27. Re:And who will control what to control? by shaitand · · Score: 1

      If this only blocked port 25 it would be useless, you can send spam on any port you like, It would have to block all non-standard ports as well.

      Like I said, it's more a matter of there not being an option to turn off in most products. And in the case of modems rather than routers, pretty much never an option since their not end user configurable.

      As for willy nilly connecting to your mailserver, when you set it to allow random connections on the web on a certain port, using a certain protocol. You gave up any claims you had to discriminating on who connects to it. Your public to the web and that is the way it is.

      Personally I believe the outgoing mailserver should be included in the distro, already configured out of the box.

    28. Re:And who will control what to control? by Doctor+Faustus · · Score: 1

      When last I checked, only misrepresenting who's sending the spam was criminal.

    29. Re:And who will control what to control? by Zeinfeld · · Score: 1
      He certainly does think it would be a good idea to require a reverse firewall before connecting to the internet.

      Actually my argument is somewhat longer than CNET would give me words for. The original article was 1500 words.

      I think that every cable modem, router should have a reverse firewall capability and that it should be turned on by default.

      I definitely think it should be possible to turn off rate capping for SMTP etc. If someone wants to run a mailing list from home that is good. One of the original reasons for making the proposal was that I wanted to propose something less drastic than disabling SMTP

      When it comes to sending spoofed source address packets or SYN flooding or DDoSing core DNS I am less sure that it should be possible to turn it off. It might be needed for performance, but I think we could have an honest debate on that one.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
  7. A better idea... by SixDimensionalArray · · Score: 5, Insightful

    Perhaps simply modifying mail protocols (migrating away from SMTP, POP3, IMAP etc.) to more robust and secured ones would be easier than having to create a product just to limit what you can do with your own machine and network connection.

    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?

    1. Re:A better idea... by Donny+Smith · · Score: 1

      >Perhaps simply modifying mail protocols (migrating away from SMTP, POP3, IMAP etc.)

      SQUID proxy + AntiVirus software?

    2. Re:A better idea... by Jerf · · Score: 1
    3. Re:A better idea... by KillerCow · · Score: 3, Insightful

      I have to agree with this. SMTP was designed when all of the machines involved were trusted. That isn't the case anymore. Since a design assumption has been fundamentally broken, it needs to be redesigned.

      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.

    4. Re:A better idea... by Anonymous Coward · · Score: 0

      "Enhanced SMTP"? You mean, like ESMTP? Oh wait...

    5. Re:A better idea... by PetoskeyGuy · · Score: 5, Informative

      Enhanced SMTP better known as ESMTP is not hypothetical. It's out there, it works, mail clients know about it. It's optional and most ISP's I've used don't have strong authentication. They could, but choose not to. Search Google for Ehanced SMTP or you'll find an ESMTP mail server.

      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.

    6. Re:A better idea... by CAIMLAS · · Score: 2, Interesting

      The problem with something like this is that it would likely either be an everyone-or-nobody change to the new system, or we'd have a scenario like the Windows API, where old code and functionality is left intact for legacy purposes (which, in effect, makes the new changes irrelevant, as the old exploitation methods are still viable).

      Not saying I disagree, just playing devil's advocate.

      --
      ~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
    7. Re:A better idea... by jamesh · · Score: 1

      some other things would happen in about a fortnight too.

    8. Re:A better idea... by Vitus+Wagner · · Score: 1

      Use good old UUCP. It requires authentication both sending and recieving mail, allows to download mail for entire family though single connection, and
      knows how to resume download after connection fails.

    9. Re:A better idea... by yason · · Score: 1

      Enhanced SMTP better known as ESMTP is not hypothetical. It's out there, it works, mail clients know about it. It's optional and most ISP's I've used don't have strong authentication.

      How about a PKI authenticated mail protocol that only allows the message sent to one recipient per each successful authentication? This would

      • force a spammer to do N million bignum computations (e.g. a simple RSA challenge) per each N million spam sent;
      • form a network of mail servers that support PK authentication which could be used to:
        1. reject mail from unknown servers;
        2. support for undeniable and unforgeable tracing of return-paths (in case someone sent spam);
        3. support an automatically propagating revocation scheme to block out servers that have gone "bad".

      These have been speculated before, but they'd nail primarily at the two worst problems of email: capability to handle a large volume (of spam) and the lack of any "trust" network.

    10. Re:A better idea... by geminidomino · · Score: 0

      Your post advocates a
      (*) technical
      ( ) legislative
      ( ) market-based
      ( ) vigilante

      approach to fighting spam. Your idea will not work. Here is why it won't work. (One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)

      ( ) Spammers can easily use it to harvest email addresses
      (*) Mailing lists and other legitimate email uses would be affected
      ( ) No one will be able to find the guy or collect the money
      ( ) It is defenseless against brute force attacks
      (*) It will stop spam for two weeks and then we'll be stuck with it
      (*) Users of email will not put up with it
      (*) Microsoft will not put up with it
      ( ) The police will not put up with it
      ( ) Requires too much cooperation from spammers
      (*) Requires immediate total cooperation from everybody at once
      ( ) Many email users cannot afford to lose business or alienate potential employers
      ( ) Spammers don't care about invalid addresses in their lists
      ( ) Anyone could anonymously destroy anyone else's career or business

      Specifically, your plan fails to account for

      ( ) Laws expressly prohibiting it
      (*) Lack of centrally controlling authority for email
      ( ) Open relays in foreign countries
      ( ) Ease of searching tiny alphanumeric address space of all email addresses
      (*) Asshats
      ( ) Jurisdictional problems
      ( ) Unpopularity of weird new taxes
      ( ) Public reluctance to accept weird new forms of money
      (*) Huge existing software investment in SMTP
      (*) Susceptibility of protocols other than SMTP to attack
      (*) Willingness of users to install OS patches received by email
      (*) Armies of worm riddled broadband-connected Windows boxes
      ( ) Eternal arms race involved in all filtering approaches
      ( ) Extreme profitability of spam
      ( ) Joe jobs and/or identity theft
      ( ) Technically illiterate politicians
      (*) Extreme stupidity on the part of people who do business with spammers
      (*) Extreme stupidity on the part of people who do business with Microsoft
      (*) Extreme stupidity on the part of people who do business with Yahoo
      ( ) Dishonesty on the part of spammers themselves
      ( ) Bandwidth costs that are unaffected by client filtering
      (*) Outlook

      and the following philosophical objections may also apply:

      (*) Ideas similar to yours are easy to come up with, yet none have ever been shown practical
      ( ) Any scheme based on opt-out is unacceptable
      ( ) SMTP headers should not be the subject of legislation
      ( ) Blacklists suck
      ( ) Whitelists suck
      ( ) We should be able to talk about Viagra without being censored
      ( ) Countermeasures should not involve wire fraud or credit card fraud
      ( ) Countermeasures should not involve sabotage of public networks
      (*) Countermeasures must work if phased in gradually
      ( ) Sending email should be free
      ( ) Why should we have to trust you and your servers?
      ( ) Incompatiblity with open source or open source licenses
      ( ) Feel-good measures do nothing to solve the problem
      ( ) Temporary/one-time email addresses are cumbersome
      ( ) I don't want the government reading my email
      ( ) Killing them that way is not slow and painful enough

      Furthermore, this is what I think about you:

      (*) Sorry dude, but I don't think it would work.
      ( ) This is a stupid idea, and you're a stupid company for suggesting it.
      ( ) Nice try, assh0le! I'm going to find out where you live and burn your house down!

    11. Re:A better idea... by edunbar93 · · Score: 1

      It's optional and most ISP's I've used don't have strong authentication. They could, but choose not to.

      We don't for a very good reason: our users are stupid. They choose stupid passwords, which increases the security risk of authenticated SMTP over plain smtp. Spammers can and do try to access athenticated SMTP servers using common passwords, and it works. One user with the login joe and the password 'password' essentially makes you into an open relay. And I'll be damned if forcing them to change their settings isn't a 3 month long nightmare, followed by another 8 months of increasingly mind-boggling stupidity as the stragglers clue in to the fact that their mail doesn't work. Two weeks, my ass.

      --
      "No problem. I have the capacity to do infinite work so long as you don't mind that my quality approaches zero."-Dilbert
    12. Re:A better idea... by Penguin2212 · · Score: 1

      Howabout Exhange, oh wait...

    13. Re:A better idea... by parksie · · Score: 1

      What about mailing list servers?

    14. Re:A better idea... by Fishstick · · Score: 1

      Search Google for Ehanced SMTP

      Google:

      Did you mean: Enhanced SMTP ?

      --

      There is much cruelty in the universe, John.
      Yeah, we seem to have the tour map.

    15. Re:A better idea... by Anonymous Coward · · Score: 0
      Dude,

      You sound like an idiot. Even though your post is great because it informs folks of ESMTP, you really discredit yourself by using 'your' instead of 'you're'.

      It seems your proposing the same argument the article does

      Should be: It seems you are proposing the same argument the article does.

      They are suggesting a hardware fix, your suggesting software.

      Should be: They are suggesting a hardware fix, you are suggesting software.

    16. Re:A better idea... by Jahf · · Score: 4, Insightful

      That's your fault for not implementing a checking algorithm when the users are changing their passwords.

      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.

      --
      It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
    17. Re:A better idea... by ladyeyes · · Score: 1
      Ok, in theory going to something other than SMTP is a good idea. Its the reality and practicality of it that hangs everything up.

      No one with the authority to say, "We're all going to use..." can agree on which new thing to use. The battles on this are currently raging, but its not finished yet. Beyond that, there is very little hard research on the robustness of the different alternatives. For example, exactly how difficult is it to "break" these new methods?

      Add to this debate about what to use instead of SMTP the general lack of knowledge, or caring, on the part of the average home or small business user, interoperability issues with the different methods being debated, any real-world cost of resources to distribute/set-up/operate/train people on new things, international boundaries/jurisdiction issues ... You get a very difficult mix of technological, political, and social science issues to "use something other than SMTP."

    18. Re:A better idea... by drinkypoo · · Score: 1
      A firewall is not hardware, it is a role. The role can be filled by a dedicated firewall appliance, a server with firewall software, or software on your own PC.

      I have Symantec Antivirus 9 Corporate and it has a transparent email proxy, a firewall of sorts, which scans both incoming and outgoing messages for virii and which can shitcan the messages going in either direction. In its current form it won't stop me from sending out spam (although being firewalled, virus scanned, immunized, and teatimer'd has so far stopped me from contracting any malware, ever) but it will stop me from sending out known worms.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    19. Re:A better idea... by drinkypoo · · Score: 1

      But TCP is broken! Do we replace TCP, or fix it? SMTP is broken, do we replace it, or fix it? The good news is that SMTP was clearly designed to be extensible, it consists of commands and response codes and can be extended in basically any way you like. So why throw away what is a useful tool?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    20. Re:A better idea... by Fritz+Benwalla · · Score: 1

      Sorry, this by all rights should be moderated "off topic" but I'd like to toss in what I hope is a thoughtful reply to your sig. I'd like to suggest that it's actually better to moderate *and* post thoughtful replies when you have them, because they serve two separate purposes.

      Thoughtful replies add to the debate, but the moderation system helps other readers priorities what is an overwhelming amount of information. I don't equate the moderation system as a lazy-person's reply system, just a way (if you choose to run with the crowd) of getting to the comments that have already intrigued other people.

      Cya!

      --

      Believe me, I'm as surprised by my comment as you are.
    21. Re:A better idea... by Doctor+Faustus · · Score: 1

      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.

      So, in response, your users now write down their passwords because they can't remember them. That's not an improvement.

    22. Re:A better idea... by Scooby+Snacks · · Score: 1

      How is a remote spammer going to "brute-force" a scrap of paper from over the Internet?

      --

      --
      Runnin' around, robbin' banks all whacked on the Scooby Snacks...
    23. Re:A better idea... by Doctor+Faustus · · Score: 1

      What about someone wandering through the office?

    24. Re:A better idea... by kaustik · · Score: 1

      Someone wandering through the office likely has their own password, anyway. Also, anyone wandering through the office with the know-how to cause damage in this regard would be a member of the IT department and could wreck havoc in a much more imaginative way.

    25. Re:A better idea... by Just+Some+Guy · · Score: 1
      So, in response, your users now write down their passwords because they can't remember them. That's not an improvement.

      Yes it is, as long as the place they write them down is the "Password:" field of their mail client. Why would anyone care if their email password is a pain to type? How often do you ever actually enter it?

      --
      Dewey, what part of this looks like authorities should be involved?
    26. Re:A better idea... by Jahf · · Score: 1

      Agreed, but since you can't moderate -and- post on the same thread, my feeling is that I would rather see what you think than see a moderation and have to guess at it. If you have nothing in mind when moderating, go for it, I'm just expressing my desire to have a thoughtful conversation with no mod up (or down :) than to see a score:5 (or score:-1 :) that goes nowhere.

      And definitely off-topic ... I've got a bit in my journal on my .sig ...

      --
      It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
    27. Re:A better idea... by minas-beede · · Score: 1

      "Since a design assumption has been fundamentally broken, it needs to be redesigned."

      First of all you need to think about trust a little more - who can trust whom?

      I'll bet you've never thought about it but the spammers can trust the rest of us with close to 100% accuracy. Does that help? Do we really want to be that reliable for the spammers? Spammers do things that decent users don't do. If you set up a system to deceive just those who do the indecent things then you injure the spammers without touching anyone else. All those probes for vulnerability - those are opportunities to strike back. If it's a probe by a spammer you should strongly wnat to strike back: they're scum, they're dirtying the internet, they're the biggest group of abusers (and even biger, if you measure the economic harm.)

      One of the worst ways they can trust us is that if a system looks like it's insecure it is insecure. we're so proud of our security we advertise it. That's wrong. An alternative to changing the design of SMTP is to protect it. (Note, too, that spammers abuse other than SMTP ports to send spam.) If the spammers can't figure out which systems are insecure and which are not they sort of have to give up, don't they?

      If it isn't clear what I am advocating is that secure systmes look insecure to the spammers. Best would be systems set up specifically for that purpose. Spammers do bulk abuse and can't afford to spend much time checking to see whether or not the systems that look like they can be abused really can be abused. Even if the main effect is to force spammers to spend more time checking that is a giant step forward in the fight against spam. Note, too, that if you are set up to detect spammer abuse tests you have information on them from the test alone - there is no way to do a stealth test. At best they can test through other abused systems, but get any useful number of trap systems set up and the spammers face a greater risk from doing multi-hop abuse. It's another way in which they'll lose.

      Yes, by golly, you can think of things the spammers could do to counter such an approach. A few people use such an approach, a few spammers do use crude countermeasures. Having to continually change hasn't bothered the filter advocates. The blocklist advocates have also changed what they do with time (probably not enough, not nearly as fast as spammers change tactics.) Having to refine the fake abusable systems from time to time is a cost of taking that approach. The cost is far less than the benefit. Do it.

      If you manage a block of IP addresses one of your goals should be that every spammer in the world know that attempting to abuse a system under your control will lead to consequences he doesn't like. (Best would be that the consequences are so severe he doesn't even have the option of doing more abuse: he's jailed.) That's not a change in the SMTP protocol, that's a change in behavior - YOUR behavior. The old security model (the one, unfortunately, that is still pushed) is one that protects (as much as it does) individual systems. Take a look, darn it: spam is an abuse that targets multiple systems - the spam recipient's email server is just the last in the chain. The single-system security model works to protect single systems but is failing to stop spam. Spam is not only a single-system abuse issue. Quit pretending it is, quit putting all the effort into single-system-abuse based approaches. The spammers laugh at how easy it is to succeed because of that unfortunate bias toward the single-system security model. Turn that laugh into a howl of pain - and make them howl louder with time.

      Check www.proxypot.org for some ideas. Traffic analysis (which is ideal for ISPs) can be used with devastating effect, too.

      Chase them down, destroy their anonymity (which is 1% their cleverness, 99% their good fortune of having the abuse ignored.)

      Win. Enjoy the win. It's easy.

    28. Re:A better idea... by Anonymous Coward · · Score: 0

      For some inexplicably popular mail clients, every time your mail server is unreachable for whatever reason... In most cases, written-down is fine though, and much preferable to being stored on disk.

  8. Off by default by Kris_J · · Score: 4, Interesting
    Where my mother works, they're all allowed to have VPN access (I know this because I'm getting ADSL so she won't be dialling in directly anymore), but it's not on by default, you have to make a request to turn it on.

    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.

    1. Re:Off by default by ottothecow · · Score: 4, Interesting
      Yes

      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).

      --
      Bottles.
    2. Re:Off by default by hellfire · · Score: 1

      It would also have an impact on my own personal email system. I have comcast as my ISP now, but I don't use comcast's email. I have a website, and through that I accept email. Because I have my own domain, I don't have to worry about changing my email ever again and everyone can get in touch with me. Fortunately my site comes with a decent spam blocker as well.

      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 integrates with my Treo 270. Everything works nice and neat and I get loads of features and things just work. It would take to look to go into major detail but because of my setup, which has lots of conveniences for me and its what I want, blocking access to my website's email from my connection would royally screw things up.

      And I don't host spam lists or anything like that. I should be allowed to access any email server I want thank you. It's the spam servers which have to be localized and taken out.

      --

      "All great wisdom is contained in .signature files"

    3. Re:Off by default by techno-vampire · · Score: 0

      You don't need port 25 to check your email; POP3 is 110. My ISP blocks all outgoing port 25 connections but doesn't insist (unlike some idiotic ISP's) that the return address be at their domain. I have an alternate address at the domain of a private club I'm a member of. I can check that email just fine, but when I send mail on that address it goes through my ISP's SMTP server. Unless you're either a spammer, a control freak or a hobbyist that really wants to learn how to run a mail server there's no real reason to run your own.

      --
      Good, inexpensive web hosting
    4. Re:Off by default by benna · · Score: 2, Insightful

      I would be seriously pissed off if I could only use their SMTP server. Spam may be a problem but I'd rather have spam and an internet connection that I chose the way I use then to lose that freedom and spam. But then hey I'm just some wacko that values freedom over safty from terrorism.

      --
      "It is not how things are in the world that is mystical, but that it exists." -Ludwig Wittgenstein
    5. Re:Off by default by Unordained · · Score: 1

      I think the idea was that ISPs should not refuse to open ports to you unless they know for sure something fishy is going on (at which point their terms of service will likely be getting you kicked off.) The idea is to have it off by default to make normal home users less useful to spammers releasing spam-relay-virii. You should (as I read the grandparent's description) have the option of running your own home email server if you like. It'd be something to ask for when you get the service set up, or something you'd get a note about before anything changed. "Just call us if you need this" -- nothing special. Sure, there are ISPs that aren't that nice, and would use this as an excuse to do worse things, without recourse. But for the "nice" ISPs out there, this would just be a "if you know to ask, you can have it" thing, that could prevent a lot of spam and make it less useful to have virii floating around. (Make sure it's listed somewhere obvious, with an easy way to get it enabled.)

      The same would be true, I would imagine, of other ports the ISP thinks are often "on" uselessly, leaving security holes open. They shouldn't even ask for a reason -- it should be enough to get a request from a customer.

    6. Re:Off by default by AuMatar · · Score: 1

      No. Not just no, hell fucking no. I'm buying internet access from them, not port 80 web access. I should be able to send whatever data I want out at any time. If I'm reaking a law, then the government should come and deal with it. Otherwise the ISP is a carrier. I should definitely NOT have to call up my ISP and get permission to use a specific port. I should be able to just start the server and go.

      --
      I still have more fans than freaks. WTF is wrong with you people?
    7. Re:Off by default by gerardrj · · Score: 4, Insightful

      There are several very good reasons to use your own email server instead of your ISPs:

      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.

      --
      Article X: The powers not delegated... by the Constitution...are reserved...to the people
    8. Re:Off by default by Ravadill · · Score: 1

      My ISP blocks SMTP (also netbui and any http incoming) by default, but allows users to remove the port blocks by logging into their online account admin page and clicking unblock.

      I think this is the best of both worlds, as it makes it harder for the average user to get infected and send out spam (or pickup nimda et al by accidentally enabling iis) but others who want to use these ports can easily enable them.

    9. Re:Off by default by AuMatar · · Score: 1

      A few good reasons:

      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

      --
      I still have more fans than freaks. WTF is wrong with you people?
    10. Re:Off by default by Ryan+Amos · · Score: 3, Interesting

      The days of the ISP as a "carrier" are long gone. They were over pretty much as soon as broadband hit the market. ISPs these days handle such massive amounts of bandwidth with such ignorant users that they have somewhat of a responsibility to the rest of the internet (not to mention their bottom line) to make sure that bandwidth isn't being used for nefarious purposes by hackers or viruses which have taken over the computers of these ignorant users. 99% of users don't need to and will never run a mail server, DNS server, whatever from their cable modem. All leaving these ports open does is allow the spambots and botnets to spread unabated.

      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.

    11. Re:Off by default by mdfst13 · · Score: 1

      "but when I send mail on that address it goes through my ISP's SMTP server."

      That's the wrong way to do it. You should be using SMTP Auth over port 587 to connect to a mail server for your actual domain instead. SPF will make your life much more difficult unless you make this switch.

      The only reason to turn on port 25 is to run your own mail exchanger. Unfortunately, most ISPs don't have the ability to turn ports on or off on a per IP (or better: per MAC) basis. They block too far up. Thus, "off by default" is not possible for most ISPs; they can either turn off or on for *everyone*. Thus the author's suggestion to put blocking at the cable modem level, so it will be per connection.

    12. Re:Off by default by techno-vampire · · Score: 1
      As I pointed out in my earlier post, a good ISP will let you use whatever domain you want and address you want on your mail. Unless you have a control-freak ISP, your point one is no reason at all, as you should already be able to do that.

      If you really think your ISP is reading your mail, you shouldn't be using it.

      There's nothing to stop you from filtering out spam as you download it, to have your machine notify you or to have it forward it, so points three and five are moot.

      About the only point that might, under some circumstances be valid is the last one. However, I'd certainly not try running my own server, not only for security reasons but because I see no reason to put that much work into duplicating what I'm already paying for.

      --
      Good, inexpensive web hosting
    13. Re:Off by default by sockonafish · · Score: 1

      The one con that invalidates all those pros:

      Lots of mail servers bounce mail that comes from a dynamic IP. I guess you could buy a static IP for $10 more a month or whatever it is most places charge, or you could just buy SMTP service from dyndns.org for $12 a year. (Not an employee, just a satisfied customer) I was running Postfix on my iBook for a short time and found it most awesome to have such control until people started telling me that they weren't getting my messages.

    14. Re:Off by default by techno-vampire · · Score: 1

      If you want to log all your email, just keep copies. As far as the rest, I'm sure you can invent as many specious excuses as you want. My best advice if you don't like your ISP's servers is find one that works better.

      --
      Good, inexpensive web hosting
    15. Re:Off by default by AdamInParadise · · Score: 1

      Please define "your own email server". If you are talking about getting a domain from a provider then using the POP3 and SMTP server of this provider instead of the POP3 and SMTP server of your ISP, then it is a great idea. If you are talking about hosting and managing your own server at your place, using your alway-on connection, then, no, I don't think that this is a good idea, unless you're really into tinkering with servers.

      Decent providers will let you do 1 to 6 with the cheapest plan. But you have to get a decent one: I agree most free or cheap providers much more than your ISP. I pay about 60$ a year for mine, and it is great value. Hosting your server may gave you a nice egoboo and some bragging rights, but actually it's a PITA. I'd rather let someone else deal with spams, viruses, security updates and everything else, and go on with my life. And I'm pretty sure that their server will have better uptime than mine.

      Regards,
      AIH

      --
      Nobox: Only simple products.
    16. Re:Off by default by techno-vampire · · Score: 1

      If my club's hosting company used SMTP AUTH, I'd send it out through them. As they don't, I send it the only way I can. I did tech support for that ISP for a long time, and many of their customers send mail from home using corporate return addresses. It all goes out through the ISP's servers and unless you read the headers you'll never know the difference. And, even if you know how to, why would you bother if the message itself is legit?

      --
      Good, inexpensive web hosting
    17. Re:Off by default by Kris_J · · Score: 1

      Hey cool, that's going to be my ISP soon too. As soon as they get my ADSL on.

    18. Re:Off by default by Marlor · · Score: 2, Insightful

      There are several very good reasons to use your own email server instead of your ISPs:

      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 DynDNS.

      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.

      If you're really worried, you will use PGP or GPG. If your ISP is intrusive enough to read your email, then they can just as easily read it as it comes into your private mailserver.

      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.

      The aforementioned email forwarding services do this too.

      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.

      Not only is it bad netiquette to send massive attachments, but most servers will block them at the other end. I see attachments over 5MB as tantamount to DOS attacks. A company I worked for used to have a policy of unlimited sized attachments, until lusers started attaching 500MB files.

      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.

      Have you heard of fetchmail?

      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.

      I'd quickly find a new ISP if this was the case. I know that my ISP's mail server certainly has higher availability than any PC in my house - although that is mainly because blackouts are more frequent here than in most places, and because ISDN is the best connection available here. However, if your ISP has less than 99% availability on their mailservers, there is something very wrong.

    19. Re:Off by default by JWSmythe · · Score: 2, Interesting
      3)Your ISPs servers suck


      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 into the account later, it's usually full of spam. That's funny, since I didn't give out the address. Oh, some mininum wage tech with too much access sold the user list again. That happens a little too often.

      I'm a bit more skilled than average Joe-user, but hey, there are plenty more like me. I read from my company mail server using IMAP, and send from my local machine using sendmail. Big deal. So 10 to 20 emails per day go out from my IP. At least right now I'm in control of my connectivity.

      I've used providers who block all kinds of things, usually arbitrarly. RoadRunner got rather pissed off at me once because I ran a caching DNS server at my house. They didn't quite grasp the concept that 30 seconds to resolve a hostname was unacceptable, knowing it should take a fraction of a second. They cut my service without notice for it, and it took plenty of screaming to get it turned back on.

      Myself, when I set up a firewall, I already block everything coming in and going out, and then allow on an as-needed basis. I feel that's the way it should be done.

      --
      Serious? Seriousness is well above my pay grade.
    20. Re:Off by default by Phil+Karn · · Score: 5, Insightful
      If your ISP is intrusive enough to read your email, then they can just as easily read it as it comes into your private mailserver.

      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.

      I'd quickly find a new ISP if this was the case.

      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.

      Not only is it bad netiquette to send massive attachments, but most servers will block them at the other end.

      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.

      Have you heard of fetchmail?

      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.

    21. Re:Off by default by Errtu76 · · Score: 1

      It's just too bad that if you're using your own mailserver, you might already be in a blacklisted (spam) ip block. Happened to me a couple of times now and my only option was to use my ISP's mailserver.

    22. Re:Off by default by AVee · · Score: 1

      ISP's should block outgoing traffic on port 25. This will stop massmailing zombies. Incomming traffic on port 25 is not a spam problem.

      With that configuration you can perfectly run your own mailserver. It will recieve incomming mail just fine and can simply be configured to send all outgoing mail via the ISP's SMTP server. I guess that makes everybody happy.

      (And don't whine about the the ISP's SMTP being unreliable, you pay for using this server so sue them or switch to an ISP that does deliver...)

    23. Re:Off by default by kieran · · Score: 1

      Mod parent down!

      None of those points, save possibly 6, are relevant to an outgoing SMTP server. Use your own POP3/IMAP server for incoming mail, and send out via your ISP's SMTP server.

    24. Re:Off by default by Dever · · Score: 1
      very good point. i personally have a myriad of options between adelphia high speed internet and thousands of dial-up providers.

      well, perhaps i'm being a bit bitchy. i could just set up a long distance custom wifi link from a friends house a mile down that has dsl.

      oh...yeah, i mean there's satellite too...

      and the Postal Service.

      --
      - I'd prefer not to.
    25. Re:Off by default by bdijkstra · · Score: 1

      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. But they can! They own the gateways, remember? They can see all your traffic. 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. You don't need a server for this. A client can also see incoming mail. 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. Get a proper ISP.

    26. Re:Off by default by JonnyCalcutta · · Score: 1

      Here's the best reason of all - because we're geeks and we can.
      I just don't get all these replies basically implying that nobody should be allowed to run their own outgoing smtp server - the internet was built on the fact that anybody could run a server, host a website or send an email. Now its suggested that what? Only private companies can run servers? Only ISPs? Only if we have certain types of IP addresses? Only with a letter from our Mums?

    27. Re:Off by default by Anonymous Coward · · Score: 0

      Actually, traffic analysis still largely works on encrypted traffic. I can tell a LOT about you by knowing who is sending how-much email to/from you when. The 'why' part usually becomes obvious after a while. Still an interesting post, though.
      Me

    28. Re:Off by default by egburr · · Score: 3, Insightful
      My best advice if you don't like your ISP's servers is find one that works better.

      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.

      --

      Edward Burr
      Having a smoking section in a restaurant is like having a peeing section in a swimming pool.
    29. Re:Off by default by YaRness · · Score: 1

      funny, i've been using a domain and host different than my isp for years. which invalidates 1-5 of your rant (except for #2 which, as someone has pointed out, is pointless because your isp can sniff all your traffic anyway).

      as for #6? clearly you just need a new isp.

      how that got modded up to 5 is beyond me.

    30. Re:Off by default by Anonymous Coward · · Score: 0

      There is no reason network or otherwise that we as a business shouldn't be running our own mailserver from our static DSL address block. Your points about spam filtering are irrelevant, we reject or discard spam at SMTP time. On the security point, it's our call and that is SMTP AUTH and IMAPS for our unlimited number of user accounts accross unlimited domains, try getting that from your ISP (I don't mean wildcards)!

      There is no reason we should be forced to queue mail through our ISP's latent mail spools, nor have anti-virus scanning forced down our throats (we are a *nix shop and reject windows attachments).

      Finally, if we weren't running mail/web servers, we wouldn't need fast connection in the first place!

    31. Re:Off by default by julesh · · Score: 1

      Who said I'm only allowed to use port 25 for sending e-mails?

      This annoys me, actually -- one of the ISPs I've used in the past has an automatic proxy server that grabs every connection on port 25 and sends it to their own outgoing mail server. Damn it! I use SMTP for doing VRFY, alias expansions and other operations that can't be done through a relay server. I have P2P software that uses randomly chosen ports, 1/64K of which will be port 25. Stop assuming everyone uses the internet in the same way as the mindless zombies.

    32. Re:Off by default by Anonymous Coward · · Score: 0

      Nothing you say is relevant to anything unless you address the points raised, you can't just say his points are not relevant. I agree with all of them apart from 5 and I'm speaking from experience. Who the fuck are you to be making assumptions on somebody else's circumstances anyway?

    33. Re:Off by default by Anonymous Coward · · Score: 0

      That's what we have ports over 1024 for.

    34. Re:Off by default by dpilot · · Score: 1

      By policy, Adelphia isn't just 'off by default', it's just plain 'off'. Their more recent Terms Of Service specify that customers may operate 'no servers of any kind.' I don't know how much of this they actually enforce, though I've heard they block incoming ports 25 and 80. Personally I'm surprised they don't just block all incoming SYN packets. These folks are least-common-denominator types, why should they spend any money to accomodate anything else? Don't forget the roots of cable Internet providers - cable TV. I suspect that they think of the Internet as 'millions of web channels' plus email. From what I understand, even Adelphia's 'business plan' has the same TOS, they just add some service guarantees, (their) server-side stuff, etc.

      So I'll take your simple 'off by default' proposal, and tell you exactly what would be implemented - OFF!

      As for the 'get another ISP' argument, when cable is your only broadband option, you can't do much else but check DSLReports monthly to see if it's available yet (no, not yet) in your neighborhood. I'd take the bandwidth drop in a heartbeat, to get true Internet service.

      --
      The living have better things to do than to continue hating the dead.
    35. Re:Off by default by Anonymous Coward · · Score: 0

      #2 Which as somone else pointed out would require them to act as man in the middle for encrypted traffic. 1-5 depends on circumstance, we have 7 seperate domains and do our own internal mail routing so whilst it may work for YOU, that doesn't mean it will work for everyone. Laugh it up!

    36. Re:Off by default by Anonymous Coward · · Score: 0

      My best advice to you is to stop dictating to others that they cease perfectly legitimate usage of their network connections or expend time looking for a new provider that will do what thay ask. Thanks.

    37. Re:Off by default by Anonymous Coward · · Score: 0

      Many (most?) MTAs now support the STARTTLS SMTP command.

      No, actually, sadly they don't. I mean, it makes sense that they should.. but your wrong, they just aren't for the most part. *Most* MTAs are small companies / ISPs, etc still.. Maybe some larger ISPs offer this, but it certainly isn't common / the norm.

    38. Re:Off by default by julesh · · Score: 1

      99% of users don't need to and will never run a mail server, DNS server, whatever from their cable modem. All leaving these ports open does is allow the spambots and botnets to spread unabated.

      Hang on, you haven't read the article have you?

      It's not talking about preventing users from running servers. It's talking about preventing users from using services in particular ways that look like they might be an attack of some kind.

      Send too many e-mails, have your e-mail access shut down. Make too many web requests and they'll assume you have something like code red. Use port 6346 and they'll assume you're running gnutella and shut that down too. OK, I'm joking about that last one, but it's the obvious next step.

    39. Re:Off by default by Anonymous Coward · · Score: 0
      Damn it! I use SMTP for doing VRFY, alias expansions and other operations that can't be done through a relay server.

      VRFY and alias expansion still work? It's been years since I've seen a mail server that accepts VRFY. Many still tell me in a snotty tone to use finger. As if anyone runs fingerd anymore.

    40. Re:Off by default by Anonymous Coward · · Score: 0
      The article is about blocking out going connections.
      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.
      Wouldn't the above be about incoming connections. Unless your experience is with trying to block spam you send yourself.
    41. Re:Off by default by Ancil · · Score: 1

      I run my own email server. I get all of these benefits. Yet I still route outgoing mail through Comcast's mail servers.

      It costs me nothing in terms of functionality. And, because no ISP in their right mind would blackhole comcast.net (4 million+ subscribers), I don't have to worry about my mail not getting through.

    42. Re:Off by default by ratboy666 · · Score: 1

      Not true

      I run my own mail server (vanity addresses). Up until very recently my ISP mail server allowed me to use their SMTP server to relay -- and forced me to authenticate. Which worked well.

      Recently, my ISP switched to "yahoo" for mail services. yahoo uses qmail, and is configured to not allow any relaying at all. Which means I am back to directly sending email.

      Oh well, back to the drawing board (I don't want my email to ORIGINATE from yahoo.com, I just want them to relay my email properly).

      ratboy

      --
      Just another "Cubible(sic) Joe" 2 17 3061
    43. Re:Off by default by qtothemax · · Score: 1

      This is exactly what I was thinking of. It would even be effective if it was possible to log into the modem and turn the reverse firewall off. Anyone who owns a zombie PC would have no idea how to do that, and therefore never would. People who actually know what they are doing would never have a spam zombie, and it would be a snap for them to disable the firewall.

    44. Re:Off by default by CodeMunch · · Score: 1
      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

      Your ISP can read your e-mail as it travels through their network to your mail server.

    45. Re:Off by default by Idarubicin · · Score: 1
      I would be seriously pissed off if I could only use their SMTP server.

      Read the grandparent post again. It suggested that by default port 25 should be disabled, but that it could be restored on request from the user.

      Quite frankly, this is sensible. Yes, it will inconvenience (very slightly) those among us who wish to run our own mail servers. But admit it--we're a very small fraction of most ISPs' user base.

      Further, it's a small amount of hassle I'm willing to put up with, given the time and bandwidth it will save me in the future when I have less zombie-sent spam to deal with. If my ISP decided to charge me more money to enable port 25--then there would be a problem.

      The bit about freedom, safety, and terrorism is decidedly uncalled for. You're just trying to push the usual Slashdot hot buttons--and unfortunately, it seems to have worked in this case.

      --
      ~Idarubicin
    46. Re:Off by default by techno-vampire · · Score: 1
      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.

      Try millions of users. That means that an ISP has multiple redundant mail servers, using robust hardware and software with people monitering them 24/7. what do you do if the mailserver falls over when you're at work?

      --
      Good, inexpensive web hosting
    47. Re:Off by default by Anonymous Coward · · Score: 0
      It costs me nothing in terms of functionality.
      It does, you can't be sure a message has reached the recieving MX until you recieve a delivery failure report or a response. Neither is relaying through your ISP's mail server ever going to be as fast as sending direct. If these don't matter TO YOU, that's fine, but WE WOULD lose functionality.
      no ISP in their right mind would blackhole comcast.net
      But I have in the past! The only mail originating from comcast or pacbell hitting our servers is viruses and spam.
    48. Re:Off by default by pclminion · · Score: 1
      Let me start by saying most of your points are good and valid. However, I flew off the handle here:

      Not only is it bad netiquette to send massive attachments...

      Oh, fuck off with this, will you? I'll send whatever the hell I damn well please to my friends. If none of us mind large attachments, who the hell are you to tell us what we can and cannot send to each other?

      The concept of "netiquette" is dead and gone, along with the dream of a "commerce-free" Internet. Usenet is the last bastion of the old ways. Get over it already. We're not an exclusive little club anymore. We don't have a set of commandments written in reverse pig latin on stone tablets.

    49. Re:Off by default by JuggleGeek · · Score: 1
      no ISP in their right mind would blackhole comcast.net

      I dunno about that. Comcast has been hosting many of the spamvertised sites that I've checked lately, and they don't seem to do anything about spam reports.

    50. Re:Off by default by YaRness · · Score: 1

      what you described isn't home user activity, that's business activity.

      so get a business-grade account with your isp.

      sucks, but that's the nature of things.

    51. Re:Off by default by Ancil · · Score: 1

      you can't be sure a message has reached the recieving MX until you recieve a delivery failure report or a response
      Which is generally true anyway. Almost no modern mail servers will bounce an email during the SMTP session, since that makes it much easier to probe for valid addresses. Heck, many SMTP servers are configured not to even send failure notices.
      Neither is relaying through your ISP's mail server ever going to be as fast as sending direct
      My goodness. Emails will be in transit for an extra 2 or 3 seconds. By all means, please provide an example for which that represents a loss of functionality.

      Of course, if you're sending to a place like hotmail.com or yahoo.com, etc, then your emails will arrive much much faster. That's because emails sent directly from your private IP address from Comcast's block will be accepted, and then silently disrcarded.

      But I have in the past!
      You're not an ISP, Mr. Anonymous Coward. In any case, if you think you'll get better connectivity running a private server on an IP flagged as "Dial-Up" than using Comcast's email servers to relay, well, you've got another think coming.
    52. Re:Off by default by A55M0NKEY · · Score: 1

      I have kmail set up to send it's mail using sendmail because my ISP's SMTP server is down so often - more often than the servers of my intended reciepients it seems!. An ISP mandating a hardware reverse firewall will piss off their own customers who want to do things on blocked ports for the benefit of everyone else who won't have to recieve zombie spam from infected users of theirs. It won't happen. It violates economics.

      --

      Eat at Joe's.

    53. Re:Off by default by gerardrj · · Score: 2, Interesting

      Let me reply to the 11 or so people who missed the points of my post:

      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 can read my mail at any time. with a sniffer they need to intentionally grab the relevant data off the wire with a sniffer and reassemble the packets. Then they can read the email for the time they were capturing.

      3. Most everyone missed the larger point. FILTERING isn't the answer to spam. Not allowing the messages to be sent from the remote server is the answer. Using many aliases is key do doing that. It stops your spam problem dead in it's tracks and saves a lot of bandwidth. SPAM will only go away when the vast majority of send attempts fail with "User not known" messages from server to server. That can only happen with mail aliasing or something similar.

      4. Many people stated that they like this limit because "it's bad netiquette" to email large files, or there was no reason to do so. Perhaps since HTTP wasn't intended for large binary distribution, ISPs should also limit the size of images and binary data that are transferred over the protocol. Email wasn't intended to carry anything but text messages, perhaps ISPs should start rejecting any MIME encoded mail? NNTP wasn't designed for binary data, but as a discussion mechanism. should all the binaries groups be deleted/rejected/filtered? All are equally absurd arguments. Protocols should be used for what they can be used for until something better comes along.

      5. Many noted that you can do this either with remote mail servers, or just have your email client contact your ISP's server and then do forwarding/notification. The first involves dragging the message unnecessarily across the Internet an extra time. The second involves repeated contacts with your ISP's server about every minute, or at least very frequently, thus increasing its work load. Neither seem as ideal a solution as running your own server. And WHY would you want to pay for a service that you can get for free and have more functionality to boot?

      6. I do have a "decent" ISP service wise. I have a cable modem with 3.2Mb/640Kb bandwidth with a static IP and am two hops to the AT&T backbone with better than .1% downtime. I can run servers and have almost no political BS as with COX or other broadband providers I've used or read about. I get all that for less than $60/month after taxes. What I expect from my ISP is unfettered access to and from the Internet via TCP/IP protocols. I don't want email, I don't want weather reports, I don't want a proxy server or filtering or newgroups or help installing software.

      And then "blacklisting". Nope, not blacklisted anywhere I've tried to send mail yet. At least not because of my IP address. There were two instances where mail didn't get through to the recipient, but that had to do with reverse lookups not matching the claimed hostname from my server, it was easily fixed. In fact, I get to blacklist entire TLDs for incoming mail that my ISP can't. I KNOW I'll never receive a legitimate email from Japan, Malaysia, Poland, Argentina, etc... so all of those TLDs are rejected before the message is sent.

      It is the norm in the postal system that each recipient operates their own receiving receptacle (a mailbox or mail slot) for privacy and expediency. Why is it the norm with email that you allow/pay for someone else to operate your receptacle and you have to go get your mail or as someone else to send out a piece of mail for you?

      In the end running your own server is the best thing you could do for the 'net. It saves bandwidth, reduces and nearly eliminates SPAM. As for the not knowing how? Most GNU/Linux distros come with sendmail or something similar installed and ready to operate with just about zero configuration.

      --
      Article X: The powers not delegated... by the Constitution...are reserved...to the people
    54. Re:Off by default by mdfst13 · · Score: 1

      Automatic checkers (SpamAssassin, SPF) read the headers (and block the message) *before* you determine that it's a legit message. The end user still won't know the difference...but they won't read your message either.

      I've found mail in my SpamAssassin junk box that did essentially what you describe. It's the wrong way to do it, and the recent trend of aggressive spam blocking by AOL, HotMail, Yahoo, etc. is soon going to make it an unsuccessful way in the near future.

    55. Re:Off by default by techno-vampire · · Score: 1

      Automatic filters will block messages where the sender's domain doesn't match the IP only if you set it to do so. It's not always safe to assume that a mis-match like this means spam. If I had a domain hosted as a virtual domain sharing an IP with similar domains there'd be no way for me to do otherwise.

      --
      Good, inexpensive web hosting
    56. Re:Off by default by techno-vampire · · Score: 1

      Commercial accounts should be different. I don't know what the policy was for them at the ISP I did support for, as I concentrated on individual customers, not corporate accounts. My comments are meant to be for home users only and I should have specified.

      --
      Good, inexpensive web hosting
    57. Re:Off by default by techno-vampire · · Score: 1
      The concept of "netiquette" is dead and gone, along with the dream of a "commerce-free" Internet.

      What you're saying is that good manners are old-fashioned and it's now OK for you to be as rude, inconsiderate and selfish as you want. That's all nettiquette is, you know, good manners.

      --
      Good, inexpensive web hosting
    58. Re:Off by default by techno-vampire · · Score: 1

      It's not that you have no right to do so, it's that I see no reason that you would want to on a home account, except for geek value. Just because most people did back when the net was young doesn't mean that you should need to today, anymore than the fact that one hundred years ago you could buy stock on 10% margin means that you should be able to today.

      --
      Good, inexpensive web hosting
    59. Re:Off by default by Malc · · Score: 1

      Static IP with my ISP is CAD$4/month, or CAD$50 one-off.

    60. Re:Off by default by Malc · · Score: 1

      7. Log files. See why you didn't receive a message, or why on outgoing connections the recipient hasn't received it yet.

    61. Re:Off by default by Geoffreyerffoeg · · Score: 1

      only allow mail connections to their own mail servers unless the user asks otherwise.

      Or disable port 25 [semi-good], 80 [little reason], and 139/445/other WinRPC ports [very good], unless the user pays an extra $30/month for a "business account". Cox Internet: broadband capitalism. I would so love to leave Yahoo! for something I myself run, I have to put my webserver on port 8080, and I once had a need to use filesharing across the network (duly opening my firewall remotely just for that) - it was not possible.

      Of course, the profit motive may be the only way to get ISPs to block these ports by default...even though there is plenty of money to be saved in lowering attack traffic on your own network.

    62. Re:Off by default by Anonymous Coward · · Score: 0

      You may be getting buried by spam from Comcast, but that's *the problem*. On all those crap messages, the source address IS NOT Comcast's SMTP, it's some end-user's whorebox.

      Using their servers for outgoing mail makes it more legitimate, since it's coming from a known IP address, and is sent by a real mail client instead of a viral SMTP engine.

      Unless you're actually talking about websites mentioned in junk mail, in which case you have no concept of what blackholing/listing means.

    63. Re:Off by default by pclminion · · Score: 1
      What you're saying is that good manners are old-fashioned and it's now OK for you to be as rude, inconsiderate and selfish as you want.

      How is it rude and inconsiderate to exchange multi-megabyte email attachments between people who have all agreed to do so? Please, explain.

    64. Re:Off by default by Rain · · Score: 1
      SPAM will only go away when the vast majority of send attempts fail with "User not known" messages from server to server.
      Sadly, no it won't.
      Per-Day Traffic Summary
      date received delivered deferred bounced rejected

      2004-07-14 720 724 192 21 4081
      2004-07-15 901 919 194 25 5879
      2004-07-16 804 821 197 32 5919
      2004-07-17 911 968 287 69 5463
      2004-07-18 749 721 360 25 5412
      2004-07-19 948 994 430 27 7563
      2004-07-20 1012 1020 481 31 6258
      2004-07-21 650 635 368 24 4294
      Reject reasons:
      10926 sbl.spamhaus.org
      9171 Recipient address rejected: User unknown
      8757 Helo command rejected: Syntax error in hostname.
      8483 list.dsbl.org
      4449 Helo command rejected: need fully-qualified hostname
      1337 opm.blitzed.org
      402 Relay access denied
      364 Recipient address rejected: Improper use of SMTP command pipelining
      220 relays.ordb.org
      118 Helo command rejected: You aren't AOL!
      91 Recipient address rejected: No UCE.
      45 Helo command rejected: You aren't CompuServe!
      28 Sender address rejected: need fully-qualified address
      26 Sender address rejected: No UCE.
      9 Recipient address rejected: While that may be true, we don't want your spam.
      4 Recipient address rejected: BALEETED
      2 rbl.bluecherry.net

      The users mail is bouncing for haven't existed since 2002. Spammers haven't even cared about rejected messages for some time.

      Slashdot rules. I had to remove some of the formatting in my message because of the so-called "lameness" filter (obviously named after itself, for all the good it's doing.) Some of the formatting has been lost as well, since <pre> is no longer allowed--I'm not going to even bother reformatting it after fighting with the lameness filter. With wonderful misfeatures like this, it's no wonder the quality of discussion here has gone down over the years.

      Anyway, the first table is the output of pflogsumm, which provides much more information than just that table, and looks much better when its output isn't raped by Slashdot. You can grab pflogsumm from http://jimsun.linxnet.com/downloads/pflogsumm-1.1. 0.tar.gz, but it only works with postfix's logs, as the name suggests.

    65. Re:Off by default by mdfst13 · · Score: 1

      "Automatic filters will block messages where the sender's domain doesn't match the IP only if you set it to do so. It's not always safe to assume that a mis-match like this means spam."

      Actually, the way the filter works is it looks for various common spam characteristics and only blocks if several are met. This just happened to be what put it over the edge. Further, it is worth pointing out that I don't configure the filter...the mail server administrator does. As I pointed out elsewhere in this thread, mail administrators do not always accept email just because it might be legitimate.

      "If I had a domain hosted as a virtual domain sharing an IP with similar domains there'd be no way for me to do otherwise."

      There is no reason why multiple domains can't share the same IP or even IPs. The DNS looks ugly but is not impossible.

    66. Re:Off by default by egburr · · Score: 1

      My mail server run from my house has had less total downtime than that of any one single ISP I have used in the past 5 years. (Not counting a ten day outage after an ice storm, where I had more pressing concerns than mail, such as power and heat.)

      --

      Edward Burr
      Having a smoking section in a restaurant is like having a peeing section in a swimming pool.
    67. Re:Off by default by Anonymous Coward · · Score: 0

      It's fine as long as:

      1. You are emailing the files over an exclusive LAN, and not a shared pipeline. If it is a shared pipeline, you should be considerate of others, and avoid the massive encoding overhead that is required for email.

      2. You both own the mailservers. If this is not the case, then I'm sure your mailserver admin will LART you.

    68. Re:Off by default by gerardrj · · Score: 1

      I agree that undeliverable mail addresses have little effect on the behavior of spammers today, but I also think it will become an issue spammers will need to deal with.

      There will come a point when there will be more ex-addresses than currently deliverable ones.
      Unless spammers find some revolutionary new way to get their messages out they have a finite amount of resources with which to send. With more and more undeliverable addresses, they will see their responses rates go from low to nearly non existent and they will be forced to cull undeliverable addresses to keep the response rate up and their profit flowing in.
      If they get (numbers out of my ass) 1 response per 100,000 emails today, then they may see only 1 response in 300,000 as more addresses become undeliverable.

      My argument that is if we could get enough "bogus" address on the lists, spammers would be forced to either give up, or maintain the lists via additional effort and cost. It's the old "bury them in what they asked for" stunt.

      Will it work? I don't know for sure. I do know the alias idea works. Like you, I see lots of "user unknown" responses in my logs, but to me that's a good thing: one less message that got through.

      --
      Article X: The powers not delegated... by the Constitution...are reserved...to the people
    69. Re:Off by default by kcurrie · · Score: 1

      RoadRunner got rather pissed off at me once because I ran a caching DNS server at my house.

      How could RoadRunner know that you were running a caching DNS server at home unless you were ACTING as a DNS server to those externally?

      --
      -- I speak only for myself.
    70. Re:Off by default by f0rt0r · · Score: 1

      Good points all around! I also have been running multiple domains for approximately six years, including all the standard services - DNS,FTP,SMTP,HTTP. The benefits are huge, not just in the spam arena, but the control and privacy it gives you cannot be matched by any ISP at a comparable cost. It is not that hard to set up a POP3/SMTP server that is locked down.

      Email aliases are the bomb. Besides blocking spam, you also can avoid those annoying email bulletins from sites you have accounts on. I just turn off the email alias unless I need to do a password change confirmation email from them or something similar. I turn it on, complete the task, and then turn it back off again.

      Running my own web server was also a huge break cost-wise because I get Gigabytes of storage space for my content at no additional cost!

      Anyhow, getting of my soapbox, the point is blocking port 25 is not a wise move. The Internet RFC's are designed in the spirit of every network device is a peer to ever other network device, and there are to be no restrictions on their communication except at each endpoint ( device ).
      i.e. my ISP cannot block my communication with another network device ( host ), but the host is allowed to set up restrictions if so desired...like a firewall :)

      --
      I can't afford a sig!
    71. Re:Off by default by techno-vampire · · Score: 1

      Multiple domains on one IP make reverse DNS lookup hard, if not impossible. I'm no expert on it, but I gather that when you send an IP in for RDNS, you expect to get exactly one hostname back, and if there's more than one, it's hard to know which to send. As far as the filtering goes, with more and more people sending business email from home over their private ISP's servers, we're all going to see an increase in legitimate email who's address doesn't match the IP. I'm not saying this should be taken out of the filters, but maybe its priority should be lowered. Again, I'm not an expert on this and would welcome input from somebody with more direct experience.

      --
      Good, inexpensive web hosting
    72. Re:Off by default by techno-vampire · · Score: 1
      Either you're exceptionaly skilled in keeping your server up or you've had bad luck with ISP's. The one I worked for had enough servers and reduncancy that the system was almost never down, although sometimes, of course, an indiviual server might be offline. As we had several different names for the servers (all served from the same IP pool) it was easy to change the server name, get a new DNS lookup and the IP of a currently working server.

      I don't think you can blame yourself for an outage after an ice storm. Acts of God take precedence over almost everything.

      --
      Good, inexpensive web hosting
    73. Re:Off by default by techno-vampire · · Score: 1

      Not sending huge attachments (and, of course, the bottom limit of "hugh" grows as does bandwidth) is just one part of nettiquette. Keeping lines in Usenet posts to a certain limit, .sig seperators and size, and any number of other things are included. Good manners are the grease that keep the wheels of civilization turning without too much friction, and you abandon them at your peril.

      --
      Good, inexpensive web hosting
    74. Re:Off by default by Anonymous Coward · · Score: 0

      Bell Sympatico is already doing this port blocking to their residential and business users. Unfortunately, we're not allowed to ask to remove it, so we have to pay our DNS/Domain hosting company $20 extra for a mail port forwarding service.

      So those companies who plan on implementing this, make sure you allow your customers unrestricted access to which ports they want open, or you may loose them to other competing companies. I did (as a residential user).

    75. Re:Off by default by f0rt0r · · Score: 1

      Those days are only gone if we allow them to be. ISP's that don't follow the spirit of the Internet as designated by the creators thereof, should get out of the way and let those who will take over. It will happen that was as people like me will go with the ISP who provides the best quality of service, and blocked ports is just plain bad service.

      --
      I can't afford a sig!
    76. Re:Off by default by JWSmythe · · Score: 1

      /usr/sbin/named
      echo "nameserver 127.0.0.1" > /etc/resolv.conf

      They were portscanning everyone, and aparently cutting people of for just about nothing. Like, how dangerous is a free roaming DNS server? It was up to date, it just wasn't configured for anything at all, except to cache my resolutions.

      --
      Serious? Seriousness is well above my pay grade.
    77. Re:Off by default by zo219 · · Score: 1

      The next guy up bought a Mac, is running Panther and a third party background app called Little Snitch, which asks me whenever anything wants to call out, the default being: No.

      Gee, that was tough.

      You people are talking about Windows, a shocking piece of code-crap. It's important to remember that.

    78. Re:Off by default by cburley · · Score: 1
      You're essentially arguing in favor of additional gratuitous points of failure by claiming there's little or no reason for well-connected end users of ISPs to run their own mailservers.

      From a reliability point of view, I believe the opposite is true: that it's actually better for end users to exchange mail messages (and other higher-level communications) directly, on an end-to-end basis, with as little interference from, and dependency on, intermediaries, beyond their use as necessary low-level transport agents.

      After all, those intermediaries are, like any component in a well-engineered system, better designed and used for a small number of tasks -- in the case of upstream ISPs, interconnecting portions of the Internet and transferring packets among them should be their main focus, not running mail servers, HTTP proxies, and so on.

      Practically speaking, yes, I can have my domain registrar do email forwarding for me. But you know what? They have an email size limit that is substantially lower than the occasional legitimate email I send or receive.

      And why shouldn't they have such a limit, since they're in the business of registering domain names, not serving as an email forwarder, which is just a convenient add-on service?

      And, yes, I can sign my outgoing emails with GPG, so while they're sitting on my upstream ISP's server, they can't be read...but that does nothing for my incoming email, and if you think it's just as easy for an corrupt employee at an ISP to scan packets in transit to port 25 on my system as it is for her to start the 3rd shift by searching all pending emails on the server for any destined for my system, I'd like to know why you don't go into the spammer-catching business, since it has some of the very same problems.

      The fact that you ask if the OP heard of fetchmail illustrates the problem regarding multiple points of failure. fetchmail has had its share of bugs, so why require its use for a large class of users that would otherwise not need it to get useful work done?

      I use fetchmail to pull mail down from my upstream ISP, which gives me essentially no opportunity to reject (or especially tarpit) known spam or sources of spam as the spam is injected into "my" mailbox (in the extended sense of including my upstream POP3 mailbox), meaning that, with fetchmail, I have to wait for a 10MB message that ends up being detected as spam by my local software to be downloaded before I get the 2K legitimate message I really need.

      Whereas, with direct injection into my system (which is what happens for my four "vanity" domain names), those two hypothetical messages are handled asynchronously, as designed by the SMTP protocol, and possibly even while I'm doing something else, so I don't have to wait for fetchmail to run. (Or I can have fetchmail run automatically every minute or so, which adds a whole 'nother set of problems, among them performance problems. Sometimes my fetchmail runs have simply not worked because my old dialup ISP's POP3 server was having problems -- thank goodness most of my important email comes directly into my system!)

      And, yes, it's nice if your upstream ISP is nearly 100% reliable, but, again, you clearly cannot have TCP+SMTP reliability exceed that of TCP-only reliability for a given upstream ISP.

      Depend on your ISP to store-and-forward your outgoing and incoming email as well as push packets around, and you're guaranteed to lose a bit of reliability right there.

      And, unless you've got another "path" to your ISP and its mail server than your home computer, it really doesn't matter much that its reliability exceeds that of your computer, does it?

      I mean, other than the convenience of having all pending emails already on your ISP's mail server when your power and/or local network comes back up, either way, you can't send or receive email while your home computer is down.

      There are definite advantages to letting your upstream ISP handle your mail service -- I'm not arguing

      --
      Practice random senselessness and act kind of beautiful.
    79. Re:Off by default by Ryan+Amos · · Score: 1

      No, those days are gone not because of the ISPs, but because of the massive amount of dangerous crap out there (outlook worms, windows worms, spyware/trojans, etc.) You can't trust what comes in nor what goes out, so it should be checked in some way.

  9. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  10. Are they user proof? by Jailbrekr · · Score: 1

    How can you make a reverse firewall as easy to set up as a normal consumer firewall? Is technology advanced and automated enough where this reverse firewall can detect when a user is sending email via port 25 to his or hers ISPs SMTP server? Can a reverse firewall tell the difference between spam being sent out, and someone emailing his entire family with good news about his daughters report card?

    A better solution is for ISPs to block port 25 for all consumer connections, and only allow port 25 traffic to their own SMTP servers. Why put the onus on the consumers, when it is the ISPs who seem to be failing us?

    --
    Feed the need: Digitaladdiction.net
    1. Re:Are they user proof? by eingram · · Score: 1

      Can a reverse firewall tell the difference between spam being sent out, and someone emailing his entire family with good news about his daughters report card?

      Sure. Setup a basic word filter to look for "enlarge" and "penis." Stop all e-mail that matches. ;)

    2. Re:Are they user proof? by black+mariah · · Score: 2, Insightful
      Why put the onus on the consumers, when it is the ISPs who seem to be failing us?
      Because the users are the ones that have the "FREE PORN NOW" software on their computer that creates all that spam in the first place. Always look towards user stupidity for your first answers.

      --
      'Standards' in computing only impress those who are impressed by things like 'standards'.
    3. Re:Are they user proof? by Nekkrist · · Score: 1

      A better solution is for ISPs to block port 25 for all consumer connections, and only allow port 25 traffic to their own SMTP servers. Why put the onus on the consumers, when it is the ISPs who seem to be failing us?

      The problem with this is that those of us who use a mail account from work, school, and our home ISP may want to send mail from each of these accounts. An ISP blocking our school and work SMTP servers would be a pain.

    4. Re:Are they user proof? by Anonymous Coward · · Score: 0

      There are plenty of sender authentication protocols already available, so you can use any mail server from anywhere, securely, as long as you have the credentials to authenticate.

      And, these already existing technology (AuthTLS, etc) operate on ports other than 25, so they aren't shut down.

      All residential and small business connections, at least, should have this restriction (port 25 blocked), and ISP's mail servers should have some reasonable limit on the amount of emails sent per day (say 100 per day outgoing).

    5. Re:Are they user proof? by arivanov · · Score: 1

      What is the bloody effing point? All the technology is already in the CMTS and BRAS systems. All it takes is to know how to configure it (yeah I know, difficult and painfull process for a cable company). In fact it is being used - Freeserve, which holds 25% of the UK dial and DSL market used to transparently proxy all outgoing mail traffic to their mailserver and spamcheck it on ingress. Similarly there are other ISPs out there who hijack outgoing mail and make it go through their servers. This is trivial.

      --
      Baker's Law: Misery no longer loves company. Nowadays it insists on it
      http://www.sigsegv.cx/
    6. Re:Are they user proof? by Anonymous Coward · · Score: 0

      I'm a net engineer for a catv company. We are just starting to roll out egress filtering on a lot of our systems. Most DOCSIS modems support access lists, so you block outbound port 25 AT THE MODEM LEVEL. The lists are sent out from the CMTS upon init and any unhacked modem will acknowledge and use them. Eliminates the unauthorized traffic coming over the HFC plant (frees bandwitdh for legit use) and you eliminate a point of failure by not having to throw a firewall between your CMTS and your access routers. Works great too, we just started rolling it out and the level of SPAM complaints have pretty much dropped to nothing. Need port 25 for a legit reason, you can have it (provided you pay for an account with a static ip, and you reallize that as soon as you attempt to spam we are shutting you down). Same reasoning applies to the ms ports. Force it to stay in the subscribers network, not ours. Not sure about DSL but i assume the same could be done.

    7. Re:Are they user proof? by Anonymous Coward · · Score: 0

      A better solution is for ISPs to block port 25 for all consumer connections, and only allow port 25 traffic to their own SMTP servers. Why put the onus on the consumers, when it is the ISPs who seem to be failing us?

      I worked at the major ISP in my country and the problem has never really been incoming spam but customers' computers who were used to relay spam. And it's this that get you black-listed if too much spam comes from your servers.

    8. Re:Are they user proof? by Jailbrekr · · Score: 1

      Well, if you want to sit back and keep pointing the finger without offering an achievable solution, by all means go for it. In the meantime, the most realistic solution would be ISP centric, because they are the ones with the know how, as well as being able to effect these changes centrally.

      --
      Feed the need: Digitaladdiction.net
    9. Re:Are they user proof? by Bill_Royle · · Score: 1

      Bad idea, now that VPN clients sometimes (if not always)route PC traffic via the corporate firewall. Thus, look at the reality:

      Some employees access their work via VPN using their home PCs. What do they do when their personal email on their personal PC won't go out?

      Don't suggest that companies should buy every employee a PC - that's not going to happen. Anyone that's spent a few years in the industry knows that companies don't do that generally.

    10. Re:Are they user proof? by DJBigShow · · Score: 1

      I think there might be some confusion as to how these spambots work. I don't have a lot of experience with them, however the ones I've encountered have actually used my ISP's SMTP server.

      I believe the reason for this is because my ISP's SMTP server will relay any message it receives from me due to the fact that I am assigned an IP address from that ISP. If the spambot didn't have access to my ISP's open-relay SMTP server, it would require access to some other open-relay SMTP server off of the net which are very hard if not impossible to find, or it would need to perform DNS look-ups to determine the mail server responsible for every domain it attempts to e-mail.

      I don't think blocking port 25, except to your ISP's mail server, will solve anything.

      -DJBS
    11. Re:Are they user proof? by cujo_1111 · · Score: 1

      What about 'pen15' and 'E_N_L_A_R_G_E'?

      Your filter would be better off using a bayesian method on both directions of communication.

      --
      If I point out that you are incorrect, making me a foe does not make you any more correct.
    12. Re:Are they user proof? by thecombatwombat · · Score: 1

      Can a reverse firewall tell the difference between spam being sent out, and someone emailing his entire family with good news about his daughters report card?

      If it can, I'll buy one for every member of my family.

  11. Oh yeah, router manufacturers will buy this... by cleverhandle · · Score: 4, 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?

    1. Re:Oh yeah, router manufacturers will buy this... by Anonymous Coward · · Score: 0

      viruses are not Microsoft's problem as such. Especially since some of the more successful ones don't do anything that they wouldn't be allowed to do on any other operating system.

    2. Re:Oh yeah, router manufacturers will buy this... by comet_11 · · Score: 4, Informative

      For the love of jesus, I hate any slashdot article relating to viruses. I have to read through comment after comment using the accursed "virii".

      "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, and stop making me - and anyone who knows the word - cringe.

      --
      By reading this comment, you immediately waive any and all rights regarding it.
    3. Re:Oh yeah, router manufacturers will buy this... by Anonymous Coward · · Score: 0

      Virii sounds much better than Viruses.

      And considering how language evolves, it only takes all the /.ers to continuesly misspell a word to make it right.

      Just the the USAians did with Colo[b]u[/b]r.

    4. Re:Oh yeah, router manufacturers will buy this... by double_plus_ungod · · Score: 2, Funny

      but this discussion is about how to prevent our beloved boxen from sending spam.

    5. Re:Oh yeah, router manufacturers will buy this... by RTPMatt · · Score: 1

      um... am i the only person who has heard of a NAT? Although, this wont stop absolutly everything, it will stop most of these takeover before they even begin

    6. Re:Oh yeah, router manufacturers will buy this... by Anonymous Coward · · Score: 0

      Sure they will... what about the extra hardware they'll get to sell. This article is basically talking about increasing the amount of firewalls on networks.

    7. Re:Oh yeah, router manufacturers will buy this... by holysin · · Score: 1

      (//Theory mode on)

      No, manufacturers will (each)take this step to dominate the market since there will be demand for all new accesspoints, routers, cable modems, etc.

      They also will increase the price for said object 50-100% higher then the expected additional costs of said modifications.

      (//Theory mode off)

    8. Re:Oh yeah, router manufacturers will buy this... by FFFish · · Score: 1, Insightful

      Virii may not be a word, but it is fun. And it's a little bit viral, too, because the more people use "virii," the closer it comes to being standard English. Which, as you must surely know, is choc-a-bloc full of mangled words.

      Virii: don't pass on it, pass it on!

      --

      --
      Don't like it? Respond with words, not karma.
    9. Re:Oh yeah, router manufacturers will buy this... by dpilot · · Score: 1

      Someone else already said that router manufacturers compete on features, and security is one of these features. So yes, they will, as much as the market forces them.

      First off, I am not an employee or stockholder of Netgear, etc.

      But I like my Netgear FR114P.
      I bought it a little over a year ago, because I saw the Internet becoming a nastier and more hostile place, and didn't feel I had the time to exercise the necessary due diligence to keep a software firewall safe.
      It has Stateful Packet Inspection and some pretty flexible firewall rules, as well as the normal router-box features.
      I have already blocked all outgoing port 25 connections from my LAN, except from my mail hub, as well as the NetBIOS ports. I suppose with a little more effort I could change port 25 into a point-to-point from my mail hub to my ISP's relay.

      This box could do what you want. It's the 'by default' that's missing.

      I suspect the other necessary detail would be for DHCP (or PPPoE) to send a mail relay IP, just like it sends DNS and NTP, today. I'm setting up Kerberos at home now, and have set up DNS TXT records to identify that, so that technique could be used, too. Or for that matter, an internal-side MX record. It's all just client-side stitching.

      --
      The living have better things to do than to continue hating the dead.
    10. Re:Oh yeah, router manufacturers will buy this... by BroccoliGod · · Score: 1

      Boxen at least has some precedent, and I don't think most slashdotters actually think it is the correct plural. Virii has no precedent: drop the "us" and add "ii"? It is just plain wrong; it is a joke misspelling. But if everyone starts telling the same joke, it's no longer funny. Yesterday I saw virii on my university's helpdesk website. Sad. Very sad.

    11. Re:Oh yeah, router manufacturers will buy this... by southpolesammy · · Score: 1

      Well....that depends. Virii is not a valid English word, but since the singular word virus is not an original English word, but actually a borrowed Latin word, then the plural of the Latin word virus is actually virii. This is almost certainly the source of all the confusion, and it's an honest mistake that a lot of people make.

      However, bastardized words like 'alot', 'irregardless', 'gotten', 'orientate', and 'remediate' do get on my nerves.

      --
      Rule #1 -- Politics always trumps technology.
    12. Re:Oh yeah, router manufacturers will buy this... by poot_rootbeer · · Score: 1

      "Virii" is, and let me put this gently, not a goddamn word.

      Neither are "mouses" and "boxen", but they're both widely-used and generally-accepted plural forms in the tech world.

      Quitcher bitchin'.

    13. Re:Oh yeah, router manufacturers will buy this... by misterpies · · Score: 1


      Well the problem with that page is that the only thing the various contributors do agree on is that the plural is not virii. On the other hand, it could equaly well be viruses, viri, vira or virora...My hunch would be to go for vira:

      I. From existing Latin written sources, it's clear that virus was a neuter noun in latin. That makes it overwhelmingly likely that the plural ends in -a (almost all neuter plurals in all indo-european languages end in -a. It's still true in modern i.e. languages that retain a neuter case, eg Polish and Russian).

      II. Written sources also indicated that the genitive singular of virus is viri. Since the plural forms of latin nouns generally share the stem of the genetive singular, that indicates that the stem of the plural is "vir-"

      III. Put them together and you get vira.

      And anyone who says it's vires...that's latin for "men". And yes, while we do have an unstoppable drive for reproduction together with a desire to access hidden ports, that's where the similarity ends. Well, OK, we're good at breaking things too.

      --
      The author of this post asserts his moral rights.
    14. Re:Oh yeah, router manufacturers will buy this... by Idarubicin · · Score: 1
      Well....that depends. Virii is not a valid English word, but since the singular word virus is not an original English word, but actually a borrowed Latin word, then the plural of the Latin word virus is actually virii.

      Actually, that's incorrect Latin, too.

      There are other pedants who will no doubt go into much more detail, but the 'correct' Latin plural would be viri or vira. 'Virii', if such a word existed, would be the plural form of 'virius'.

      --
      ~Idarubicin
    15. Re:Oh yeah, router manufacturers will buy this... by adolf · · Score: 1
      The page you link to refers, at length, to a bunch of Latin mumbo-jumbo.

      Not only do I not speak Latin, but I have no intention of ever attempting to try. I'm an American, and I speak American English.

      While Latin is dead and stagnant and firm, English (in any of its dialects) is extremely nonsensical, and still under very active development. English presents itself as a mere collection of ever-changing common words, and a set of very loose rules to confine their use. The reason that English dictionaries are under constant revision is for the inclusion of new words.

      New words? That's right. People use new words all the time. Eventually, some of them end up being defined by a dictionary.

      Since "virii" is, plainly, a very common word, it therefore is. Perhaps it might be categorized as slang, but that doesn't make it nonexistant, nor does it make it somehow not a word, no matter what your Oxford tongue believes.

      'Sides, I reckon that ya'll know where an argument about slang words might lead. And this just ain't the place for all that.

      "Virii" is an English word. It is a fun word. It's fun to say, fun to write, and fun to look at. It is simply defined as a plural of the word "virus". (And you knew this already, since you're obviously able to grok its meaning.)
      It is often forgotten that (dictionaries) are artificial repositories, put together well after the languages they define. The roots of language are irrational and of a magical nature."
      -Jorge Luis Borges, Prologue to "El otro, el mismo."

      Learn to adapt. Your language is leaving you behind.

    16. Re:Oh yeah, router manufacturers will buy this... by PzyCrow · · Score: 1

      A word has a meaning in the context of the communication and the experience it triggers in the receiving end. And only then.

      I herby declare "virii" to mean computer viruses.

    17. Re:Oh yeah, router manufacturers will buy this... by ispeters · · Score: 1

      Since we're already well OT, how would you pronounce virii? When I read it and the writer means "more than one virus", I usually "hear" viri in my head (two syllables: vie-rye), but if virii is the plural of virius, then I suppose virii would sound like radii: veer-ree-eye, no?

      Ian

    18. Re:Oh yeah, router manufacturers will buy this... by Idarubicin · · Score: 1
      I usually "hear" viri in my head (two syllables: vie-rye), but if virii is the plural of virius, then I suppose virii would sound like radii: veer-ree-eye, no?

      Quite. What you're hearing in your head is the correct pronunciation of the (less incorrect) version of the plural. Your subconscious has learned how to form pseudo-Latin plurals. The pronunciation with three syllables would be the appropriate way to say the (completely incorrect) 'virii'.

      Of course, life would be simpler if people could just move on and use the (unquestionably correct) form, 'viruses'.

      --
      ~Idarubicin
    19. Re:Oh yeah, router manufacturers will buy this... by Anonymous Coward · · Score: 0

      What you say is true in principle, except:

      • The word is not even sort of in common usage. It's a slashdot nerdism.
      • The 'latin mumbo-jumbo' you refer to is constantly referenced as an authorative source because 'virii' is an attempt by the less than classically literate to latinize a noun that essentially oughtn't to be. Again, a nerdism.
      • This attempt to latinize the plural arguably comes from the intelligent, geeky desire to be correct about things. The truth is that the vast majority of english speakers do not grok latin endings; they are dying out. Less and less people use them, just in general.
      • Given the above, there's a certain rebelious desire on the part of geeks to do it the right way, except that in this case, the geek who thinks latin is mumbo jumbo and yet still tries to construct latinate plurals is wrong, and the unwashed, uneducated masses who naively pluralize the word just like the vast majority of english words are pluralized is right.
      • Frustrated by this, the geek in question starts talking about language evolving, even though only Slashdot reading script-kiddies actually say virii. Absurd.

      The truth is, when you write virii, you simply expose yourself as someone ignorant, which is not well regarded in the larger geek community. You talk about 'latin mumbo jumbo', but the precise reason most geeks care about latin is because it is mumbo-jumbo, it's stuff the vast majority of ignoramuses out there simply do not grok, and as such represents a sort of arcane geek-knowledge. You were motivated to use virii in the first place for this reason.

      Anyway, type what you want, but realize that it makes you look like an idiot, just like people who use leetspeak when posting look like morons. Leetspeak is fun to type. Whether it is fun to read, is, like "virii", dependent on who is reading, but I'll wager that most informed people disdain both.

    20. Re:Oh yeah, router manufacturers will buy this... by adolf · · Score: 1
      The word is not even sort of in common usage. It's a slashdot nerdism.
      I've been seeing the word "virii" since about 1992, but that was on a BBS, and is of course gone. However, Google has references to computer virii going back as far as 1988. The word therefore predates Slashdot by a number of years.
      The 'latin mumbo-jumbo' you refer to is constantly referenced as an authorative source because 'virii' is an attempt by the less than classically literate to latinize a noun that essentially oughtn't to be. Again, a nerdism.
      Mumbo-jumbo, indeed. Is a solid understanding of Latin a prerequisite for the forming of new English words?
      This attempt to latinize the plural arguably comes from the intelligent, geeky desire to be correct about things. The truth is that the vast majority of english speakers do not grok latin endings; they are dying out. Less and less people use them, just in general.
      Of course. However, the populace's generally shrinking vocabulary has little to do with a language's ability to absorb new words. I use terms every day in my line of work which are inarguably correct, but completely unknown to people outside of my trade. Next.
      Given the above, there's a certain rebelious desire on the part of geeks to do it the right way, except that in this case, the geek who thinks latin is mumbo jumbo and yet still tries to construct latinate plurals is wrong, and the unwashed, uneducated masses who naively pluralize the word just like the vast majority of english words are pluralized is right.
      Ok. Show me the rule that says a pluralized noun may not have synonyms. I'm not arguing that "viruses" is in any way incorrect. I'm arguing that both are correct.
      Frustrated by this, the geek in question starts talking about language evolving, even though only Slashdot reading script-kiddies actually say virii. Absurd.
      *sigh* You've failed to research the topic before bantering on about it.

      A quick bit of research, using Google (of course) shows that there is about a 1:7 ratio of "virii" to "viruses" on Usenet, which sure seems like common usage to me, at least amongst the computer literate. (The computer illiterate have yet to create an easily-searched lexicon of their every utterance, and so their habits are rather difficult to study.)

      But you do raise an interesting point: Suppose that the only people using the term "computer virii" are the same people who are occupied with them in at least the capacity of a hobby, and the various-and-sundry computer professionals who are charged with cleaning up the mess.

      These are the people who make such things as virii a primary concern in their daily lives.

      Yet, you insist that they're all wrong, and that "virii" is improper. So, who is more qualified to name the things than that group of geeks? Should the scholars name them? The Bush administration? The pope? Rob Malda?

      If I were a woodworker who made building blocks for children, and I called my blocks "woodenblochten," would you be irate at my completely improper use of pseudo-German to contract and pluralize an English noun? Probably not. But what if it caught on? Even a little? What if 1 in 7 people started saying "woodenblochten" instead of "wood blocks"?

      If the people who create them, and the people who are employed by them want them called "virii," so be it. Latin be damned, English is moving along just fine, thank you very much.

    21. Re:Oh yeah, router manufacturers will buy this... by HermanAB · · Score: 1

      It is a word now - get over it.

      --
      Oh well, what the hell...
  12. Reasonable? by Southpaw018 · · Score: 1

    Seems reasonable. Too reasonable. Just like a deal with the devil.

    --
    ACs are modded -6. I don't read you, I don't mod you, I don't see you. Don't like it? Don't be a coward.
  13. The Journey of 1,000 miles by agentxy · · Score: 2, Insightful

    Great Idea! New technical concepts and products always excite me. We must keep one thing in mind however, hackers/crackers/spammers/whatever you want to call them are clever and very imaginative people. Single concepts and technologies will be overcome and bypassed. The security/spam fight needs to be a continuous and evolving process. One cannot simply rely on a single product or conceptual model to end malicious actions. When people start realizing that keeping computers secure is a process and NOT a product, the world will be a lot safer and secure.

  14. Ha! Beat you too it! by physicsphairy · · Score: 2, Funny

    I, being the ubergeek that I am, already have a 14k^H^H^H^H "reverse-firewall".

    No hackers for me, no siree!

  15. Old hardware by Endareth · · Score: 0

    So spammers either use slightly old hardware without the reverse-firewall, or simply use some of their ill-gotten gains to purchase higher end equipment, same as large companies or ISPs already do, which wouldn't have the reverse-firewall in it. Or even find a cheap hardware manufacturer who is will take simply not include the reverse-firewall in exchange for the spammers buying all their hardware for them.

    --
    Disclaimer: The above comment was made while under the influence of too much coding and not enough sleep.
    1. Re:Old hardware by physicsphairy · · Score: 1

      The idea here is not to stop spammers from using their own equipment, it is to stop them from using other's equipment (i.e. trojaned windows boxes).

    2. Re:Old hardware by Volmarias · · Score: 1

      At which point they get blackholed, and that nice shiny T1 is now useless.

      Only the most legitimate of spammers (and what an oxymoron that is)even use their own equipment anymore. What they're doing is semi-legal as it is, so taking the next step into actually breaking the law is reasonably trivial.

  16. Re:Not just for spam! by afidel · · Score: 1

    The problem is that unlike traditional NAT'ing firewalls where everything not part of an existing TCP/IP conversation can be thrown to the bit bucket there is no such simple rule for a reverse firewall. So you get into heuristics and signatures, which have to be constantly updated and which give a LOT more false positives than a simple NAT box, ask anyone who has worked with intrusion detection systems. Not only that but since updates have to be done constantly to screen for new threats there is an ongoing cost, and so companies will of course want to charge an ongoing fee, so instead of a cheap Linksys box just costing $50-100 it will cost that much AND have a monthly maintenance fee. I personally wouldn't want such a device for the same reason I don't own a Tivo, I hate perpetual revenue streams that add little value over what I can get with fixed function device. Now I personally would LOVE this for my business customers, I already utilize Sonicwall's with integrated virus enforcement, blocking machines with unusual usage paterns would be nice so long as the false positive rate were sufficiently low.

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  17. icewall. by silicongodcom · · Score: 1

    at least name it right!

  18. Reverse? by Anonymous Coward · · Score: 0

    I don't get it, how is this different from a regular firewall? Do they come configured to block everything by default?

    If anything, maybe filters that worked on a "if x packets in n time access y port then block" would be a decent idea. Like a lot of IRC scripts do as flood protection.

  19. Why this might be a good idea for this problem by Anonymous Coward · · Score: 1, Insightful

    SMTP is limited to one port (25), and most people are simply not sending out hundreds of emails per hour. A simple bit of rate limiting of the outgoing traffic (say 60 emails per hour) wouldn't even be noticed by 99% of home users. The other 1% probably knows what they're doing and could disable it. 60 per hour is plenty for the average person, but a hinderance to a spammer.

    1. Re:Why this might be a good idea for this problem by Anonymous Coward · · Score: 0

      I'd love to see a change to the SMTP spec so that the first 100k of any email is severely rate limited on a per connection basis.

      So, you send out an email with a 2 MB attachment, everything works as usual, save for the slower first 100k.

      You send out 25,000 spams for p3n!s enl@rgment p!ll$ and it takes you an eternity.

      Spam would drop off the face of the earth.

      Large mass mailing houses would be effected, but they could deal with it. I send out a newsletter to 75,000 subscribers monthly, and this would take several days instead of several hours to complete, but it's no big deal.

    2. Re:Why this might be a good idea for this problem by cujo_1111 · · Score: 2, Insightful

      I'd love to see a change to the SMTP spec so that the first 100k of any email is severely rate limited on a per connection basis.

      So, you send out an email with a 2 MB attachment, everything works as usual, save for the slower first 100k.


      How would this impact the spammers?

      They would just send fewer emails with more people in the BCC list. One email gets sent from the client and then the load gets put onto the servers sending it to all the recipients.

      Putting in arbitrary delays will only piss more people off. Sure, getting more people angry about SPAM may be a good thing to try and wipe it out but I think you may be going about it the wrong way.

      --
      If I point out that you are incorrect, making me a foe does not make you any more correct.
    3. Re:Why this might be a good idea for this problem by Anonymous Coward · · Score: 0

      Which is why I add delays for people listed in spam blocklists and doing other spammy things (ie huge BCC lists).

  20. Reverse firewalls? by afay · · Score: 4, Insightful

    First of all, the linked article simply describes a firewall blocking some outgoing traffic with easy rate limit rules (i.e. no email after x messages sent in y amount of time). There's no need to call it a reverse firewall. It's a firewall, plain and simple. Just because most people allow all outgoing traffic doesn't mean that if you block some you've invented a new type of firewall.

    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.

    --
    Best slashdot comment
    1. Re:Reverse firewalls? by FauxReal · · Score: 1

      Well, if it "sounds" different it's patentable isn't it? Someone call my lawyer we got some money to make!

    2. Re:Reverse firewalls? by laing · · Score: 1

      The rate limiting idea is good - but I think the spammers have already developed and deployed a countermeasure to it. The latest trend of having a large, distributed pool of spam bots gets past this safeguard. Each node in the pool can send low-volume spam and still deliver the spammers message very effectively. "There's strength in numbers."

      Either way, I don't like the idea of ISP's unilateraly deciding to change the terms of service after service has commenced. I'm in the very small minority of people who run their own mail exchanger.

      --
      This space for rent.

    3. Re:Reverse firewalls? by Anonymous Coward · · Score: 0

      Wait. We're going to firewall the machine with the machine, right?

      Great.

      I'll just shut down your internal firewall when I 0wn you. N0 pr0813M.

    4. Re:Reverse firewalls? by shird · · Score: 1

      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.

      And thats known as a 'personal firewall'. Many existing products do this already and are widely used. Zonealarm and KAV anti-hacker are two off the top of my head. I even use the KAV one, it is very good, and can help prevent apps that 'call home' from doing so etc. And any exploits that work by contacting a remote host via tftp etc are able to be blocked. (a better fix is to patch the exploit of course, but thats not always possible with 0 day exploits etc).

      --
      I.O.U One Sig.
    5. Re:Reverse firewalls? by God!+Awful+2 · · Score: 1

      First of all, the linked article simply describes a firewall blocking some outgoing traffic with easy rate limit rules (i.e. no email after x messages sent in y amount of time). There's no need to call it a reverse firewall. It's a firewall, plain and simple

      I think it's like a firewall configured in reverse. It's not a new type of firewall; it's just a different way of configuring a firewall.

      -a

    6. Re:Reverse firewalls? by cowbutt · · Score: 1
      I agree. This story is not news. The idea of 'egress filtering' has been around for ages and is common in security-aware corporate environments and universities.

      --

    7. Re:Reverse firewalls? by Anonymous Coward · · Score: 0

      It's laughable. Like we dont have enough jargon out there. Many people have pointed out that all firewalls (XP firewall excluded) do egress filtering.

      The second article has no significant content. Sounds like someone independantly came up with an idea similar to DEN (Directory Enabled Networking).

      How did this get on the main page?

    8. Re:Reverse firewalls? by Bishop · · Score: 1

      it's just a different way of configuring a firewall.

      Maybe for home users. Any good firewall blocks all packets (traveling in any direction) by default. The better packet filtering docs for Linux or BSD all start with default deny rules. Any sane company with a firewall will only allow a few outgoing ports.

      The correct term is egress filtering.

    9. Re:Reverse firewalls? by Nurgled · · Score: 1

      One thing I find amusing is that the term "firewall" comes from the practice of strategically-placing fire-retardant walls in buildings to slow the spread of fire in large office blocks, schools etc. Essentially, the firewall is there to keep the fire from escaping the area it started. These so-called "reverse firewalls" are closer to the idea of a traditional fire wall than the more usual model of stopping the fire from entering.

      (of course, there are cases where a fire wall is there to keep the fire out, such as around an important area of a building such as a data repository.)

    10. Re:Reverse firewalls? by waveclaw · · Score: 1

      It sort of looks like the submitter just googled for "reverse firewall" and posted the first match

      Yes, I'd have to disambiguate between the links as well. A "Personal Firewall" is a full Microsoft style system to stop an application from opening up ports for which you didn't ask to be opened. It is local to the individual PC and a very good idea in the World of Trojans/'spl0its/et al. A full Demillitarized Zone (DMZ) is more than a router with an extra port that has holes in the firewall for services. A full DMZ is a complete network between two firewalls - one that doesn't trust upsream 'Internet' traffic and one that doesn't trust downstream 'intranet' traffic. The (usually private) network between these two firewalls [1] is where your servers (and hopefully proxies) live.

      With a reasonable full DMZ, you can really slow down the affect of the Boss's infected laptop on your IIS boxes. With Personal Firewalls you can slow down that affect to other workstations on your network as well. Both are common in meduim to large companies, while the DMZ-hanging off one interface is common in SOHO environments.

      -----

      1. i.e. the internal-to-outside firewall is a machine in the private network served by the outside-firewall, often on a dedicated interface with it's own IP network. That way adding a secure WiFI bridge is as simple as adding a new inside-DMZ box with some form of VPN and some form of 802.11.

      --

      "You cannot have a General Will unless you have shared experiences. You cannot be fair to people you don't know."
    11. Re:Reverse firewalls? by God!+Awful+2 · · Score: 1

      Maybe for home users. Any good firewall blocks all packets (traveling in any direction) by default. The better packet filtering docs for Linux or BSD all start with default deny rules. Any sane company with a firewall will only allow a few outgoing ports.

      Yeah, well the article seemed to be talking about home users didn't it?

      And BTW, I think you'll find that there's tons of companies out there with a wildcard accept+NAT rule down at the bottom of their outgoing policy.

      -a

    12. Re:Reverse firewalls? by Bishop · · Score: 1

      there's tons of companies out there with a wildcard accept+NAT rule down at the bottom of their outgoing policy.

      I am sure there are. Those firewalls would not classify as "any good firewall." :-)

    13. Re:Reverse firewalls? by _pi-away · · Score: 1

      Thank god someone here knows what they're talking about, this use of "reverse firewall" as if it were anything different than an everyday firewall was driving me nuts. Kudos!

      Ingress and Egress people; this is what you should have been doing all along. Nothing new to see here, and certainly nothing reversed.

      --

      "The crows seemed to be calling his name, thought Caw."
    14. Re:Reverse firewalls? by DunbarTheInept · · Score: 1

      Exactly. A firewall is *already* a thing that can block traffic in two directions. A firewall blocking outgoing stuff is very common - like to prevent users in a company from using instant messenger, for example, or to prevent users from hitting a blacklist of websites, or prevent internal users from sending packets with IP addresses not in the right range for the local subdomain (to prevent viruses that try to spoof IPs from getting out).

      Just like one-way streets, a one-way firewall is really the exception, not the norm.

      --

      Don't label something "offtopic" unless you know the topic well enough to tell what's on topic.

    15. Re:Reverse firewalls? by DunbarTheInept · · Score: 1

      Actually, it comes from the term in a car - the firewall in a car is the thicker shielding at the front occupant's feet that separates the passenger compartment from the engine compartment - to retard fires that break out in the engine. IN that context it sort of does mean keeping the fire "out" - from the context of the passengers - by keeping the fire in - from the context of the engine compartment.

      Remember "out" and "in" swap meaning depending on where you're standing.

      --

      Don't label something "offtopic" unless you know the topic well enough to tell what's on topic.

    16. Re:Reverse firewalls? by will3477 · · Score: 1

      I didn't RTFA, but I know with our red hat enterprises boxes, I've started firewalling them on the local level. We're beind a departmental firewall, but this way if there's ever a worm for linux etc, its one more thing they have to by-pass. Is it possible, sure, but it took two lines to do and so I figured it was worth the effort. As I said in a comment above, our departmental firewall also allows all outgoing traffic unless it meets some conditions, part 25 not from our mail server being one of them.

  21. Egress firewalls.. by Anonymous Coward · · Score: 0

    Wow. "VeriSign's principal scientist" recommends "reverse firewalls". Nice, but I believe the term and thoughts about EGRESS firewalling has been around for a while. Reverse firewalling - Yesh. Get a clue. It wouldn't be that bad of a idea but 1. It won't be turned on by default 2. People won't turn it on 3. People won't get it.

  22. Noooo by joey.dale · · Score: 1, Interesting

    [tinfoil_hat_on]
    1. What if I where to have a good reason to send loads of e-mail?

    2. Whould these firewalls keep logs, and if so, who would have access to them.

    3. This sound alot like microsoft Trusted Computing project, bad idea
    [tinfoil_hat_off]

    -Joey

    1. Re:Noooo by Anonymous Coward · · Score: 0

      1. You disable the feature if you know what you're doing (ie running a mail server on purpose).

      2. It's your firewall/hardware device, so if there are logs (which there probably aren't), you have control over them.

      3. It does?

  23. Re:Not just for spam! by DAldredge · · Score: 3, Insightful

    For about 3.2 seconds till the UPNP enabled virus tells the UPNP enabled firewall that it is an authorized app...

  24. Am I missing the point here? by multiplexo · · Score: 1
    It seems to me that if you had properly configured firewalls built into all cable modems (at the very least having NAT and some packet inspection) that you could largely avoid the problem of having home PCs recruited into BotNets, turned into Zombies, et al. Also if Windows wasn't so bad from a security standpoint it would be a lot harder to infect/recruit Doze boxes. I keep my systems behind a firewall and keep my patches up to date and I do the same for my parents, so what is a reverse firewall going to do for us? And how long would it be before the hackers and script kiddies figure out how to game the reverse firewall rules and set up new phishing networks?

    --
    cheap labor conservatives - they want to keep you hungry enough to be thankful for minimum wage.
    1. Re:Am I missing the point here? by jimwelch · · Score: 0
      Yes, everyone complaining about the reverse part of this is missing the deeply hidden point. This new term will help joe six pack think about a new and improved way to use their firewall.

      Or to put it another way, moving info from the geek level to the everyday use level requires marketing. We may know and use this all the time, but with a little maketing buzz, joe six pack will want this too.

      Think of this as, the real use of marketing, educating the masses. How long has it been since the masses even knew a firewall was a computer thing and not something the fire marshall made the theater install to stop stage fires from killing the audience?

      --
      Never trust a man wearing a coat and tie!
  25. It was the obvious solution... by retodd · · Score: 1

    Reverse firewall polarity!

  26. accursed firewall... by i_will_frag_u_all · · Score: 1

    all mine does is prevent me from playing halo or warcraft... thats pretty mean, blocking the viruses so they stay in your computer!! "great, my computers infested with viruses, and we have to install a whole new operating system, but at least everyone else doesnt have it!!" comon, are you really going to think of that? how very american of them ever think of the fact that we would WANT to send lots of viru-*cough*emails out to the general public? oh, so im not normal now?!?!?!?

  27. Great Reverse Firewall for Mac OS X by toupsie · · Score: 4, Informative
    If you have got a Mac, there is a program called "Little Snitch" that is an excellent reverse firewall. While I am not worried as much about my Mac becoming a part of a botnet, it is amazing to see how often my installed software packages want to "phone home". I have even caught third party web advertisers wanting to open ports outside of 80 and 443.

    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.

    --
    Strange women lying in ponds distributing swords is no basis for a system of government.
    1. Re:Great Reverse Firewall for Mac OS X by Anonymous Coward · · Score: 0

      Is there a little snitch for Windows?

    2. Re:Great Reverse Firewall for Mac OS X by xenocide2 · · Score: 1

      Its been a number of years since I've tried it, but tiny/snort (I think that was the name of the combo) did a nice job of firewalling things, using MD5 signatures to make sure programs you'd already authorized had been given clearance. When set to a reasonable strength, it will alert you when any program not whitelisted is trying to open a connection.

      --
      I Browse at +4 Flamebait

      Open Source Sysadmin

    3. Re:Great Reverse Firewall for Mac OS X by gblues · · Score: 2, Informative

      Your software isn't necessarily "phoning home." It's probably trying to do something mundane, like print. In fact, if you do something stupid like block all network access, you'll kill your ability to print!

      As long as you make sure requests to "localhost" are allowed, you should be OK. :)

      Nathan

    4. Re:Great Reverse Firewall for Mac OS X by toupsie · · Score: 1

      Well when you see a DNS entry that isn't yours, you know its phoning home! Little Snitch tells you exactly where that little packets wants to travel.

      --
      Strange women lying in ponds distributing swords is no basis for a system of government.
  28. Just do it right first time. by solojony · · Score: 1

    If he means a firewall based on network level and not on content it will fail miserably in providing good service for power users, because the firewall won't be able to react to new traffic trends. Even the NAT can give you headheaches and has been around for a while.
    If he means a firewall with content scanning embedded, is certainly a security risk... for the user, I don't trust my router deciding what is right and not right for me thank you.

    What is needed here is a protocol for mail exchange designed with spam in mind, not zillions of dumb firewalls fighting their own users.

    Stop bloating networks with security fails at top protocolos, some guys should reread OSI stack fundamentals...

    1. Re:Just do it right first time. by skhisma · · Score: 1

      i agree, a new protocol designed to prevent spam is a lot less frightening than the possibility of my router, modem, etc 'thinking different' (ie, exhibiting very palladium-esque features). personally i think we should all be allowed to do what we wish with our hardware, even if that does give spammers the right to spam.

  29. Rate limit regular SMTP by Anonymous Coward · · Score: 0

    Regular people need to stop using port 25. It's time for users to switch to 587 or 465 for sending mail to their mail server. If you're running a mail server on purpose, then you can disable the rate limit.

  30. Just had to by manwithoneredsynth · · Score: 2, Funny

    Just the thing to protect the computers of... Reverse Vampires

  31. real solution by epyT-R · · Score: 1

    I know, instead of trying to band-aid the problem with a hack that does nothing but weaken the peer to peer concept of the net even more, how about getting microsoft the fix the crux of the problems in the first place?

  32. reverse firewall? what? by rritterson · · Score: 5, Interesting

    Reverse Firewall? As far as I know, a wall of fire would be flaming on both sides.

    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

    --
    -Ryan
    AUWYHSTOT (Acronyms are Useless When You Have to Spell Them Out Too)
    1. Re:reverse firewall? what? by hiekka · · Score: 2, Informative

      Hear, hear!

      Outbound firewall is still firewall, not "reverse firewall" or "anti firewall" or ... It's firewall. Actually we should call inbound-only firewalls half-firewalls to distinguish from real firewalls.

    2. Re:reverse firewall? what? by Anonymous Coward · · Score: 0

      A firewall isn't a wall of fire--it's a wall to STOP a fire. Like a fire door, only with fewer hinges. If your firewall is burning on both sides, it's failed.

    3. Re:reverse firewall? what? by mdfst13 · · Score: 3, Interesting

      "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."

      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.

    4. Re:reverse firewall? what? by Tony-A · · Score: 1

      Actually we should call inbound-only firewalls half-firewalls to distinguish from real firewalls.

      Finally, somebody gets it.

      A firewall has to be as much about protecting the internet from the big bad intranet if it is to stand any chance of being effective.

    5. Re:reverse firewall? what? by stridebird · · Score: 1
      ...a wall of fire???

      Thanks for that. 'Firewall' has just taken on a new meaning in my mind. I don't think I will be able to shake that for a long time. I was going to chide you on your reverse imagery, I was going to day it's a WALL TO STOP FIRE. But not no more it aint. Now it's a WALL OF FIRE. And I like it like that.

      But of course, now that I am thinking about it, it's not a wall at all. Metaphorically it's a secure door, a checkpoint, an underpaid security guard asleep at a desk in a grimey Brighton office after midnight (oh wait that's my place). It's an pinchpoint, whether it stops fire or is on fire.

    6. Re:reverse firewall? what? by evilviper · · Score: 1
      Reverse Firewall? As far as I know, a wall of fire would be flaming on both sides.

      Perhaps by "reverse firewall", he means a "water wall"?

      Really, the author wants consumer networking devices to have more capable firewalls.

      Actually, I have to think that most DSL/Cable-modems are already plenty capable. I know I telnet'ed to mine recently, and found that it's practically a full-featured router. You can configure advanced bridging options. You can tell it to send/recieve RIP routing table updates. You can also do IP routing/filtering as well. I suspect that nobody would need Linksys routers if the simple Cable/DSL modems had an easy web interface to them.

      The spam has to be getting in somehow, and that is something a normal firewall should be able to stop.

      Not true. Unless every single port (incomming and outgoing) is blocked, a connection can still get through.

      Backdoor programs don't just open a port... No. They typically connect to some IRC channel, and await commands. That means, it only needs one outgoing port to be open on the firewall, and it's got a usable connection. Firewalls just can't possibly stop that.

      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.

      Firewalls are good protection, but not that good. Even if you have a perfect firewall, without a single open port, you've still got issues of every other machine on the network needing to be trusted. If you ever plug your notebook into another network, you're in trouble, and your firewall can't help. Same goes for allowing other people to plug their notebooks into your network. All it takes is one infected machine to get in around your firewall.

      Of course, a notebook (or removable hard drive) isn't necessary either. All it takes is a single file with a worm payload to be run by one person. Antivirus is also a very good thing, but it can't be perfect, and it needs to be.

      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

      No, it's likely just to be another feature on the next network device you buy. No training, no convincing you to go out and buy something. Nothing.

      I see this as likely to generate many headaches with not much benefit

      I see the opposite... It's likely to deliver many benefits, with not many headaches. Only those who are running mailing lists need to worry.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
    7. Re:reverse firewall? what? by jseitz · · Score: 1

      Its called egress filtering. Its been around on firewalls and routers since the beginning, check it out. What would be great is if people actually started using it;-)

    8. Re:reverse firewall? what? by Anonymous Coward · · Score: 0

      Hey and you know whats funny? Most big cablemodem and DSL ISP's *are already doing* exactly that - blocking outbound port 25. And more are realizing its a good idea every day.

      Most end users needing to submit mail for outbound relay can use port 587 as more and most hosting companies recognize the need for that.

      Open relays were slowly put mostly out of style, soon too will trojaned and 'open proxy by default' wincrap machines sitting on broadband connections. The big question is what will the spammers do next? Get a real job? - we can only hope.

      So whats news here, exactly?

    9. Re:reverse firewall? what? by HermanAB · · Score: 1
      "home PCs aren't spam-generators, they are spam relays."

      Oh yeah? I had two internet accounts shut down today (clients of Telus and Hotmail) because the PCs of two Windows users were generating virus spam and one of my clients was an unfortunate receiver of a constant stream of viruses.

      So yes, some PCs may be spam relays, but others are generators - after they became sick.

      These two ISPs are very good at this - send them a friendly e-mail, asking to please shut a spammer down, with some proof attached and within an hour, the problem has gone away.

      --
      Oh well, what the hell...
  33. I undrestand... by altaic · · Score: 2, Insightful

    that spam is a difficult problem to solve, but that is the most idiotic idea I think I've ever encountered. That's like making it difficult to do encryption to prevent terrorists from communicating safely. Granted, "normal" people's computers are a vessel for spammers, but it's asinine to limit normal people's hardware. Why not fix the problem at the source and work on making consumer's computers secure? The day I find out my DSL modem is blocking ports or something like that is the day I wreck the thing while trying to fix it. I mean, really.

  34. ZoneAlarm software firewall already checks... by Futurepower(R) · · Score: 1


    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.

  35. Worried about outgoing Spam? by lecithin · · Score: 2, Funny

    Just Put a Condom on it.

    --
    It could be worse, it could be Monday.
    1. Re:Worried about outgoing Spam? by Anonymous Coward · · Score: 0

      that joke is so bad i think you should put a condom on your enter key to prevent any more escaping.

    2. Re:Worried about outgoing Spam? by desplesda · · Score: 1

      Spam? Don't you mean a packet flood?

  36. Virus could disable software firewall by erice · · Score: 4, Interesting

    The virus is already on the inside with "root". It would be trivial for the virus to simply disable the firewall before spewing.

    No, for a "reverse" firewall to make any sense, the firewall must be on a different machine.

    1. Re:Virus could disable software firewall by Graff · · Score: 1
      The virus is already on the inside with "root". It would be trivial for the virus to simply disable the firewall before spewing.

      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, sure the virus could infect your own personal account but since the firewall runs under root the virus can't disable it. Yes, you still won't stop the idiots who blindly authenticate anything that pops up but at least this is another barrier to stop the spread of a virus.
    2. Re:Virus could disable software firewall by Aneurysm9 · · Score: 1

      So the virus initially acts as a keylogger then, once the user has typed in the password for something else, the virus forks off a process to kill the firewall and goes to work.

      --
      There was Cowboy Neal at the wheel of a bus to never-ever land.
    3. Re:Virus could disable software firewall by hdw · · Score: 2, Interesting

      Well yes and no.

      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.

      The 'hardware' firewall (on a dedicated box, router or modem) is of course much safer but it has several limitations.
      The biggest is the challenge to write and maintain the ruleset.

      I'm using the hardware version, blocking all outgoing traffic except from a dedicated proxy and configuring the PCs behind to use the proxies for mail and web.
      But my kids aren't old enough to want to play multiplayer games and other stuff that most people sooner or later want to.
      And it also requires me to maintain the filterlist in the proxy.

      So, no, there's no simple fix I'm afraid.

      (Yes, I assume that everyone blocks incoming traffic with a NAT box or such.)

      // hdw

      --
      Executive Pope (small) Kallisti Engineering
    4. Re:Virus could disable software firewall by Laebshade · · Score: 1
      The virus is already on the inside with "root". It would be trivial for the virus to simply disable the firewall before spewing.

      No, for a "reverse" firewall to make any sense, the firewall must be on a different machine.


      Which is why in the FAS (F'ing Article Summary), He says reverse firewalls should be embedded in every cable modem and wireless access point for home users. Notice that he never says in the FAS that it should be on the same PC. Stop whoring for karma.
    5. Re:Virus could disable software firewall by Just+Some+Guy · · Score: 1
      That's not true on every OS. From FreeBSD's init(8) man page:
      The kernel runs with five different levels of security. Any super-user process can raise the security level, but no process can lower it. The security levels are: -1 Permanently insecure mode - always run the system in level 0 mode. This is the default initial value. 0 Insecure mode - immutable and append-only flags may be turned off. All devices may be read or written subject to their permissions. 1 Secure mode - the system immutable and system append-only flags may not be turned off; disks for mounted file systems, /dev/mem, /dev/kmem and /dev/io (if your platform has it) may not be opened for writing; kernel modules (see kld(4)) may not be loaded or unloaded. 2 Highly secure mode - same as secure mode, plus disks may not be opened for writing (except by mount(2)) whether mounted or not. This level precludes tampering with file systems by unmounting them, but also inhibits running newfs(8) while the system is multiuser.

      In addition, kernel time changes are restricted to less than or equal to one second. Attempts to change the time by more than this will log the message ``Time adjustment clamped to +1 second''.

      3 Network secure mode - same as highly secure mode, plus IP packet filter rules (see ipfw(8) and ipfirewall(4)) cannot be changed and dummynet(4) configuration cannot be adjusted.

      I pretty much always run production servers in securelevel three. If you set the immutable attribute on the scripts that set the securelevel at login and your firewall setup so that a hacker with root privileges can't modify them, then nothing short of a kernel flaw will let them modify your firewall. The caveat is that unless you're at the console, forget modifying your firewall ruleset. However, some of my configs have been running for years without modification (deny all by default, allow incoming TCP 22, 25 and 80, allow outgoing keep state) so that's not necessarily a problem in practice.

      So, tune your firewall and set your securelevel. If your OS doesn't provide one, then convince someone to make it happen or sit down and write it yourself. I wouldn't rely on it as the sole means of defense (because kernel bugs aren't unheard of), but it certainly eliminates a huge number of security issues.

      --
      Dewey, what part of this looks like authorities should be involved?
    6. Re:Virus could disable software firewall by _Lint_ · · Score: 1

      Acting as a keylogger would require it to already have root permissions

    7. Re:Virus could disable software firewall by GregChant · · Score: 1
      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.

      Try opening up Terminal and running the following command:

      # sudo sh

      It's not that hard to gain root in Mac OS X, even with superuser disabled in NetInfo.

    8. Re:Virus could disable software firewall by Anonymous Coward · · Score: 0

      i dunno exactly about osx but i know it is trivial if you have the account of someone who uses su in the shell to get the root pass

      just make them a private binary dir add it to thier path in the bash profile and put your fake su there

    9. Re:Virus could disable software firewall by Graff · · Score: 1
      Try opening up Terminal and running the following command:
      # sudo sh

      It's not that hard to gain root in Mac OS X, even with superuser disabled in NetInfo.

      Right but even then you are asked for a password before you can open up a root shell. The point is that the password is yet another roadblock to a virus gaining root on your system. Of course there is no 100% sure way to stop all attempts at infiltrating a system but every roadblock helps!

      For those that are truly paranoid I'd recommend running your main account with no sudo privileges at all. Basically create two accounts, an administrator account with the ability to sudo and do all the other stuff that an admin needs to do and a regular joe account with no special privileges at all.

      Use the admin account for installing, updating, and fixing stuff and use the average joe account for your normal day-to-day e-mail, web, spreadsheets, etc. That way even if a virus did infect your machine it would most likely be in the average joe account you use all the time and where the virus can't do squat since that user can't do anything to the system.

      With Mac OS X's Fast User Switching it is pretty easy to swap between these accounts at will and still maintain privilege separation.
  37. Re:Not just for spam! by flyneye · · Score: 1

    until of course a cablemodem (or whatever the llawerif is embedded in)is reverse engineered and a hack found and described for the world to see.even if most couldnt do the hack,some would.
    this is more nonsense.
    software will always be hackable.(after all its just commands to harness the hardware)
    hardware will always be hackable(it would take a meta man to create hardware unhackable by man)
    GTF over any notion that computers on networks will EVER be secure.Gawd if you could just show legislators that simple logic we could quit wasting valuable tax dollars in this country.
    we make machines to work for us.
    we have to talk to the machines in a language they understand.
    The language can conduct nice business with the comp.
    The language can conduct nastiness.
    we make machines that block nastiness.
    we move this circuit.shunt.rewire.reprogram the cmos or in the case of nvidia just move this resistor from here-> * to here ->* and save a buncha mon$y.
    so in reply:no it wont stop virii and worms as well.

    --
    *Repent!Quit Your Job!Slack Off!The World Ends Tomorrow and You May Die!
  38. How much will it be useful ? by abhinavmodi · · Score: 2, Insightful

    While it is true that the reverse firewall will stop too much traffic from a "home" computer, there are some aspects of this which raise interesting questions: 1. How much is "too much" ? How is this decided? 2. What abt proxies to circumvent this? 3. The majority of spam, generated is probably not from a home computer. 4. Modern firewalls can be configured for outbound filtering as well. How radically will the propsed scheme be different from this? Correct me if i am wrong in any of the assumptions above. If we are achieving too less while applying too much effort, the low of economy wouldnt justify this.

    1. Re:How much will it be useful ? by Vitus+Wagner · · Score: 1

      1. How much is "too much" ? How is this decided?


      I've invented following scheme for our appartment block network (about 100 users connected via ethernet to my server, which works as gateway/firewall)


      1. By default, outgoing connections to port 25 are blocked, except to local mail server
      2. There is a web page where user can enter name of SMTP server he wants to be allowed to connect to. This page requires user password.
      3. Local mail server accepts only certain amount of messages per day Say, 100 or 200, which is more than enough for user who have to type them down,
        but very few for spambot
      4. There is also web page where user can press a button "allow me another 200 messages today". It is also password protected.
      5. All rules with links to control pages are published on local web site (unaccessable from outside) and given to user in printed form.


  39. A DRM by any other name... by noidentity · · Score: 1

    This sounds similar to the reasoning used by the RIAA and others use to conclude that DRM is a good thing. Copyright fair use turns into a permission model. At least in this case the problem is one of real theft of resources.

    1. Re:A DRM by any other name... by Anonymous Coward · · Score: 0

      What the hell are you talking about? Are you stoned out of your fucking mind? This shit has nothing to do with goddamn DRM, you tool, any more or less than a normal firewall (which, as has been pointed out, is what the article's author was trying to talk about in the first place) does. For fucks sake, sober up before you post again.

  40. floods of e-mail by weenis · · Score: 2, Interesting

    speaking of "floods of e-mail," one of the most entertaining things is to take my original copy of win2k without any service packs,
    do a fresh install,
    plug in without any firewall,
    and watch how fast the damn thing tries to send out mass mailings :-)

  41. Re:Not just for spam! by Anonymous Coward · · Score: 0

    Um. I highly doubt a reverse firewall would be UPnP enabled.

    It wouldn't add functionality. It would add a glaring security flaw. Let me think about that.

  42. Simpler by Uhlek · · Score: 1

    ip access-list extended EGRESS_FILTER
    permit tcp any eq smtp
    deny tcp any any eq smtp
    permit ip any any
    interface
    access-group EGRESS_FILTER out

    Fixed!

    1. Re:Simpler by Uhlek · · Score: 1

      Stupid HTML

      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!

    2. Re:Simpler by Technician · · Score: 1

      permit tcp any eq smtp
      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.

      --
      The truth shall set you free!
    3. Re:Simpler by Uhlek · · Score: 1

      That's a router ACL. Perhaps I was a bit too vague, but my intention with that particular post was that "reverse firewalls" aren't what's needed at every house. Rather, very simple egress filtering as the responsibility of the ISP could mitigate a great deal of spam, and prevent spoofed packets (commonly used in DDoS attacks) from leaving the network.

  43. There seem to be alot of misconceptions. by Artega+VH · · Score: 2, Insightful

    This would limit the rate of outgoing emails (or presumably anything else) to a limit that most people wouldn't hit in normal use. If implemented this limit would be configurable in the "firewall" so that users who know what they are doing can alter it.

    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.

    --
    groklaw, wired and slashdot. The holy trinity of work based time wasting.
  44. Re:Not just for spam! by DAldredge · · Score: 1

    Please check and see what % of currently shipping sub 100 USD firewalls/NAT devices are UPNP enabled. You might be shocked.

  45. Welcome 1984 by novalogic · · Score: 1

    Wonderful, Just what I need, yet another wing of the cable company telling me what I can and can't do. And just how do you propose monitoring this system? What if I run a mailing list or support group from home, why would I want to pay another $20 to send out 50 emails to poeople, and at what point would this firewall cut me off?

    What if a new game comes out which makes a odd form of connection for multi-play. Or perhaps my software dose something thats not viewed as "normal" by Joe Schmoe, M.C.S.E.

    And what could I do about it?

    Here is the problem.

    You have a flood of water 15 foot high coming for your house.

    So lets paint the basement with some water-sealant.

    There are bigger problems to fix.

    Complex things lead to complex problems.

    --
    --
    1. Re:Welcome 1984 by Artega+VH · · Score: 1

      "And just how do you propose monitoring this system?"

      Why does it need monitoring?

      "What if I run a mailing list or support group from home, why would I want to pay another $20 to send out 50 emails to poeople, and at what point would this firewall cut me off?"

      Presumably since the firewall is in your cable modem you can configure it how you like. If you can't THEN there would be problems.. Lets complain about them then instead of trying to shoot down what could be a good idea.

      "What if a new game comes out which makes a odd form of connection for multi-play. Or perhaps my software dose something thats not viewed as "normal" by Joe Schmoe, M.C.S.E.

      And what could I do about it?"

      Refer to my previous answer? This wouldn't be controlled by the ISP's just recommended by them. Most users wouldn't be affected, and those that were can probably figure out how to configure the thing just like a standard router?

      --
      groklaw, wired and slashdot. The holy trinity of work based time wasting.
  46. security model by blazen1 · · Score: 2, Funny

    However, the security model in 802.11 may not be enough to prevent an attacker to get access to the intranet.

    you're kidding..

  47. The downside of free speech. by _aa_ · · Score: 1

    Obviously this is a practical concept, but I'm hesitant. I personally feel that spam blocking is the burden of the receiver, just by the nature of the email protocol. I hate obtrusive advertising as much as the next guy, but I do recognize it as a form of speech. And no matter how inane, idiotic, and offensive it may be, I feel it is protected under the 1st amendment.

    I recognize that spam is an inconviniece for end recipients, and a serious waste of resources for networks. Regardless, i feel that a reverse firewall process as described sets a dangerous precedent. Many might concede to blocking mass emails, but would they also concede to blocking of private web servers? Would the blocking of P2P be acceptable?

    I've encountered numerous mail servers that are rejecting emails sent from cable modem and DSL users. I think that that is a significantly more responsible solution, even though it may not be as efficient. I feel as a paying customer of my broadband provider, I should not be prevented from emailing whoever I want, in whatever manner I want, though I cannot force any mail server to actually receive my emails.

    1. Re:The downside of free speech. by geminidomino · · Score: 2, Insightful

      I personally feel that spam blocking is the burden of the receiver, just by the nature of the email protocol.

      All well and good, until /. runs another story about SPEWS blocking yet another idiot site who decided to save money by hosting at a spamhaus. THEN nobody has the right to BLOCK spam either, so they can get their email from BBR.

      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. Hint: If I tell you to STFU or get out of my store, I'm not violating your first amendment rights, because I'm not the government. Same goes for my email servers. 1st amendment Freedom of Speech/Assembly/etc... protection applies to the government.

    2. Re:The downside of free speech. by _aa_ · · Score: 1

      I don't follow your counter-point.

      I think you're trying to suggest that it's legal for non-governmental institutions to infringe upon one's rights of free speech. Which is certainly not true. But regardless, the real question is weather email is considered of a medium of speech. Obviously email is not a right, it's a purchased privaledge. But so are most mediums of speech. Printing presses, radio transmitters, and ISPs are not free of financial cost. But my right to publish and broadcast my opinions and anything else i want, are (or should be) protected. Why not email?

      Noone really complains about advertising on commercial radio and television broadcasts. I really don't see a significant difference between television advertising and email spam. If anything, for me, email spam is less frustrating, and certainly less time consuming. Any spam I encounter can be simply overlooked, and I can move on to the next message in my inbox. With televison or radio, other than changing channels, I have no control over the advertising I'm exposed to.

      You as an individual can tell me to STFU all you want, but cannot actually take any action to prevent me from excercising my right to speak. If I am unwelcome at your store, you can have me arrested for trespassing, but you cannot infringe on my right to protest your store and speak about it. The loose metaphor being that you can have me arrested for sending you pornography, or violating a no-call-list, or damaging your computer; but you should not be allowed to prevent me from sending my emails.

    3. Re:The downside of free speech. by Anonymous Coward · · Score: 0

      I think you're trying to suggest that it's legal for non-governmental institutions to infringe upon one's rights of free speech. Which is certainly not true.

      But it is. The Constitution is a document that sets out limits on what the government can do. It says absolutely nothing about non-governmental organizations. The Bill of Rights does not give you positive rights (such as freedom of speech), it gives you negative rights (such as the right not to be censored by the government). It's a little semantical, but that's the reality of it.

    4. Re:The downside of free speech. by Artega+VH · · Score: 1

      First, free speech isn't a right in all countries.

      Second, why should having the right to speak mean I should provide you with the pulpit? I should have the right to listen, or not..

      --
      groklaw, wired and slashdot. The holy trinity of work based time wasting.
    5. Re:The downside of free speech. by _aa_ · · Score: 1

      Well, semantics aside. Non-governmental institutions hold no jurisdiction over public areas. Unless you're physically on private property, the government dictates the rules. In public spaces, I retain the right to free speech. Presuming the internet as a whole is a public place, as I'm sure few will contest, the right to speak should be protected for all individuals, or at least US Citizens.

      Besides, you'll encounter few organizations that are wholly unaffiliated with the government and can therefore bypass such rules as Equal Oppritunity laws. By their affiliation with the government, be it through grants, contracting, or SEC participation, they are acting on behalf of the government and must adhere to and uphold the laws.

    6. Re:The downside of free speech. by _aa_ · · Score: 1

      No, it isn't, but perhaps it should be.

      Well, in this particular case, if "You" are my ISP, I'm paying for the pulpit. I pay for a connection to the internet, and what I choose to do with it should be my business.

      If by "You" you mean the average email user, I don't believe that you are providing spammers with a pulpit. Take for example the sidewalks of Las Vegas, where hundreds of people are paid to, rather forcefully, hand out flyers for adult entertainment. However persuasive they try to be to get you to take their flyer, they are forbidden to force it upon you. I beleive that email spam is very similar. Because of the automation of our email clients, we automatically download everything in our mailboxes to our inboxes. Our email clients accept this spam on our behalf. If you wish to manually go through your messages one by one, you could easily reject any email you wish without ever viewing it. But because of the volume and difficulty of a manual process like that, we forego our means of individually filtering our email and blindly entrust our email clients to accept everything. And it's this blind acceptance that spammers exploit. You certainly have the right to accept or reject any email that gets sent to you before you download it. It's this right that you waive to some extent by using a non-discerning email client.

    7. Re:The downside of free speech. by geminidomino · · Score: 1

      I think you're trying to suggest that it's legal for non-governmental institutions to infringe upon one's rights of free speech. Which is certainly not true. But regardless, the real question is weather email is considered of a medium of speech. Obviously email is not a right, it's a purchased privaledge. But so are most mediums of speech. Printing presses, radio transmitters, and ISPs are not free of financial cost. But my right to publish and broadcast my opinions and anything else i want, are (or should be) protected. Why not email?

      Short Answer: AOL V. CyberPromotions.

      Longer Answer: Yes, if you own the press, you can print out all the "free speech" you want. I fail to see how your rights to "broadcast" are guaranteed. You can NOT force me to distribute it for you in my store. You can't come into my parking lot and put pamphlets on my customers' cars if I tell you not to. You cannot force others to listen to your "free speech", nor to supply you with the megaphone. Your right to free speech ends at someone else's right to not listen.

      Noone really complains about advertising on commercial radio and television broadcasts. I really don't see a significant difference between television advertising and email spam.

      The largest difference is that With TV/Radio advertisements, the RECIPIENT does not pay for it. With spam, he/she does($3/month for AOL users, e.g.).

      You as an individual can tell me to STFU all you want, but cannot actually take any action to prevent me from excercising my right to speak. If I am unwelcome at your store, you can have me arrested for trespassing, but you cannot infringe on my right to protest your store and speak about it. The loose metaphor being that you can have me arrested for sending you pornography, or violating a no-call-list, or damaging your computer; but you should not be allowed to prevent me from sending my emails.

      The network does not belong to you, it belongs to your ISP. You rent it from them. If they choose to keep you from spamming the hell out of the known universe (more power to them!), then get a new ISP, or get yourself a T-1 and an IP delegation. Your right to free speech does NOT supercede their right to determine how THEIR property will be used.

    8. Re:The downside of free speech. by Artega+VH · · Score: 1

      I'd be perfectly happy to lock up the pamphlet guys and girls along with the spammers.. they all piss me off :p

      --
      groklaw, wired and slashdot. The holy trinity of work based time wasting.
    9. Re:The downside of free speech. by Anonymous Coward · · Score: 0

      The network does not belong to you, it belongs to your ISP. You rent it from them.

      So the ISPs want it both ways, they want the freedom of washing their hands by saying we are just common carriers - we don't know what they are sending back and forth, therefore we are not liable and at the same time they want to say we can monitor your traffic and whack you for what kind of and the quantity of traffic you are sending. If the assholes who run the ISPs want me to "rent" it, then they should allocate a prominently visible and clearly stated cap of X GiB/month and let me decide what traffic over what ports I want to use those GiBs of traffic for, if not they aren't common carriers. That is the deal that was made long ago with the telo (AT&T), you build a tube, you let people use buy transit through the tube and you don't peek into the tube - we the government, won't let people sue you for what goes through the tube. ISPs want to break the deal because it is convenient for them.

      Fuck the ISPs for being hypocrites and fuck the self important assholes who work for them and want to distain the customers under the guise of fighting the good fight, the morally justified crusade.

    10. Re:The downside of free speech. by _aa_ · · Score: 1

      Your store, and your parking lot are PRIVATE PROPERTY, upon which, you are right, you're the boss on your property. The sidewalk outside your store, however, is public. This is why abortion protests occur on the sidewalk in front of the clinic, and not in the operating room.

      I'm not aware of a "Right to Ignorance" but I don't disagree that as a speaker in any medium, I cannot force you to hear it. Regardless, I have the right to speak it anyway. If I am in a public place, I have the right to assemble, speak, and protest until I'm blue in the face, at my own expense. Broadcast mediums are becoming more and more restricted, to my dismay. I'm not certain that the internet technically is defined as a broadcast medium.

      You're absolutly right. I cannot tell my ISP what to do with THEIR PROPERTY. But the cable modem is NOT THEIR PROPERTY. It's MY PROPERTY. I paid for it. I overpaid for it, as a matter of fact.

      Imagine there's a public park on an island. In order to get to it, you have to either buy a boat yourself, or rent one from someone else. What right does the renter have to demand that you can use their boat to get to the island, but once you're on the island, you cannot goto a specific part of it. It's a public island. The internet is a public place.

      Again, I'm not saying that this method of blocking spam is neccesarily a bad idea. Instead, I think it sets a bad precedent, and as a cable modem user, I'm hesitant to yield my present right to send mass emails from my cable modem.

    11. Re:The downside of free speech. by Anonymous Coward · · Score: 0

      "Presuming the internet as a whole is a public place"

      Bzzt. *There* is your mistake. The Internet is not a 'public place' - it is a very large number of privately owned places which have agreed to "Inter" connect using a standard communication protocol, and to follow certain rules and conventions to prevent any one of them (or a customer of any one of them) from using the others' resources without their permission.

      You have the right to *send* all the email you want - you do *NOT* have a right to demand that any other privately owned portion of the "Inter" network accept it.

    12. Re:The downside of free speech. by Anonymous Coward · · Score: 0

      Yes, you pay *your* ISP. Unless he has a so-called 'pink contract', a spammer does not pay his ISP to allow him to abuse other ISP's customers, nor does he pay his intended *recipients* ISP for the right to use their customers mailbox as a billboard.

      In this 'Inter' connection agreement, it is expected that one ISP will take steps to prevent its customers from abusing other ISP's customers, including terminating the abusers access, if required. If an ISP does not do that, then the other ISP's often decide they dont want to receive any email from any customer of the ISP harboring the spammer.

      'filtering' between the mailserver and the email client is too late - the spam has already wasted bandwidth, already occupied disk quota (and maybe even by doing so prevented desired email from being received). The time to reject mail is at the SMTP session, with a swift '550' - this also gains the side affect that should a person sending a 'nonspam' email is rejected as well, *their* ISP should return the mail to their mailbox as rejected, and they actually *know* it didnt get through, as opposed to having it silently dropped by some filter - notice the subtle difference between the *recipients* isp accepting it, and then returning it after the fact to the claimed (almost always fake or forged) 'sender' address, which only causes more problems.

  48. Been there, done that.... by jclagreca · · Score: 1

    This sounds like a really dumb idea to me (It might be time to shit can their principal scientist) Not only will it be easy to get around after someone figures out how it works, but it sounds like something that should be done more centrally, maybe at the ISP level instead of each individual cable modem.

    Actually if this "scientist" did his research he would have found it has already been done by ISP's. Cox.net blocks outgoing port 25 so you are forced to use their email servers. I'm sure they have something in place to prevent an outflow of spam.

    ISP's can block whatever they want because all traffic must flow through them. Therefore this is an old idea, that may just need to be implemented in more places.

  49. Reverse Firewalls are already very popular by Anonymous Coward · · Score: 0

    ..in Japan.

  50. Re:Not just for spam! by Anonymous Coward · · Score: 1, Informative

    No. See. There's a difference.

    On those routers, it provides functionality. It allows software the ability to portmap itself to allow functionality as a server. For P2P, for instance, that's a boon.

    On a firewall specifically designed to block outgoing attacks, that it a worthless function. It would, however, allow malicious programs free access, making it worthless.

    If you can't see the difference, you're hopeless.

  51. I liked this idea better... by Anonymous Coward · · Score: 0

    ..when it was called "egress filtering", done at the ISP's hardware.

    This guy shouldn't even get the time of day on Slashdot.. what's next:

    "To filter spam we should use DNS to publish the IP addresses of spamming hosts. I call this 'DNS-based Naughty Lists' or 'DNSNL'.. no one ever thought of this before.. I AM TEH GEN1US!!!!!!!!!!!!11111111111"

  52. Re:Ha! Beat you too it! by double_plus_ungod · · Score: 1

    so how did you post to slashdot?

  53. Re:Not just for spam! by Savet+Hegar · · Score: 1

    Better yet, make the thing totally configurable so you can block all of the spyware inherently loaded into Windows. Not only can you lock down all incoming ports, but lock down all outgiong ports. Of course....iptables already does this. Just one more way they need 3rd party hardware/software to catch up to what Linux is already doing.

    --
    Mod points are pointless when you browse at -1.
  54. Yeah but by Lord+Kano · · Score: 1

    how I am I supposed to crash Half Life servers when some admin is being a real dick?

    LK

    --
    "Hi. This is my friend, Jack Shit, and you don't know him." - Lord Kano
  55. If we can't get people to run Anti-Virus Software by Art+Pollard · · Score: 1

    If we can't get people to run anti-virus software to scan their systems and remove viruses, how can we hope people will run a reverse firewall?

    Installing anti-virus software is not too difficult but apparently too difficult for a significant number of users. If we can't get people to install anti-virus software to keep the viruses from destroying their hard drive, how can we hope they'll install a firewall to stop their machine from sending spam?

    -Art

  56. Stupid idea by losttoy · · Score: 1

    Anyone who takes control of your PC will also use it to punch open holes through your firewall to allow spam to go out through the modem/router/whatever!!

    1. Re:Stupid idea by Artega+VH · · Score: 1

      I swear the average IQ of a slashdotter must be amazingly low.. Did you somehow manage to read the summary, not the article and NONE of the comments?

      It stops people from sending alot of emails.. not one.. you know this spam thing.. its where people send alot of emails at once.. whereas most people don't do that...

      --
      groklaw, wired and slashdot. The holy trinity of work based time wasting.
    2. Re:Stupid idea by Anonymous Coward · · Score: 0

      Real firewalls dont run on the same PC they are protecting. Real firewalls are a seperate hardware device (or another PC, running an OS that isnt a toy) and the PC that the firewall is protecting (and protecting the Internet from if that is the case) can have all the viruses it wants without having any affect whatsoever on the firewalls ability to continue doing its job unmolested.

      The software 'firewalls' that you are thinking of are junk. Real ones are made by (eg) D-Link, Linksys, Netgear, etc..

  57. Obligitory form-letter post by AnotherBlackHat · · Score: 0

    Your company advocates a

    (x) technical ( ) legislative ( ) market-based ( ) vigilante

    approach to fighting spam. Your idea will not work. Here is why it won't work. One or more of the following may apply to your particular idea, and it may have other flaws which used to vary from state to state before a bad federal law was passed.)

    ( ) Spammers can easily use it to harvest email addresses
    ( ) Mailing lists and other legitimate email uses would be affected
    ( ) No one will be able to find the guy or collect the money
    ( ) It is defenseless against brute force attacks
    ( ) It will stop spam for two weeks and then we'll be stuck with it
    (x) Users of email will not put up with it
    ( ) Microsoft will not put up with it
    ( ) The police will not put up with it
    ( ) Requires too much cooperation from spammers
    (x) Requires immediate total cooperation from everybody at once
    ( ) Many email users cannot afford to lose business or alienate potential
    employers
    ( ) Spammers don't care about invalid addresses in their lists
    ( ) Anyone could anonymously destroy anyone else's career or business

    Specifically, your plan fails to account for

    ( ) Laws expressly prohibiting it
    (x) Lack of centrally controlling authority for email
    (x) Open relays in foreign countries
    ( ) Ease of searching tiny alphanumeric address space of all email addresses
    ( ) Asshats
    ( ) Jurisdictional problems
    ( ) Unpopularity of weird new taxes
    ( ) Public reluctance to accept weird new forms of money
    ( ) Huge existing software investment in SMTP
    ( ) Susceptibility of protocols other than SMTP to attack
    ( ) Willingness of users to install OS patches received by email
    ( ) Armies of worm riddled broadband-connected Windows boxes
    ( ) Eternal arms race involved in all filtering approaches
    ( ) Extreme profitability of spam
    ( ) Joe jobs and/or identity theft
    ( ) Technically illiterate politicians
    ( ) Extreme stupidity on the part of people who do business with spammers
    ( ) Extreme stupidity on the part of people who do business with Microsoft
    ( ) Extreme stupidity on the part of people who do business with Yahoo
    ( ) Dishonesty on the part of spammers themselves
    ( ) Bandwidth costs that are unaffected by client filtering
    ( ) Outlook

    and the following philosophical objections may also apply:

    (x) Ideas similar to yours are easy to come up with, yet none have ever been shown practical
    ( ) Any scheme based on opt-out is unacceptable
    ( ) SMTP headers should not be the subject of legislation
    ( ) Blacklists suck
    ( ) Whitelists suck
    ( ) We should be able to talk about Viagra without being censored
    ( ) Countermeasures should not involve wire fraud or credit card fraud
    (x) Countermeasures should not involve sabotage of public networks
    (x) Countermeasures must work if phased in gradually
    ( ) Sending email should be free
    ( ) Why should we have to trust you and your servers?
    ( ) Incompatiblity with open source or open source licenses
    ( ) Feel-good measures do nothing to solve the problem
    ( ) Temporary/one-time email addresses are cumbersome
    ( ) I don't want the government reading my email
    ( ) Killing them that way is not slow and painful enough

    Furthermore, this is what I think about you:

    ( ) Sorry dude, but I don't think it would work.
    (x) This is a stupid idea, and you're a stupid company for suggesting it.
    ( ) Nice try, assh0le! I'm going to find out where you live and burnyour house down!

    1. Re:Obligitory form-letter post by bhima · · Score: 1
      I can't believe the spam discussion has degenerated to the point were this sort form comment thing is so correct!

      Where the hell has VeriSign been? Arrogance to the point of ignorance!

      --
      Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
    2. Re:Obligitory form-letter post by Artega+VH · · Score: 4, Informative

      Did you select from that "form" randomly or did you want to actually make an insighful point?

      (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.

      --
      groklaw, wired and slashdot. The holy trinity of work based time wasting.
    3. Re:Obligitory form-letter post by Shirotae · · Score: 1

      I find it amusing that VeriSign's chief scientist has the initials PHB.

      I read the article and found it to have very little substantial content. It makes some vague suggestions in areas where the devil is in the detail. It ends up with a sales pitch for a VeriSign service - a very bad sign for any article that purports to be technical.

    4. Re:Obligitory form-letter post by bhima · · Score: 1
      PHB!

      No Wonder!

      --
      Nothing in the world is more dangerous than sincere ignorance and conscientious stupidity.
    5. Re:Obligitory form-letter post by Anonymous Coward · · Score: 0

      Well, naturally we'd *all* be safer if we had to obtain Verisign secure certificates in order for our mail servers to talk to other mail servers :-P

    6. Re:Obligitory form-letter post by anti-NAT · · Score: 1

      (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)

      I think you may be over estimating people if you think firewalls are practical for the majority of users on the Internet. They haven't worked out how to keep their systems patched yet, (using basic, automated patch installers) and you think they understand UDP/TCP/IP/ICMP well enough to configure a firewall properly ?

      The "so-called" advantage of NAT is that on a home router, you plug it in, switch it on an you are magically "secure". Sadly, that's all people want to do, and that is usually what they do. They don't want to learn what this NAT thing is, and they don't want to have to configure it. Same with a firewall. All they want is access to the Internet, and if they can view a web page, they consider they've achieved that, and don't want to spend any more effort on doing it "properly".

      We might be able to do something like "reverse firewalls" once the majority of the VCRs in the world have stopped blinking "12:00". That would show a dramatic improvement in the technical competence of the general public.

      I'd recommend not holding your breath ...

      --
      The Internet's nature is peer to peer - 20050301_cs_profs.pdf
    7. Re:Obligitory form-letter post by Anonymous Coward · · Score: 0


      once the majority of the VCRs in the world have stopped blinking "12:00".


      Cool how do you make your vcr do that? Mine has the right time. Is it an easter egg? :)

    8. Re:Obligitory form-letter post by AnotherBlackHat · · Score: 1

      (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..


      Some would, some wouldn't.
      Check other posts to see what some people think of the idea of "restricting their internet service"


      (x) Requires immediate total cooperation from everybody at once
      No. Every user that gets one of these things helps.


      Just like every open relay closed cut down on the amount of spam?
      Lots of ISPs block port 25 completely.
      Have you noticed a reduction in spam as a result?


      (x) Lack of centrally controlling authority for email
      Huh?


      A bit of a strech perhaps, but consider the problem of people who refuse to install one of the things.
      How do you punish them for that?


      (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)


      I don't.
      But like many others I have no objection to other people installing them.
      It's when they insist that I buy one that I consider it a problem.


      (x) Countermeasures should not involve sabotage of public networks
      (x) Countermeasures must work if phased in gradually
      Pardon?


      This is an impediment to the traffic flow (sabatoge) and it won't have any real effect on spam unless it gets enourmously large scale adoption, and even then it's not clear that it will work as theorized.
      Large scale adoption is necessary just to test the theory.


      (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.


      Go ahead and laugh, I don't mind.

      -- less is better
  58. ISP SMTP Servers - Re:Off by default by billstewart · · Score: 1
    A lot of ISPs force you to use their server for outbound mail; it's one of the things that really annoyed me when my old Netcom dialup account morphed into Earthlink. Some do it transparently. Some ISPs also restrict you to using _them_ as the From: address, but fortunately evolution has mostly fixed that. There are some newer SASL-authenticated and SSL-encrypted versions of SMTP submitting protocols that use ports other than 25, which let you use SMTP servers that are better than your ISP's.

    This proposal is different, though - it's saying that ISPs should restrict Port 25 by default, but let customers have it turned on if they do want to. That means that you can still do what you want, but if you weren't using it, and you get some Outlook virus because you're careless, you won't got spamming everybody. Some cable modem companies have started doing this, and it's much more reasonable than the policies that they used to have.

    --

    Bill Stewart
    New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
    1. Re:ISP SMTP Servers - Re:Off by default by evilviper · · Score: 1
      A lot of ISPs force you to use their server for outbound mail; it's one of the things that really annoyed me when my old Netcom dialup account morphed into Earthlink.

      Umm... I don't get it.

      I've used Earthlink primarily, for a very long time. They are one of the very few ISPs that has never even attempted to block outgoing SMTP traffic. If Earthlink was blocking SMTP for you, then it was some local issue, because they've never done that at large.

      Some cable modem companies have started doing this, and it's much more reasonable than the policies that they used to have.

      I agree completely. ISPs are so hostile torwards their users, that they like to block common ports, and then force you to upgrade to a "business" account to get them turned back on. Frankly, this practice should be illegial, since you aren't paying for "WWW access", you're paying for "Internet" access, which they advertise, and yet don't completely offer.
      --
      Slashdot gets worse every day... Pipedot: News for nerds, without the corporate slant
  59. What's new? by NerveGas · · Score: 1

    The idea of putting that sort of thing near the customer (in the ISP) isn't new at all. It's been promoted and advocated for years. There's just one problem: ISPs don't want to do it.

    They claim that they're just in the business of moving bits from one point to another. They dig in their heels and resist just about any sort of filtering on their customers. There's just one irony: They all whine, moan, and complain when someone else's infected/stupid/malicious customer causes problems for them, and the other ISP doesn't take care of it.

    I can't tell you how many times I've been approached by people, and asked "Why doesn't anyone offer a service where you're protected from (insert virus/spam/whatever)?" While I haven't (yet) started a business doing it, I've made quite a few people happy by giving them email through my mail server, where any executable attachment is blocked. A couple of times per year, it'll block a legitimate email. But (literally) tens of thousands of times per day, it's preventing malicious email from ever hitting their computer.

    steve

    --
    Oh, you're not stuck, you're just unable to let go of the onion rings.
    1. Re:What's new? by pe1chl · · Score: 1

      I think it is OK that the ISPs don't want to filter the traffic, but at the very least they should make available a system to send short messages to customers selected only by the IP address, without having to go through a manually handled abuse@isp address.

      Of course this system should be protected against use for spamming. Something like a webpage, preferably with a standard URL, with the usual countermeasures against automatic use.

      Many systems are infected with spamsending trojans without the owner knowing it, and as a victim you cannot inform the owner without the cooperation of the ISP.
      But the ISP often does not co-operate, either becasuse the abuse department is understaffed or because it has unreasonable policies.
      ("you need to supply full headers of the virus mail", "we take action only if we receive several complaints", etc)

  60. Why rate limit? by mdfst13 · · Score: 1

    Why rate limit? Just shut off the port altogether. Unless they are running a mail exchanger, cable/DSL users should not be using port 25; they should use SMTP Auth over port 587 instead. If they are running a mail exchanger, then that person should have the port open for as much traffic as they need.

  61. Software firewalls already do this. by syousef · · Score: 2, Insightful

    I use zonealarm. Most of the time its a nice sane product, and the price can't be beaten.That gives me an alert every time a new piece of software tries to access the net, for both outgoing and incoming connections. I then get to choose whether to always allow the program to make the connection, or just allow that particular instance.

    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.

    --
    These posts express my own personal views, not those of my employer
    1. Re:Software firewalls already do this. by Maserati · · Score: 2, Informative

      If a trojan infects an application, then ZoneAlarm notes that the MD5 hash has changed and it asks you again if you want to allow that application access. If you haven't done anything to change it, then block access and investigate.

      --
      Veteran, Bermuda Triangle Expeditionary Force, 1992-1951
  62. distributed spam killer? by freeduke · · Score: 1
    After you successfully configured your anti-spam firewall, you are safe from outgoing attacks.

    But then what will happen to you? You are just a lamb surrounded by wolves.

    I have linux and, as far as I am concerned, have never been subject to such worms spreading by mail. So my situation is similar to a windows system properly configured to block outgoing mail.

    The fact is that I receive a lot of email for those worm that oblige me to configure a spamassassin on my computer. I think that an anti spam filter is more efficient, at first, and quite easy to configure to block harmfull spam. Moreover, before trying to fix what goes out from your computer, if the incoming traffic was stop in the first place, no unwanted outgoing traffic would even exist.

    I really think that the problem comes for laxist default firewalling rules (if any...) in widows system: if there was a blocking one for incoming traffic, it would be good thing for the average windows user, that would have to take firewalling into account if he wants to act as a server. At least he would know about the problem...

  63. ZoneAlarmPro by v1x · · Score: 3, Insightful

    ZoneAlarmPro is best known for its ability to block to control outgoing traffic. However, lesser known is its ability to control outgoing email, by specifying which applications can send email, along with how many emails are sent at once before an alarm is raised about possible virus/worm, and the offending application is frozen by ZoneAlarm until the user intervenes & allows it permission to do so. So, the functionality of the reverse firewall to reduce spam that the author is asking for is already available.

    1. Re:ZoneAlarmPro by pe1chl · · Score: 1

      Of course a trojan that is capable of installing itself without the user's consent and distribute itself and spam from the system, will also be able to tell ZoneAlarm that it has permission to send the outgoing traffic.

      These trojans already try to (and succeed in) disable virus scanners. When ZoneAlarm would be a mandatory item or standard part of Windows, it would be targeted the same way.

      That is why the idea of installing this functionality in an external device (cablemodem) is so much better than using something like ZoneAlarm. At least on systems where the user has administrative permissions by default.

    2. Re:ZoneAlarmPro by v1x · · Score: 1

      Agreed. The weakest link remains the end-user running with defaut administrative permissions. But ZA, just like many antivirus softwares out there, already has the ability to set a password for enabling access, or for shutting it down. Without the password, it is only possible to shut down the interactive component (zlclient.exe), but the core firewall runs as a privileged service, and cant be shut down in this fashion. In addition, there is a user-invisible component to ZA, which loads up as a non PnP service at bootup (these drivers load before everything else), which offers boot-time protection. All in all, this one well designed soft-firewall.

  64. I'm in favor of public execution by Anonymous Coward · · Score: 0

    I think that convicted spammers, and especially crackers and virus writers, should be executed on public tv. The method of execution should be particularly gory and disturbing to watch. Firing squad, electrocution, hanging, beheading, and especially disembowling would all be my top choices.

    I think that all executions should be shown on TV. How is the death penalty supposed to be an effective deterrant if no one ever sees it being used?

  65. "Traditional firewalls", huh? by Anonymous Coward · · Score: 0

    Aren't they packet filters that can be configured to allow or deny in any direction on any interface?

    "Reverse firewall" seems to assume a bit too much to me. It seems to assume that one side is untrusted and the other side is trusted. But that is for the admins to decide. Regardless, what they will use in both cases is a firewall!

    Do we really need the term "Reverse firewall" for a firewall configuration that is pretty obvious for that given problem?

    I guess my OpenBSD PF firewall is a firewall, reverse firewall and whatever the next firewall flavour of the week will be.

  66. I'd get it by tutwabee · · Score: 1

    If its not much extra to have embeded into a router, I would get it in a second.

  67. Doubtfully a better idea... by Pseud0 · · Score: 1

    Sure, it would be a better idea. But how long would this take to implement? Just take the example of ICANN adding IPv6 to their root servers. They expect it'll take 20 years before IPv4 is out of the business. How many years would it take for SMTP/POP/IMAP? 10? 15? 20? ... not to mention how long it would take for the new protocols to be developed and accepted by the major players.

    VeriSigns idea is a quicker but uglier solution.

    --

    /John Sjolander, project manager Contribio
  68. Re:If we can't get people to run Anti-Virus Softwa by Artega+VH · · Score: 1

    The manufacturers will make the cable modems ect with this feature and the ISP will sell them.. or they'll become common and everyone will have one...

    The problem with anti-virus software is its an ongoing commitment.. with this thing there would be much less user maintenance needed.

    --
    groklaw, wired and slashdot. The holy trinity of work based time wasting.
  69. Letterhead? by imnoteddy · · Score: 1
    The article states:
    When a real letter comes from my bank, it is printed on letterhead with a prominent bank logo.

    Every snail mail I get from my bank is done with a laser printer - pretty easy to fake the bank logo.

    --
    No electrons were harmed creating this post, though some may have been subjected to electrical and/or magnetic fields.
  70. Windows XP SP2 has outbound firewalling by Zog+The+Undeniable · · Score: 1

    Provided the clueless millions install the Service Pack, that is. They obviously don't use updated anti-virus software to stop the mass-mailing worms, so I won't hold my breath. Everything you ever wanted to know about SP2, and many things you didn't, is here.

    --
    When I am king, you will be first against the wall.
  71. Reverse Firewall by Anonymous Coward · · Score: 0

    Reverse Firewall is essentially what ZoneAlarm, and ISS try to do by explicitly requesting permissions by changed/modified programs. Although, if poorly configured it may not do the job. I dont really understand how a reverse firewall will actually help since Firewalls generally work at the Network layer (If performance is of any concern) and therefore will allow the legitimate traffic such as email. Maybe a reverse intrusion prevention/detection system would be more apt to detect traffic abnormalities such as a high # of emails being sent in a short amount of time. Just have MS build secure code and we would not have these discussions. /.

  72. Why stop at network access? by iamacat · · Score: 1

    With all the worms, spyware and apps violating user's privacy, we need a strong security model for individual processes rather than just different users.

    Let's say, by default the application is allowed to only open one top level window and access it's own directory on the disk ala chroot jail. No internet access at all. Users can pick application type from a list of profile, for example "A typical web browser" and further edit permissions manually. Only priviliged system processes will be able to install or modify executables. Now try to turn my PC into a spambot.

  73. cumshot by Anonymous Coward · · Score: 0

    fantastic can we get more of this IT pr0n.

  74. Not a new idea by Cee · · Score: 1

    This reminds me of an old joke.
    Our university doesn't need a firewall to protect itself from allt the "hackers" on the internet, the internet needs a firewall to protect itself from the students at the university.
    Not funny? Try telling it on a party, really late..

  75. I dunno, chief. by mcco7614 · · Score: 5, Funny

    I just think it's funny that VeriSign's "chief scientist" said we should use "reverse firewalls" ... I'll foil his plans by installing a reverse router with dual reverse Ethernet switches between my hosts and my cable modem. And I'll connect it all using my reverse CAT6 cables. This way, by the time a packet arrives at the reverse firewall it will already have been reversed...in which case...uhhh...it will be re-reversed and forwarded normally. Yup.

    I'm gonna go to reverse sleep now.

    --
    "A clear conscience is usually the sign of a bad memory."
    1. Re:I dunno, chief. by Anonymous Coward · · Score: 0

      When you reverse a crossover cable, do you have to flip it too?

  76. Re:Just had to by locr1an · · Score: 1

    no, the server is the vampire. The wheels are it's markings. ~We's dumb...dumb as hell.

  77. Ridiculous suggestion by tezza · · Score: 1
    When 99% of spam comes from these guys, i don't see why our rights should be curtailed or monitored for acceptible use.

    They already have this. For internal accounting they keep track of everything traffic related, ports, amounts, frequency. If you abuse it, they send you a letter. This is governed by laws [in most sensible democracies].

    Stop eroding our rights under a smokescreen of SPAM prevention.

    --
    [% slash_sig_val.text %]
    1. Re:Ridiculous suggestion by Anonymous Coward · · Score: 0

      Amen, I want a site where people can create an organized resistance to bad internet infrastructure ideas like these.

  78. hosting companies by chrisranjana.com · · Score: 0

    Yes should start from the big companies and move to small ones.

    --
    Chris ,
    Php Programmers.
  79. Stopping china-originated spam on netfilter by zboubi · · Score: 1

    A lot of spam originates from servers located in China, Taiwan, HongKong and Korea. I don't plan to receive mail from these countries in a foreseeable future; yet, spamassassin doesn't catch all the spam they send me. So I designed a tool to filter them at the firewall level : netfilter iptables geoip

  80. Egress filtering by Alioth · · Score: 1

    In the business world, the need for egress filtering (i.e. what they are calling a 'reverse firewall') has been needed and met for a long time. For example, my network's firewall only allows *out* legitimate traffic, rather than the typical NAT home broadband router which by default blocks in on all, but passes out on all. My default rule is block in on all and block out on all, and only open port/IP combinations where there is a definite legitimate need to be met.

    Many people fail to see the value in egress filtering by default - most small-business network administrators see the obvious need to protect their network from incoming traffic from the Internet, but don't think about the consequences of a cracker getting in and being able to defeat your ingress filtering by having their machine listen to a port, and then remotely (say, via a webserver vulnerability) have a shell connected as an *outbound* connection to their machine. Not to mention that egress filtering helps you be a good net neighbour - if someone manages to run a trojan, it's at least contained.

    1. Re:Egress filtering by pe1chl · · Score: 2, Interesting

      But this filtering is quite difficult to do, especially with static rules.
      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 utility of this approach, because when a cracker is able to install a trojan process that does outgoing connects, who guarantees me that he will not be able to defeat this magic filter?

  81. Dangerous twaddle by cardpuncher · · Score: 5, Insightful

    Apart from the annoying debasement of the word "scientist", this really does reveal VeriSign's view of the function of the Internet and, unfortunately, it's becoming more common.

    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.

    1. Re:Dangerous twaddle by mks113 · · Score: 3, Informative

      Yep, it is getting more widespread too.

      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

    2. Re:Dangerous twaddle by Anonymous Coward · · Score: 0

      "We have met the enemy, and he is us!"

      No, the enemy is simple economics.

      ISPs simply can't stay in business if they offer unlimited, unfiltered access to people who are cheap and only buy the least expensive consumer-grade connection package.

      Your usage pattern is not that of an average customer. The fact that you were able to exceed normal usage patterns without paying more was a GIFT by the ISP. When you use more resources then others (more then your fair share), then it makes perfect sense that you should pay more. (Hint, it's called business-class pricing for business class service.)

      The fact that you don't *like* it has nothing to do with anything and has nothing to do with "the man is trying to keep us down".

      You're just pissed because too many people figured out how to pig out at the trough and now the ISP had to crackdown on the overeaters. Now, instead of getting first-class service for cattle-class fare, you're being asked to pay first-class fare for first-class service.

    3. Re:Dangerous twaddle by Anonymous Coward · · Score: 0

      I think there is a huge flaw with that. ISPs are forever advertising 'Unlimited Internet.' If they are going to give you 'Unlimited Internet (up to certain vague common usage patterns)' then they should have to advertise as such. They show you a BMW then hand you the keys to a ford. I don't think you deserve the BMW for the price of the ford, but you do deserve to know exactly what it is you are paying for.

    4. Re:Dangerous twaddle by Anonymous Coward · · Score: 1, Interesting

      It's always been the same, at least as far back as I've been online (no not since the beginning, probably 14 years or so though).

      The ISPs get away with that kind of bullshit because 98% of users don't go anywhere near the limits and no matter how loudly the other 2% shout that they're being ripped off, nobody listens or cares.

      They can't advertise it as "limited internet" because nobody else does, they wouldn't get new customers despite the fact that those customers would have stuck well within the limits anyway. People always like to think they're getting more for less.

      The result is that anyone who does want their broadband connection to be used as a broadband connection either has to pay vastly inflated business rates or use an ISP that hosts spammers/porn/etc where they end up blacklisted from half the net.

      Theres also the TOS (terms of service), most ISPs TOS includes statements such as "we reserve the right to change the TOS without informing the customer and without incurring liability", i.e. we can do whatever we want and you can suck it up.

    5. Re:Dangerous twaddle by ElOttoGrande · · Score: 1

      There are other ways to run mailing lists. Most of my friends use Yahoo Groups or a list manager from their hosting company. But i just did a quick search and came across http://www.coollist.com/ . Dunno if it's any good but might be worth looking into.

    6. Re:Dangerous twaddle by nzhavok · · Score: 1

      Try bsdwebhosting.net, I've never tried sending more than a few emails a day but I'd be surprised if they were limiting it. You can send them an email to check I guess.

      I've used them for about a year now and it's been pretty economical.

      --

      He who defends everything, defends nothing. -- Fredrick The Great
  82. OptusNet does this already in Australia. by Trejkaz · · Score: 1

    I had to actually phone them to ask them to turn it back on when it happened, because naturally they were blocking me sending an email to request it. But it's good that it's there now, even though it did mean a bit of inconvenience in the beginning.

    --
    Karma: It's all a bunch of tree-huggin' hippy crap!
  83. Just to be pedantic by fishbot · · Score: 4, Informative

    but a firewall is a piece of software which allows or denies packets based on their properties; it cares not in which direction they are flowing.

    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.

    1. Re:Just to be pedantic by pandrijeczko · · Score: 2, Informative
      Mod parent up!

      I thought this exact same thing also... I have no experiences with commercial firewalling software but have used ipchains/iptables within Linux also.

      ipchains/iptables simply treat each packet as one of three types:

      1. Incoming (from a specific network interface)

      2. Outgoing (to a specific network interface)

      3. Forwarding (incoming from one network interface and outgoing to another = "routing")

      The way you build rules for each packet type is identical so you never have the concept of just "protecting me from the outside world", more "should this packet from point A be allowed to get to point B" where point A or point B can be the local host or a distant one.

      I'm afraid it's all about marketing (again!) - "buy our firewalling software because you are the good guy that needs protecting from the bad guys on the Internet" without any mention of the fact that you might actually be the bad guy, albeit unknowingly.

      --
      Gentoo Linux - another day, another USE flag.
    2. Re:Just to be pedantic by Anonymous Coward · · Score: 0

      I'm sorry, but you're wrong. Any modern, decent firewall in the last five years pays attention to the direction. It also pays attention to see if it's part of a valid session.

      Go ahead and try to name just one firewall vendor that doesn't pay attention to a packets direction. They all track it.

    3. Re:Just to be pedantic by HermanAB · · Score: 1
      You add the interface IP address or network name to most of the rules to define which way the rule is working.

      This is necessary to make masquerading work and to protect against specific attack types from the outside, or blocking telnet incoming, while allowing it outgoing etc.

      --
      Oh well, what the hell...
  84. Difference between Spam and Newsletters? by Anonymous Coward · · Score: 0

    What about startup companies that don't have a huge corporate mailserver and the know-how to set one up? Should sending newsletters be this difficult when its blocked by the ISP? If it were only spam I would agree, but you can't for example make media unreadable so that people can't copy it? If I buy a cd i expect it to play on my computer or cdplayer just as much as I expect to be able to send out newsletters from my home to subscribing costumers using my ISP!

    I'm not talking about unsoliscited email, I'm referring to what makes the Internet an incredible resource in communication! Reverse firewalls would probably block a percentage of spammers who don't have their own servers but also the startup companies that rely heavily on their home DSL account.

    Also, spammers my friends, don't all live in america... so I am NOT pro this ridiculous idea of blocking mass emails not knowing the content of them... whats next? ISP customer blacklists? How would one acquire those blacklists as an ISP? Read the customer emails? lol...

  85. Last I heard... by JOstrow · · Score: 1

    ...a "reverse firewall" was called the OUTPUT chain.

  86. Re:Just wait by ZenJabba1 · · Score: 1

    too late ... http://yro.slashdot.org/article.pl?sid=04/07/20/10 15234&tid=95&tid=17

    --
    `find / -name "*your_base*" -exec chown us:us {} \;`
  87. New??? by really? · · Score: 4, Interesting

    Perhaps it's just me, but egress filtering is the default behaviour on all FW boxes I set up. And I'm not even that much of a harcore security geek.

    --

    "Consistency is contrary to nature, contrary to life. The only completely consistent people are the dead." A. Huxley
    1. Re:New??? by geminidomino · · Score: 1

      I'm not even that much of a harcore security geek.

      No, you're someone with half a clue who'd like to prevent his boxen from blasting spam and/or other naughtiness at innocents, not some sniveling half-wit who thinks that for $30/month, the internet is his personal playground to shit on as he sees fit.

      Good job.

    2. Re:New??? by julesh · · Score: 1

      Perhaps it's just me, but egress filtering is the default behaviour on all FW boxes I set up. And I'm not even that much of a harcore security geek.

      Are you sure? I've never met a non-hardore security geek who knows what 'egress filtering' is. And you seem to admit to having installed firewalls that aren't software packages that run on the PC they're protecting. This is definitely the behaviour of a security geek.

    3. Re:New??? by Maserati · · Score: 1

      "This way to the egress filtering seminar ----->"

      --
      Veteran, Bermuda Triangle Expeditionary Force, 1992-1951
    4. Re:New??? by really? · · Score: 1

      I've never met a non-hardore security geek who knows what 'egress filtering' is.

      Now you have. :-)

      But seriously, anyone with even a modicum of curiosity/concern can pick up a copy of "Firewalls for Dummies" and get 1/2 a clue. No?

      --

      "Consistency is contrary to nature, contrary to life. The only completely consistent people are the dead." A. Huxley
  88. Dark Ages by paulkoan · · Score: 1

    It is endlessly frustrating when there are posts like this.

    Why isn't it obvious that the only traffic allowed in and out of a network or PC is that traffic that has been explicitly defined as being allowed. Even if that network consists of nothing but your home PC.

    You don't "block email not coming from your server", you simply do not *unblock* anything but the traffic you need.

    Explicit! Not implicit! Repeat until you either get it or you get someone else to do it that gets it.

    Sigh.

    This was disappointing five years ago, and will undoubtedly disappoint in another five.

    koan

    --
    This signature intentionally left blank
  89. Quick! by paulkoan · · Score: 1


    Everyone stop saying "reverse firewall".

    No, just stop.

    A firewall is something that controls traffic flow through it. Not in a particular direction.

    A reverse firewall is one that you have simply turned around. This just makes it harder to plug the cables in. Or easier if you are using non-specific hardware as a platform.

    So don't say it anymore.

    Oh crap look at Google, there are already 670 entries for "reverse firewall".

    Damn, thats another one.

    koan

    --
    This signature intentionally left blank
    1. Re:Quick! by syrinx · · Score: 1

      Thank you. That's what i thought when I read the title... "reverse firewall? wtf?" That doesn't mean anything. It's a firewall, period, no matter what 'direction'. It's like "reverse descrimination"... again, a stupid term.

      I'm giving up on the English language and moving to Sindarin.

      --
      Quidquid latine dictum sit, altum sonatur.
  90. Incorrect analysis. by samjam · · Score: 1

    Your eager analysis is flawed.

    The only people who will be affected are
    1) those who use the ISP-supplied modem
    AND
    2) don't ask to have that feature disabled because they are running mailing lists

    Most users with trojan'd machines are not running a mailing list, are using the ISP supplied modem and will not be asking to have this feature disabled.

    You are correct when you say it requires co-operation from many people at once, but each ISP that uses it gives their customers an advantage as spamming moves to other networks and their customers avoid being black-holed.

    Most cable ISPs have remotely updatable firmware so it is technioally managable - I think this covers any valid parts of your "lack of centrality" objection, and the fact that the end user is not required to install any patches.

    Sam

    1. Re:Incorrect analysis. by geminidomino · · Score: 1
      Your eager analysis is flawed. The only people who will be affected are 1) those who use the ISP-supplied modem AND 2) don't ask to have that feature disabled because they are running mailing lists
      Read the form again in context of the parent's "Dump SMTP" post and it will make a LOT more sense.

      For the record, I consider NOT using egress filtering to be neglegent.
    2. Re:Incorrect analysis. by samjam · · Score: 2, Informative

      I stand corrected, yes, your analysis is correct in regard to the abandonment of SMTP recommendation.

      Sam

  91. Which is why SPF is a load of rubbish by samjam · · Score: 1

    SPF is flawed, and won't become a popular standard for reasons like this.

    I don't want to debate about it, but the few people who behave against the SPF rules in the various different ways add up to a lot of people.

    If folk don't want to hear from me because of SPF, then I don't want to talk to them.

    Sam

    1. Re:Which is why SPF is a load of rubbish by mdfst13 · · Score: 1

      Open relay blacklists are flawed (they reject legitimate mail) but still obtained wide use. I remember back in 2001, the mail server that I helped administer was blacklisted because it would relay mail for a departmental mail server that was an open relay. Were we able to ignore ORBS? No, a football coach was unable to send email to one of his correspondents, so we had to make the department fix its mail server. We weren't offered the luxury of saying that it was the receiving mail server's fault for blocking us based on dubious information (and we weren't allowed to blacklist the departmental mail server, which was my suggestion).

      Microsoft and AOL have already agreed to support SPF. In fact, from http://spf.pobox.com/adoption.html "AOL is also currently requesting all of their whitelist partners to switch to SPF to remain on their whitelist." Perhaps you can afford to not send email to AOL addresses, but I (and many others) can't.

  92. Personal firewall setup by smittyman · · Score: 3, Funny

    yeah just like all the other "personal firewalls".

    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 Outlook and Outlook express.
    Yes / no / I like it
    - Paid for more space on the hotmail account.
    Yes / no
    - You made friends with a Gorrila.
    Yes / no / I like him because he is purple
    - Do you trust company popups that trie installing software.
    Yes / no / They are here to help me run the internet arent they?

    Thank you for filling out these questions, your personal setting will now be choosen. While we are doing that please fill in as many square boxes below as possible and a few email adresses from YOU and your friends so we can GIVE you information for FREE......

    Setting found, If one of the questions above was not no your personal firewall will be put in the L-User setting, dis-engaging internet connection now, thank you, go read a book or play solitaire........still here? the setting was permanent, shoo, SHOO, rebooting now......

    --
    Message from god, Please logoff, rebooting the Universe
  93. Mailing Lists? by Agret · · Score: 0

    I'm sure this would conflict with some mailing list senders who have many contacts and decide to send all the emails at once, that always gives a burst in email sending. This would block all the messages from your mailing list.

    --
    Have you metaroderated recently?
  94. Router manufacturers sell security features by Shirotae · · Score: 1

    Router manufacturers compete on features, and that includes security. See for example Cisco's "Network Admission Control", or HPs "ProCurve Networking Adaptive EDGE Architecture". It may take a while for those sort of security features to appear in consumer products, but defending the rest of your enterprise network against an infected PC is a real market for the router and switch manufacturers. If a particular idea is not taken up it is more likely that the people who really know the business think it will not work.

  95. There's a bigger issue here... by EmagGeek · · Score: 1

    Everyone is harping on the fact that the term "reverse firewall" is not really accurate. But, there's a more important issue here, and that is the idea that one of these should be forced on anyone who has a cable modem or access point. They're talking about taking more control away from Internet users, which I believe is the wrong thing to do.

  96. and, better yet, by gilroy · · Score: 1

    a reverse firewall will keep Megabyte and Hexadecimal bottled up in the Tor... :)

  97. Wouldn't this be like herding cats? by hodet · · Score: 1

    What is the chance of getting everyone out there behind their own reverse firewall? Slim, very slim. However, blocking outbound port 25 at the ISP's router is the way to do it at the flip of a switch and still maintain the flexibility of opening it up to those users who have a business need or have demonstrated the "know how" to run their own mailserver. We can't even get all ISP's to block port 25, how you gonna get aunt Jane and kasaa loving cousin Sally to bother going down to Costco to pick up a router with reverse firewalling built in.

  98. Done! by troon · · Score: 1

    Blocked outgoing port 25 except from my Linux mail server.

    My three-year-old daughter is an Administrator on my Win2k box (mutter, mutter, stupid Bob the Builder game), so if she manages to do anything that compromises the box, I won't be churning out spam now.

    --
    Ydco co ,df C erb-y go. a Ekrpat t.fxrapev
  99. Standard practice at companies? by atcurtis · · Score: 3, 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....

    --
    -- The universe began. Life started on a billion worlds...
    -- Except on one where stupidity was there first.
  100. Fix Outlook by Anonymous Coward · · Score: 0

    why run something to "fix" a buggy program. Fix the buggy program first. If MS doesn't fix it - throw it out!

  101. exactly by scharkalvin · · Score: 1

    what many ISP's are now installing on their servers. Bell south is now changing their servers so the clients must log in and verify their identity each time they send mail. BTW they told me they don't surport Mozilla but do support Netscape! Idiots...
    Netscape IS Mozilla!

  102. So... just crack the firewall by Ed+Avis · · Score: 2, Interesting

    Obviously, if the firewall rather than the PC becomes the main point allowing or denying access to the network then attackers will concentrate on the firewall instead. Lots of consumer-level firewalls are likely to have 'easy-to-use' features which can be exploited. Probably even a firewall control panel accessed from Windows, so all you need to do is crack the PC and wait for the user to enter the firewall password once.

    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.

    --
    -- Ed Avis ed@membled.com
  103. Yeah right... by Anita+Coney · · Score: 2, Insightful

    And the cable companies would NEVER use it to shut down things they don't like, e.g., online gaming servers, p2p programs, etc.

    --
    If someone says he and his monkey have nothing to hide, they almost certainly do.
  104. Unskilled user here by Anonymous Coward · · Score: 0

    If you're running any reasonably modern firewall (or using Linux and iptables for your firewall) this is fairly trivial to setup.

    Feelin' a little bashful over here, hence the AC . . . I'm an OS X user and using a Linksys WRT54G router (or whichever is their wireless g model). How do I set it up to kill outbound port 25 traffic with execptions that I designate?

  105. Help censor the American media by Anonymous Coward · · Score: 0

    Support ethnic cleansing in Palestine and help censor the American press!
    If you are at an American University we are recruiting active censorship drones to spy on fellow students, lecturers and guest speakers on behalf of the Israeli government.
    We can stifle democratic thought and criticism of Israeli fascist oppression -But only with your help!

    Free housing:In six short weeks we can show you how to build a rogue state by demolishing existing homes in Palestine and building new houses on top!
    We are currently looking for experienced bulldozer drivers with a large western bank balance to emigrate to the expansionist state of Israel and call it home.
    Simply choose a plot of land and start building! Its easy peesy!!
    If your chosen plot is currently occupied by a Palestinian family, dont worry
    -simply build over them!
    Its as easy peesy as eeny meeny miney mo!

    We can protect your residential developments on occupied land with experienced snipers in full body armour and appropriately armed Apache helicopters kindly donated by the American public.
    If you are an American citizen with a view to emigrating to warmer climes and view of the Med, you may also be eligible for a fraction of the 3,000,000,000 (yes thats 3 Billion!) dollars donated yearly by American taxpayers to help support our broken-ass state.

    Due to our endless appetite for weapons of mass destruction our economy is unsustainable and we require your support. WMDs don't come cheap you know. It costs $$$$$$s to terrorise a whole region.
    Our military personnel can barely afford to maintain our arsenal of 200 nuclear weapons, spy satellites and attack submarines.
    Give a man a gun and he can kill a Palestinian child. Give him a helicopter and he can kill them all.
    Part-time vacancies available:
    We are currently in construction of the world record breaking apartheid wall surrounding the largest ethic ghetto since Krakow.
    The Israeli military is hiring expatriates preferably with a military background to monitor the prisoners and maintain watchtowers. If you are blinded by a covetousness of other peoples land, but have a keen eye with a sniper scope you would be the ideal candidate for our border watchtower division.
    We need your help. Sponsor an Israeli colonizer.
    Do it today.If anybody criticises you, just point a finger an call them anti-Semite.
    It worked for the Liberty.

  106. reversefirewall? isn't that just a proper firewall by bingbong · · Score: 1

    i've always held that a good firewall ruleset should have an 'east german borderguard' type mentality. all traffic going in and out on either side is suspect of being bad things.

    all the concept of 'reverse firewall' does is demonstrate how inadequate and inappropriately named the 'built-in' firewalls that come on cable/dsl router/modems are.

    --
    "Omnis tuus capsa sunt inesse nos"
  107. This is nothing new by jbarr · · Score: 2, Interesting

    I've been using Zone Alarm to do this for years. And as I recall, Windows XP SP2 will include a bi-directional firewall. While it would be nice to have this implemented into a set-it-and-forget-it hardware solution, apps like Zone Alarm are are free and quite effective.

    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.

    --
    My mom always said, "Jim, you're 1 in a million." Given the current population, there are 7000 of me. God help us all!
  108. Also known as... by Anonymous Coward · · Score: 0

    A *REAL* firewall rather than a cheap firewall appliance

  109. well, that's it by zogger · · Score: 2, Interesting

    A "hardware" firewall is just a software firewall on another machine. As such, it's still complex to keep it setup correctly. You can get close to a default good condition, but it's not perfect.

    "but it also requires the user to accept or reject applications requesting access (and knowing users, they will just click accept all the time)."

    You got it. There is no easy practical way to actually know what all the requests, even when presented with them, actually *mean* right then at the exact second you need to make an executive decision on allow/disallow. You have the tool to do this, but not the knowledge to make the decision intelligently without a LOT of prior research, it is not default "clear" to most people. For one, you as joe user have to know which host/process/connect/in/out is cool or not. The firewall will do what you tell it to do, that part is not difficult, it's binary, yes or no, but if you don't *know* intuitively,in advance of being forced to make a decision, you have to *guess* if you want to continue surfing.

  110. Well, duh! by Xenophon+Fenderson, · · Score: 1

    All the guy's talking about is egress filtering, and I too wish more people did it. Thankfully, some ISPs have gotten a clue and started filtering individual outbound services (e.g. SMTP) or installed intrusion prevention systems at their NAPs (e.g. RoadRunner Business Class, who block my portscans, the bastards). Unfortunately, egress filtering, like ingress filtering, requires detailed knowledge of your network in addition to appropriate Acceptable Use Policies, and your typical business or residential customers rarely have that depth of understanding.

    --
    I'm proud of my Northern Tibetian Heritage
  111. SomePoorSchmucks Law of Short-Sightedness by SomePoorSchmuck · · Score: 1

    Anyone who goes on record as saying "normal people have no need for [technology x]" will find themselves quoted to hilarious effect when, within ten years, "normal people" are using [technology x] as part of daily life.

    --

    Hollywood, Television, has become the dream machine. We need to take that back; each of us is a Dream Machine
  112. egress filtering anyone? by blackbear · · Score: 1

    This isn't new. It's not even something that security practitioners don't know about. It's just something that management doesn't want to implement in most cases, and that personal firewall vendors are afraid to.

    It's egress filtering and every firewall in existence should have been configured to do it a long time ago. When done correctly, it can allow you to filter all of your outbound traffic with ease on your existing firewall.

  113. How about "Egress" instead? by ThatDamnMurphyGuy · · Score: 2, Interesting

    "Reverse" firewall huh. That sounds a lot like Egress filtering to me. Don't all real firewalls do that?

    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.

  114. More on Zone Alarm (Was Re:This is nothing new) by McLuhanesque · · Score: 2, Interesting

    More than just tying the application to the port (email client to port 25) Zone Alarm warns if an excessive amount of email is about to be sent by the previously authorized client. My normal mail goes without a peep; my distributions to a mailing list gets a Zone Alarm confirmation.

    With a compromised spam factory, such a volume warning may serve to wake up even the most naive user. OTOH, I wouldn't be surprised at a, "Oh that Zone Alarm thing? Yeah, it does that every night..."

  115. Stupid is as Stupid Does by Anonymous Coward · · Score: 0

    Last I checked, my firewall blocks coming and going on 90% of the ports. It makes exceptions for things like FTP,POP3,IMs,ect... This reverse garbage isn't new. As a matter of fact, it's been around for a few years now. It's not a reverse firewall, it's just a well designed firewall. I picked up one for $100 at a shop. years ago.

  116. It is called egress filtering,... by Darth+Daver · · Score: 1

    and it has been considered a best practice for a looong time. Unfortunately, it requires a little bit of knowledge, comprehension, skill and time, and most computer users will have none of that, hence Windows.

  117. Kind of pointless... by javab0y · · Score: 1

    Why spend all the money to stick this stuff in DSL and Cable modems, when they should be signing up ISPs to block the ports at the gateway. Then there is no need to have all these companies distribute a hardware option.

  118. This is like reverse Discrimination by Anonymous Coward · · Score: 0

    This is like reverse Discrimination....

    Is it a firewall or isn't it?

  119. Too lazy to patch or protect by Anonymous Coward · · Score: 0

    If folks won't use AV software or patch their computers, why would they bother to set up a firewall properly?

    I find it interesting someone coined a new term to describe what firewalls have always already been able to do and the security community has preached about for years now.

  120. snitch for windows/linux? by Anonymous Coward · · Score: 0

    I've been trying to articulate a request
    for something like Little Snitch for over a
    year. I knew it was out there somewhere,
    but I never expected to find exactly what I
    wanted - but on a platform that has (comparatively) little need for such protection.

    Please folks... is there anything like the snitch for those of us who can't afford a modern mac?

    1. Re:snitch for windows/linux? by indiechild · · Score: 1

      For Windows? ZoneAlarm.

      Seriously, I've been using ZoneAlarm for years. I used Sygate before that, and have also tried various other proggies. ZA is the one I keep coming back to, and you can get a free version as well.

  121. REBOOT COMMENT by Anonymous Coward · · Score: 0

    Just like the ReBoot cartoon! SWEET!!!!

  122. It's Called ZoneAlarm by Anonymous Coward · · Score: 1, Informative

    And I've been using it for years.

    Great for stopping those pesky programs that like to "phone home to mother" without your permission.

  123. "Reverse" Firewall? by Semantic+Anomaly · · Score: 1

    I always thought that the purpose of a firewall was to filter traffic, whether it be outgoing or incoming. Isn't the term "reverse firewall" about as ridiculous as "reverse discrimination?"

  124. Great by Eudial · · Score: 1

    *wraps his cable modem in tin foil*

    --
    GAAH! MY PRINTER IS ON FIRE!!! PUT IT OUT! PUT IT OUT!
  125. Try SmoothWall! by heybo · · Score: 1

    Try SmoothWall Firewall. A great open source and easy to set up and use firewall.

    SmoothWall.
  126. Sending out bulk emails is my right by Anonymous Coward · · Score: 0

    and no router is gona stop me from doing that!

    1. Re:Sending out bulk emails is my right by Anonymous Coward · · Score: 0

      yeah, and supposedly smoking in public is your right too, but everyone hates it and would end it if they could. outbound filtering provides a means to this end. makes the net better for everyone if we don't have numbnuts like you exercising their 'rights' to staple ads to everyone else's email accounts.

  127. One better Balastic armor system by SWTP_OS9 · · Score: 1

    Why not a balistic armor firwall system. Any thing like spyware etc when it hits your firewall fires back a kill program to the orginator that terminates that system. After about .002 seconds proabbly half of the worlds computers would be clean permently.

    Locks only keep honest people out.

  128. Yes, assuming... by mwood · · Score: 1

    ...that "normal email" means "everything goes through my ISP's server." Wrong.

  129. Re:Not just for spam! by drakaan · · Score: 1
    Does free count as sub-100-dollars (well, about $25-$50 worth of hardware for the average geek)?

    Look here and here.

    This is slashdot...if you're here, you're probably a geek, and cheap to boot...build your own.

    First link is for control freaks, second link is for putterers.

    --
    "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
  130. Reverse firewall by rotozapper · · Score: 1

    check mirage networks out

  131. What happens when some ignorant user "teaches" by blueZ3 · · Score: 1

    the firewall that the spam trojan is legitimate traffic?

    I'm pretty sure that most folks see the little "Allow this application to connect?" dialog and click OK automatically. That's what Windows has been teaching them to do for eons... try and delete something, then click Ok. Try and close a program, then click Ok.

    So when the firewall says "Do you want to allow Bob's Friendly Spam Puppy to connect to the Internet?" they just automatically click Ok. This is additionally reinforced when they click "No" after seeing "Do you want to allow msimn.exe to connect to the Internet" (What's that anyway - sound suspicous!) and mail stops working. Oh oh! Better never click No!

    There's no silver bullet.

    --
    Interested in a Flash-based MAME front end? Visit mame.danzbb.com
    1. Re:What happens when some ignorant user "teaches" by Zeinfeld · · Score: 1
      I'm pretty sure that most folks see the little "Allow this application to connect?" dialog and click OK automatically. That's what Windows has been teaching them to do for eons... try and delete something, then click Ok. Try and close a program, then click Ok.

      Granted there are pinhead end users. But you are stuck in the mindset that if there is any possible flaw in a security scheme then it cannot be any use at all. This is the type of thinking that has led us to the current situation.

      First off I am proposing firewalls at the network edge because it is much harder for end users to be gulled into over-riding them. I have plenty of complaints from people telling me that their kids have mucked up their PC.

      Secondly even if some people turn off the controls they can still have a real reduction in fraud losses and in propagation of viruses. If only 80% of systems have the rules turned on that still reduces the fraud losses to a fifth of what they would be. In the case of virus propagation (x/5)^n is a much friendlier exponent to deal with than x^n. If x 5 then the virus quickly dies.

      --
      Looking for an Information Security student project suggestion?
      Try http://dotcrimeManifesto.com/
  132. Used Academically by Flamesplash · · Score: 1

    My ugrad Clemson did this back when I was there 97-00 to keep all the kiddies from sucking up bandwidth using p2p programs etc, as well as using dialpad, for which we made /. I believe.

    --
    "Not knowing when the dawn will come, I open every door." - Emily Dickinson
  133. Firewall, not a "reverse firewall" by hkb · · Score: 1

    Egress filtering is a normal function of a normal firewall, so I don't see a particular need for some new "reverse firewall" paradigm.

    Even newbie-oriented firewalls have been doing egress filtering for some time. See also: ZoneAlarm.

    --
    /* Moderating all non-anonymous trolls up since 2004 */
  134. One doesn't preclude the other by pdp0x14 · · Score: 1
    Eventually SMTP protocols will be enhanced, but that activity is independent of other anti-spam activity in the meantime.

    There's nothing wrong with monitoring outgoing traffic in the cable/DSL modem if the user has the option to control the blocking rules. All good (software) personal firewalls have this capability.

    I like to know when some piece of commercial software suddenly decides to phone home. It's also potentially a good trojan warning.

    This is actually a very good idea. It's the ISPs who choose which modems to use and their interests lie in reining back bandwidth usage, so they can put pressure on the modem manufacturers.

  135. Built in to the cable modem? by pclminion · · Score: 2, Interesting
    In other words, this guy wants to force us to install egress firewalls on our home networks in the name of "stopping spam?" Can anybody else see how terrible this idea is?

    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.

  136. This gets back to default security by Anonymous Coward · · Score: 0

    All that's needed is for the OS to properly disable commonly unneeded/often abused ports until a user manually decides to open them. For example, windows typically comes with most ports open, whereas OS X comes with most ports closed. The reason for setting most ports closed by default is because most users are unaware of how ports are used and that certain incoming/outgoing ports should probably be disabled unless there's a dedicated reason for opening them. It shouldn't be the responsiblity of the user to have install some sort of "reverse firewall" program, it should be the responsibility of the OS to close "unsafe" ports by default and provide the user with good recommendations for port open/close actions based upon the actions they want to perform.

  137. Doesn't make much sense to speak of "reverse" FW by hhardy01 · · Score: 1
    It is illogical to speak of a "reverse firewall". Perhaps these folks also tore a hole in the front of their house next to the "door" so they could also have a "reverse door" to exit by!

    Firewalls work both ways, in and out. Which side is "in" and which side is "out" is also just a matter of definition and which network connection you connect to which port.

    I think what they meant to discuss is "egress filtering" and this is not by any means a new idea. see "Consensus Roadmap for Defeating Distributed Denial of Service Attacks" at http://www.sans.org/dosstep/roadmap.php from February 2000 for one prior example of this concept.

  138. then it will be... by nazsco · · Score: 1

    the same.

    today:
    1. infect PC
    2. zumbify it
    3. ???
    4. profit!

    with that crap ideia in place:
    1. infect PC
    2. zumbify it
    2,5. run some code to change the modem settings from the lan side.
    3. ???
    4. profit!

    On the other hand, i mean, the regular user hand:
    1. buy a PC and pay for an exorbitant adsl service
    2. use it

    with that crap ideia in place:
    1. buy a PC and pay for an exorbitant adsl service
    2. get lots of legitime services blocked because of crap implementantions of crap ideia.

  139. How I did it with my router/firewall by Anonymous Coward · · Score: 0

    Here's what I did. I bought a Netgear FR114P (combination router, firewall, switch, print server). I also bought a subscription to secure-tunnel.com, which allows me to tunnel out web, mail, news and some other traffic through their anonymizing servers. Then I put rules into my Netgear firewall to block ALL inbound traffic and block ALL outbound traffic. Then I put in exceptions for my secure-tunnel connections outbound to secure-tunnel's servers. I use Mozilla Thunderbird and Firefox, which do their own proxying rather than tying into Windows proxying. Result? Nothing on my system knows how to secretly call out anymore. No need for ZoneAlarm or any other kind of software solution. Nothing gets in or out unless I allow it. I tellya, for $80 you can't do much better than that.

    For games, I open explicit ports only when I'm playing, so I can even game (very easily) with this setup.

    Next step is to set the parents up with a rig like this. It's cheap, and the peace of mind rocks. And it's fun to watch spyware like RealPlayer flail around trying to call home.

  140. I don't want the cable company doing it TO me! by lordscotus · · Score: 0

    Reverse firewall?! Only when I set it up. I don't want the cable or DSL provider deciding what can connect out of my machines!

  141. And they'd be secure, right? by ummit · · Score: 1
    ...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..."

    And given the rock-solid nature of the platform in question, there's no way the bot software would ever be able to reprogram the `reverse firewall' to let the floods out anyway. Uh uh, no way.

  142. i want to make up new words too! by Anonymous Coward · · Score: 0

    Instead of calling in egress filtering, I'll call it a reverse firewall. Now, gimme loads of cash for being an internet consultant.

    Excuse me, i'm going to go get a coke out of my compressor driven kitchen heater ( turns out the inside of it is cold! ).

  143. Verisign trusted security? by ReNeGaDe75 · · Score: 1

    I thought Verisign was a digital security company. Yet they don't know how a firewall works... and these people go around signing security certificates. Wow am I ever impressed.

    For some reason evil monopolistic companies and stupid uneducated companies seem to always be the same.

    --
    Hypocrisy is the 8th deadly sin.
  144. firewalls like 'flammable' by JimmytheGeek · · Score: 1

    reverse firewalls are like 'inflammable'

  145. Re:Not just for spam! by DAldredge · · Score: 1

    True. But the rest (95%) of the population will just fsck up our internet because they will use the store bought UPNP enabled ones.

  146. Where can I get a reverse firewall for my wife? by Anonymous Coward · · Score: 0

    Just sayin... any human implementations possible?

  147. Ah a *reverse* firewall by dcam · · Score: 1

    Otherwise known as a firewall.

    --
    meh
  148. NAT O' Matic; Time of Past by layer3switch · · Score: 0

    While it's hard to believe someone who should know better will actually state something like "reverse firewall"; an idiosyncrasy common to denial-state bureaucrats who's been long resistant to giving control to the users and to applying better method of security policy and measure, it's a sign that finally industry is making step toward breaking that set-it-and-forget-it NAT'd mask as the only line of defense, an old odium among many security and control freaks.

    Perhaps VeriSign can convince enough cable and dsl providers that setting security policy on the both side of the fence instead of simple NATing is a common practice.

    --
    "Don't let fools fool you. They are the clever ones."
  149. oh good then my computer could be just like my TV by waspleg · · Score: 1

    one-way communication that you pay a subscription to access the "content" of

    brilliant.

  150. Re:Not just for spam! by drakaan · · Score: 1
    Do what I do...go on a crusade. The next time a 95-percenter says "man, I got TOTALLY hosed by virus X", ask him if he has an old PC lying around, and set him up.

    Up-to-date antivirus software and a hardware firewall will stop most of those machines from ever being used as open proxies or open relays, and you can sell it on the "hey, just buy one of those 'hub' thingies, and you can connect more than one computer to the internet at the SAME time!" (from past experience, try to stand back so when their jaws drop they don't hit your shoes).

    Even non-techies are cheap...they'll bite, especially on a pitch made by their personal geek friend.

    --
    "Murphy was an optimist" - O'Toole's commentary on Murphy's Law
  151. Words, words, words... by zooblethorpe · · Score: 1

    I'm something of an inveterate language geek, and now a professional linguist (translator), and I read your post and the linked page with some interest.

    Coming away from the linked page, I found myself thinking a couple things. For one, if the Latin speakers of the time considered "virus" a non-count noun, this clearly denotes a quite different concept from the modern one. In such a case, it makes sense for the word to change (i.e., to grow a plural when previously it had none).

    For two, I find it admittedly unexciting that some English speakers should choose the "us -> i" for the plural. Sure, that might be inconsistent with the original Latin, but then so is the whole concept of the plural "virus" to begin with. (Incidentally, though the linked page was quite scandalised at the thought of anyone using "octopi", nowhere did it say what would be the correct plural; furthermore, Merriam Webster lists both "octopi" and "octopuses" as the plural forms...)

    Waxing somewhat philosophical, I ask what is a word, in your view, and posit that languages change. My point is that, ten years ago, "blog" was not a word, while now it is widely understood. "Virii"/"viri" may cause some (considerable) cognitive distress, but if it has common currency, is it not a word? If it isn't, what would it take to make it one? I'm genuinely curious as to what you think, and would appreciate a response.

    --
    "What in the name of Fats Waller is that?"
    "A four-foot prune."