Slashdot Mirror


Routers Pose Biggest Security Threat To Home Networks

Nerval's Lobster writes "The remote-access management flaw that allowed TheMoon worm to thrive on Linksys routers is far from the only vulnerability in that particular brand of hardware, though it might be simpler to call all home-based wireless routers gaping holes of insecurity than to list all the flaws in those of just one vendor. An even longer list of Linksys (and Cisco and Netgear) routers were identified in January as having a backdoor built into the original versions of their firmware in 2005 and never taken out. Serious as those flaws are, they don't compare to the list of vulnerabilities resulting from an impossibly complex mesh of sophisticated network services that make nearly every router aimed at homes or small offices an easy target for attack, according to network-security penetration- and testing services. For example, wireless routers (especially home routers owned by technically challenged consumers) are riddled with security holes stemming from design goals that emphasize usability over security, which often puts consumers at risk from malware or attacks on devices they don't know how to monitor, but through which flow all their personal and financial information via links to online banking, entertainment, credit cards and even direct connections to their work networks, according to a condemnation of the Home Network Administration Protocol from Tenable Network Security. Meanwhile, a January 2013 study from Rapid7 found 40 million to 50 million network-enabled devices, including nearly all home routers, were vulnerable to exploits using UPnP. Is there any way to fix this target-rich environment?" If only there were an easily upgradeable open source router operating system to which vendors could add support for their hardware leaving long term maintenance to a larger community.

264 comments

  1. dd-wrt?? by neo8750 · · Score: 4, Informative
    1. Re:dd-wrt?? by Anonymous Coward · · Score: 5, Informative

      DD-WRT is based on the open source OpenWRT, but DD-WRT itself is proprietary.

    2. Re:dd-wrt?? by WRD-EasyTomato · · Score: 5, Informative

      Or try EasyTomato or any of the other Tomato variants (Toastman, Shibby, etc.). Super easy to install, has a pretty and easy to use interface, and it's all open source.

    3. Re:dd-wrt?? by Technician · · Score: 1

      If you have a home router, is it protected if it is behind the router built into many DSL or Cable modems? Your ISP may be protecting your firewall router by placing it behind another firewall router in your modem.

      A quick test to see if this may apply to you. view your router's status page and look at the IP address of the WAN connection. If the WAN connection is a 196.168.x.x number then your modem has a router too. Has anyone pen tested your modem router?

      --
      The truth shall set you free!
    4. Re:dd-wrt?? by unixisc · · Score: 4, Insightful

      How exactly does an average consumer put things like DD-WRT, or OpenWRT, or Tomato, or pFsense or m0n0wall on a router?

    5. Re:dd-wrt?? by whitroth · · Score: 5, Interesting

      First you have to find the right build of DD-WRT. This involves totally ignoring the router database, which, as one person's website put it, is either massively out of date at best, and *WRONG* at worst, liable to brick your router.

      And if you join the support forum, you discover people talking about their "favorite" builds, something in over 30 years in the field I've *NEVER* heard of. And they don't have formal releases, and regression tests seem to be mostly dependent upon the lead developers.

      Two months of fighting this, and debricking my router 2? 3? times, and I found one that did what I needed (that was to actually serve as a print server for a USB printer, as well as routing).. I have no idea how, or if, I'll be able to upgrade.....

                mark, sr. sysadmin, Linux/Unix

    6. Re:dd-wrt?? by jxander · · Score: 1

      Two months of fighting this, and debricking my router 2? 3? times, and I found one that did what I needed (that was to actually serve as a print server for a USB printer, as well as routing).. I have no idea how, or if, I'll be able to upgrade.....

      mark, sr. sysadmin, Linux/Unix

      Just FYI. If you can "debrick" something, than it's not bricked.

      --
      This signature is false.
    7. Re: dd-wrt?? by thinuspollard · · Score: 1

      Or try a RouterBoard/MicroTic based router. Runs Linux, great interface. Doesn't do ADSL, use a cheap modem for that. A tad expensive, but I got tired of comercial grade routers. This works for me and ymmv.

    8. Re:dd-wrt?? by SkunkPussy · · Score: 3, Interesting

      DD WRT has a history of GPL violations, so anyone who's cool doesn't use it!

      --
      SURELY NOT!!!!!
    9. Re:dd-wrt?? by msauve · · Score: 2

      Some devices may indeed be behind carrier NAT and be assigned RFC 1918 addresses. But that's more likely for mobile connections, and very unlikely for home DSL/cable ones - it would break all sorts of things because you have no control over inbound NAT.

      Also, you most certainly meant "192.168...". 196.168.x.x are public IP addresses. If a carrier were to use private IP space, they'd be much more likely to use 10. addresses.

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    10. Re:dd-wrt?? by msauve · · Score: 2

      Just buy it pre-installed. Buffalo offers that on some models (DD-WRT).

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    11. Re:dd-wrt?? by chipschap · · Score: 1

      Hmm ... my carrier (Hawaiian Telcom) uses 192.168... addresses in the router portion of the DSL modem. Supposedly you control NAT by settings made in the admin panel. Fortunately though you can set it to pure passthrough mode and run it into my nice Tomato router.

    12. Re:dd-wrt?? by msauve · · Score: 1

      I guess I wasn't clear on what the GP was describing? I've used cable modems which give out a single, public IP to the connected device with DHCP. It's really a bridge, not a router. I suppose some ISPs hand out devices which have private IP space behind them and provide a NAT gateway. But why would you put another NAT router behind one of those? If you simply want to add wireless, you'd simply ignore the wireless router's (I really hate calling those simple NAT gateways "routers") WAN port, turn off DHCP on it, and use it as an AP.

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    13. Re:dd-wrt?? by Cramer · · Score: 1

      Long ago, it was a fork of openwrt. Today it's almost nothing like it. And how the hell is ddwrt "proprietary"? The source is there; you can build it yourself. Yes, there are binary blobs in it due to manufacturers sitting on driver code. Yes, some platforms are commercial, but most aren't.

    14. Re:dd-wrt?? by Cramer · · Score: 1

      They do have formal releases, they're just uselessly WAY out dated. Their development model is far too complex, and IMO, haphazard. To be fair, they are building software for thousands of devices, most of which they don't have at hand to test -- not that they have the lab resources to actually do that level of testing. OpenWRT does things a bit better, in that it's much closer to a typical linux distro where you can choose what to install; of course, that makes is a difficult system to work with.

      Once you find something that (other people say) works... don't mess with it. I've not updated any of my WRT's in a long time.

    15. Re:dd-wrt?? by whitroth · · Score: 1

      That's fine... except I suggest you go there, or just google on debricking a router. It's the terminology.

                    mark

    16. Re:dd-wrt?? by AvitarX · · Score: 1

      I've not updated any of my WRT's in a long time.

      which brings us back to the OT.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    17. Re:dd-wrt?? by Cramer · · Score: 1

      a) It Works(tm). b) There are no published exploitable bugs in the builds I'm running. [and c) only one of them is actually connected as an internet router.]

    18. Re:dd-wrt?? by AvitarX · · Score: 1

      I'm sure your system is fairly secure, with probably minimum open ports (ssh maybe, lighthttp maybe, and the firewall itself I'd assume), if a problem were to be discovered, you may not be aware of it, and you would have trouble upgrading.

      Note, I have an Oleg firmware on an old Asus with a similar problem, I wasn't trying to be aggressive, but it is a problem, at least I perceive it as one for me.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    19. Re:dd-wrt?? by Technician · · Score: 1

      I am behind one, on DSL. I did not bypass it, but have admin privilages on the router section. I still use a consumer router after it because I don't know how effective it is. I could have used a simple switch to add more physical ports as the modem only has one LAN port. The DSL modem provides DHCP in the 192.168.0 range and my rounter is 192.168.0.2 to use the gateway in the modem.

      I did forward a port used by my PAP2T-NA so I can receive phone calls. Other than that, I left the firewall intact in both routers. I did turn off remote admin of the router and UPNP. I presume the ISP still has admin privelages of the modem section to set QOS on their end.

      --
      The truth shall set you free!
    20. Re:dd-wrt?? by Anonymous Coward · · Score: 0

      How exactly does an average consumer put things like DD-WRT, or OpenWRT, or Tomato, or pFsense or m0n0wall on a router?

      I use OpenWRT on my router. Providing your router is supported, it's simply a case of downloading the firmware and flashing it through your router's existing firmware.

    21. Re:dd-wrt?? by Cramer · · Score: 1

      It's a matter of keeping up with security notices. And as only one of them is an actual internet router (with as much turned off as possible), it's a minor vulnerability.

      (Now, my stack of Cisco IOS based devices... there's a ball of exploitability. currently, ntp being the pain in the ass to reign in.)

    22. Re:dd-wrt?? by mcrbids · · Score: 1

      Or, you could use a Router / company that supports DD-WRT out of the box....

      Bought mine online, love it, no issues, great reception, and perhaps $10 more than the N600 at the local Be$t Buy.

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    23. Re:dd-wrt?? by Anonymous Coward · · Score: 0

      Nah, I own a router that actually works and has no security issues. Don't need some hacky, half-working third party crap.

    24. Re:dd-wrt?? by whitroth · · Score: 1

      A day or so late, but unlike most slashdotters these days, here's the actual answer to your question:
            0. Do some research, and decide which F/OSS firmware distro will meet all your needs.
            1. Go to the home page, then find the release that's for your hardware, and d/l it to your system. I did
                        it to a netbook, rather than my workstation, for reasons in step 2.
            2. Connect a system to the router. MAKE SURE IT IS *N*O*T* on the Net. Turn off wireless, so that the
                        only connection between the router and the system is one wired cable.
            3. On your connected system, which has the d/l firmware, browse to the router (often 192.168.1.1, so put
                            that in as the URL: http://192.168.1.1/ and you'll get to your router's built-in webserver. It will have
                            a default password, if you haven't already reset that.
            4. Log into the router, and there will be an admistration, or some such, page, and on that page will be
                          the option to update your firmware. Point it to the file on your system that's the new firmware,
                          and follow the directions from the router info, and from the F/OSS firmware.

      Yeah, it took me almost as long to write this as it will take you to do it, once you've got the firmware file.

                            mark
                       

    25. Re:dd-wrt?? by sjames · · Score: 1

      Not really. Bricked simply means no way to recover it through ordinay effort. De-bricking generally involves opening it up, soldering in a JTAG connector and using that to re-flash the firmware.

      So if you can get it going using the TFTP update technique, it's not actually bricked. If your only option is JTAG, it's bricked.

    26. Re:dd-wrt?? by jxander · · Score: 1

      I can get behind that.

      I just see too many people who claim to have bricked some hardware, and needed to reboot to fix it. You are, for all intents and purposes, rebuilding a new device from the carcass of the old bricked one.

      --
      This signature is false.
  2. Has any work been done on.. by Anonymous Coward · · Score: 5, Interesting

    Pentesting the custom firmwares from projects like OpenWRT/DD-WRT/Tomato etc?

  3. Wow... misconfigured devices are insecure? by Anonymous Coward · · Score: 0, Funny

    Misconfigured devices are insecure? Who'd a thunk it.

    I'd vote that end users pose the biggest security threat to home networks, anyway.

    1. Re:Wow... misconfigured devices are insecure? by jythie · · Score: 4, Insightful

      If your product can not be reasonably or safely configured by its target market, then while it is tempting to blame the individuals, it is the manufacturer who has failed.

    2. Re:Wow... misconfigured devices are insecure? by jandrese · · Score: 4, Insightful

      A home router that is not by default secure on it's WAN side is defective.

      --

      I read the internet for the articles.
    3. Re:Wow... misconfigured devices are insecure? by Anonymous Coward · · Score: 0

      Sometimes you are stuck with whatever the ISP forces upon you. e.g. Modem + router combos *rentals only* with router functions that cannot be turned off.
      Enjoy your double NAT.

      There are *no* open source alternatives for modem + router gateway combos either because of the non-free nature of the modem binary blob even if your ISP gives you the choice of buying the modem from them.

    4. Re:Wow... misconfigured devices are insecure? by Anonymous Coward · · Score: 0

      The type of network I am talking about is Cable or VSDL where the ISP has to approve your modem before it would be on the network.

    5. Re:Wow... misconfigured devices are insecure? by Anonymous Coward · · Score: 1

      The failure is the whole notion that computers and technology should be "easy" for people to set up. Nobody insists that electrical circuits be designed for end users to be able to install and configure, nobody insists that plumbing be made so that every home user can just buy a garbage disposal and hook it up correctly themselves. Why in the hell do we think routers and computers should be easy. They aren't, and they never will be. It's complicated technology and if you don't understand it, you're going to fuck it up. That holds true no matter what we're talking about. So, in summary, not only is it "tempting" to blame the users, but it's appropriate.

    6. Re:Wow... misconfigured devices are insecure? by Anonymous Coward · · Score: 0

      I think the problem is that most end users don't understand enough to understand how they put themselves at risk by not having things done professionally. An end user may struggle for hours getting a router to work correctly, but the moment it appears to work, he feels successful and gets on facebook, never to think of it again. Since failure in security is invisible, he has no way of measuring his success. If you do your own mechanic work, chances are you know your mistakes shortly after making them. The same isn't so with networking.

    7. Re:Wow... misconfigured devices are insecure? by jxander · · Score: 2

      Not only that, but the device primarily in charge of transporting data is the most likely point of entry for malicious data.

      Who'da'thunk

      --
      This signature is false.
    8. Re:Wow... misconfigured devices are insecure? by jedidiah · · Score: 1

      If your ISP sticks you with inherenently insecure hardware then that's on the ISP. This is not a situation where they are powerless. This is yet another example of how you don't necessarily have to be an idiot. Better choices are possible. Saner engineering choices are possible.

      You don't have to (and you should not) tolerate crap.

      --
      A Pirate and a Puritan look the same on a balance sheet.
    9. Re:Wow... misconfigured devices are insecure? by mcgrew · · Score: 1

      Bullshit. If you're supplied with your ISP's router, simply buy a second one and plug your PCs and ISP router into your own. It's yours, you can block traffic with it even if the one feeding it can't.

      Where did all the nerds go?? Way too many normals here these days who are anti-science and technology and ignorant of both.

  4. PFsense by johneee · · Score: 4, Informative

    I have PFSense running on a virtual server, which I recommend to anyone. Perhaps not on the virtual server... it kind of adds a layer of complication that most people probably wouldn't care for, but it works well enough.

    http://www.pfsense.org/

    Hopefully no huge flaw comes out on that without me noticing. That would be embarrassing.

    --
    - ------- There are ten kinds of people in the world. Those who understand binary, and those who... Huh?
    1. Re:PFsense by Spazztastic · · Score: 3, Interesting

      I really liked pfSense but when I used it long ago it was very buggy. It may be time for me to give it another try. However, if you're familiar with the Cisco IOS CLI, Vyatta is another solution. I plan to set up a small low power box to be my router and only use my Linksys Router/AP combo (flashed with DD-WRT) as an access point. It gives you far more options in terms of management, and if you happen to seed a lot of Linux ISOs you don't have to worry about filling up the memory with the routing table.

      --
      Posts not to be taken literally. Almost everything is sarcasm.
    2. Re:PFsense by Xenna · · Score: 3, Interesting

      Yeah, I've been running that stuff for years after getting frustrated with commercial routers. Has been extremely stable.

      Of course, being lazy I got it in appliance form from this place:
      http://www.applianceshop.eu/in...

      "Hopefully no huge flaw comes out on that without me noticing. That would be embarrassing."

      Ultimately it's a matter of (perhaps misguided) trust...

    3. Re:PFsense by carnivore302 · · Score: 4, Informative

      I second that. PFSense is rock solid and comes with a lot of features. Dual wan, vpn, you name it.

      Just as lazy... also got mine from applianceshop.eu.

      --
      Please login to access my lawn
    4. Re:PFsense by FictionPimp · · Score: 2

      I highly recommend the Ubiquiti EdgeMax Router lite. It's 99 bucks and runs a variant of Vyatta. Great little product.

    5. Re:PFsense by johneee · · Score: 2

      If I remember correctly, I tried Vyatta, and because I don't know IOS, I flamed out trying to configure it.

      PFSense was only marginally more difficult than OpenWRT, so it kind of suited my level of expertise.

      With it being on a VM, it means that I have one box that is my router, file server, media server, and experimentation box all in one, which is convenient for me.

      It does mean that the hypervisor is - in theory - exposed to the net, but since it never communicates externally except through the router software, it has basically no attack surface, so it shouldn't be too much of an issue. (he said hopefully) \

      --
      - ------- There are ten kinds of people in the world. Those who understand binary, and those who... Huh?
    6. Re:PFsense by Spazztastic · · Score: 1

      Thanks, I may look into this. It'll be cheaper less expensive than the one I had originally spec'd out on Newegg.

      --
      Posts not to be taken literally. Almost everything is sarcasm.
    7. Re:PFsense by Spazztastic · · Score: 1

      There's a learning curve with Vyatta but once you catch on it's pretty easy. There's also plenty of guides online that'll get you started and a very friendly community.

      I didn't like the web interface of pfSense, and at the time of using it I was still pretty green with the Linux CLI so using that wasn't as much of an option. From what I can see there have been improvements, plus it's also been 7~ years since I used it, so I might give it a shot in a VM.

      --
      Posts not to be taken literally. Almost everything is sarcasm.
    8. Re:PFsense by swb · · Score: 1

      That's how I run it, too, although I agree that there can be complications if your VM environment has a hiccup and you need Internet connectivity to fix it. A couple of times I've found myself hauling out an old broadband router and jacking it into my cable modem so I could fix something.

      Do you run it with a dedicated WAN NIC, or do you use a VLAN?

      I use a VLAN which I assume might be some kind of slight vulnerability, but there's no management interfaces on any device for that VLAN which I'm guessing adds some margin of security.

    9. Re:PFsense by Foresto · · Score: 1

      The Ubiquiti stuff looks pretty sweet, but I don't think EdgeOS is open source. What's their track record of bringing updates to old products? Can anyone outside of Ubiquiti audit the code?

    10. Re:PFsense by johneee · · Score: 1

      Dedicated. Seemed easiest, and the motherboard has two ethernet ports, so there wasn't any extra cost.

      --
      - ------- There are ten kinds of people in the world. Those who understand binary, and those who... Huh?
    11. Re:PFsense by Anti-Trend · · Score: 1
      Been there, done that. pfSense isn't bad, really; just the implementation has some ugly hacks under the hood that make edge cases exceptionally painful, and pf itself (the filter for which pfSense is named) isn't the best for scalability. It's probably fine for most users though -- certainly better than your typical lowest-bidder, unpatched firmware image from who-knows-where. I ran pfSense for years -- I guess about 5 -- and wrote an article about it not too long ago. Eventually moved to a low-power Atom 1U and VyOS (brand new community fork of Vyatta, which Brocade has essentially killed off). I'm very happy with the results.

      ...if you're familiar with the Cisco IOS CLI, Vyatta is another solution...

      Vyatta/VyOS are actually a lot closer to JunOS syntax, FYI. Which is good, since recent IOS syntax makes less sense than ever.

      If you're not the DIY type, there's also Ubiquiti, who has their own fork of Vyatta called EdgeOS. Ships standard on all their EdgeMAX routers.

      --
      Working in a DevOps shop is like playing in a band made up entirely of keytarists.
    12. Re:PFsense by mgcarley · · Score: 1

      They're updating EdgeMax every few months - 1.4.0 came out just a few weeks ago. As far as code is concerned, it seems to be sitting on top of vyatta with a mini install of Debian (MIPS) so it should be fairly straightforward for anyone who has ever used Linux CLI.

      As far as any other proprietary stuff is concerned it would seem that, if at all, anything "proprietary" would probably be mostly UI stuff, but even that can be replaced if you really want (there seem to be a couple of projects floating around). You can install anything in the Debian repos (I usually start with nano and for a while I used darkstat but I now run cacti on a separate server and retrieve everything by snmp).

      While most of the system is open-source/using FOSS components (that is to say, the entire underlying system is Open Source), is it really *necessary* to have everything 100% FOSS or would you rather have something that is 90-95% FOSS and that which isn't "just works"?

      --
      Founder & COO, Hayai India (hayai.in) / USA (hayaibroadband.com) // t: @mgcarley
    13. Re:PFsense by Foresto · · Score: 1

      I prefer open source over a black box mainly to avoid two problems: unverifiable security and abandonware. If Ubiquiti can convincingly show that all security holes are patched before or promptly after someone discovers them, and continue to do so until I no longer have use for the product, then I'm fine with proprietary. I don't know know how they would accomplish the former, though, and so few companies choose to do the latter that I'm skeptical.

    14. Re:PFsense by mgcarley · · Score: 1

      I understand where you're coming from, but the devices are not black boxes. As I mentioned, the devices operate using a collection of open-source software (Debian MIPS & Vyatta) and presumably can be hacked/upgraded/fiddled with to your hearts content if you so desire.

      As I also mentioned, IF ANYTHING probably it's only the GUI that is closed, but having not bothered to check on my own devices I don't know whether it actually is or is not. Considering however that the functionality you're referring to is in the core system (which appears to be OSS), what you're describing seems largely to be a non-issue - you can SSH in to the device and see a good old mostly-standard Linux CLI.

      I can and have successfully installed other debian packages on it just by running apt-get, so, as long as the debian repos are up-to-date, I have no reason to suspect that the software on my own ER is not also up-to-date.

      --
      Founder & COO, Hayai India (hayai.in) / USA (hayaibroadband.com) // t: @mgcarley
  5. opensource firmwares not perfect either by Anonymous Coward · · Score: 2, Interesting

    I bet everyone is busy writing smug comments about closed source firmwares, but let's not forget that DD-WRT have had a similar bug. http://www.xtremesystems.org/forums/showthread.php?230880-Massive-DD-WRT-Security-Hole-%28Unauthenticated-Root-Control-Possible%29

    1. Re:opensource firmwares not perfect either by compro01 · · Score: 4, Insightful

      The important difference being that bug was fixed, as opposed to being left wide open forevermore.

      --
      upon the advice of my lawyer, i have no sig at this time
    2. Re:opensource firmwares not perfect either by Minwee · · Score: 5, Insightful

      In fact, it was even fixed for devices which are no longer in production with no need for the original vendor to even still be in business. Open source is funny that way.

    3. Re:opensource firmwares not perfect either by Anonymous Coward · · Score: 0

      "Open source" is not ATTEMPTING perfection any more than science is attempting truth. The peer review is everything.

    4. Re:opensource firmwares not perfect either by Anonymous Coward · · Score: 0

      AFAIK, that bug was patched in something like an hour after it was brought to their attention.

  6. Why I buy apple airports by goombah99 · · Score: 4, Interesting

    I don't actually know if it matters or not but I prefer Apple over other wireless routers because it's so damn braindead easy to keep them patched. Apple just pushes out firmware updates (rarely). Every other router I've owned it was a struggle to figure out if it needed a patch, how to do it. Moreover it was a source of worry even when there wasn't a problem which alone was worth any relatively small cost differential.

    --
    Some drink at the fountain of knowledge. Others just gargle.
    1. Re:Why I buy apple airports by Anonymous Coward · · Score: 4, Funny

      Apple is the next thing to godliness. Praise Apple. I wish I was an Apple. Eat me.

      [NO CARRIER]

    2. Re:Why I buy apple airports by jythie · · Score: 4, Insightful

      Eh, to be fair, this is something they are doing right and a lot of manufacturers are not. Techie types sometimes freak out over being automatically patched with who knows what, but for the vast majority of users (including techie types), it is a good strategy.

    3. Re:Why I buy apple airports by dreamchaser · · Score: 1

      It's a terrible strategy for any technical person. New bugs can be introduced. For a techie type, being able to test out new updates prior to rolling them into production is a must.

    4. Re:Why I buy apple airports by syzler · · Score: 1

      And number of techie types that actually manage consumer grade routers for businesses, I would guess, is an extremely small cross section of techie types. Most businesses that actually employ a technician probably use at least something along the lines of a Juniper SRX as the public router. The point still stands, that automatic firewall updates is a good idea for the vast majority of consumers and techie types (just not in their professional arena). I must confess, that I have been using the Apple base stations for nearly a decade for home use. My business uses a Slackware Linux router, and Junipers for our clients.

    5. Re:Why I buy apple airports by ColdWetDog · · Score: 1

      You realize, of course, that you don't have to update. It just notifies you. I like that little feature of the Apple routers (and OS X and iOS). Given that Apple, like every other vendor on this planet at least, pushes out updates that occasionally break things (Hi Microsoft!), I don't upgrade the moment the patch is available. I wait a week or so unless there is some overwhelming reason like some nasty exploit.

      Yes, it's not perfect. No, nobody is perfect. As has been mentioned on this thread and countless others, computer technology is insufficiently mature and it's a big problem giving $randomUser more computing power that existed on the entire planet a couple of decades ago.

      Sic Transit Gloria Mundi

      --
      Faster! Faster! Faster would be better!
    6. Re:Why I buy apple airports by j+h+woodyatt · · Score: 1

      Another feature of the AirPort home gateway product line is that it doesn't have any UPnP support, which is the attack surface that has been proven to be so difficult to secure. It also doesn't have an embedded web server for administration and configuration, using instead a proprietary Apple protocol between the firmware and the AirPort Utility rich client program that runs on OS X, iOS and Windows. The attack surface on the AirPort home gateway is really small compared to other products.

      Too bad Apple will probably never make another one.

      --
      jhw
    7. Re:Why I buy apple airports by Anonymous Coward · · Score: 0

      Too bad Apple will probably never make another one.

      Er, what? Apple recently (less than 1 year ago) introduced a completely redesigned AirPort Extreme / Time Capsule. It has a different physical design (vertical tower instead of flat pancake, and it has a cooling fan this time around), adds 802.11ac radios, was upgraded to a completely new SoC with a dual-core Cortex-A9 CPU, and so on. It doesn't seem to be a dead product line at all.

  7. Sigh - what the heck ... by udippel · · Score: 3, Informative

    I feel that all those links to WRT/PFSense/M0N0Wall/Tomato/etc are kind of redundant.
    Sufficient to understand, that the underlying concept of UPnP is an abomination; a sick and distorted concept that deserves nothing less than an immediate death sentence, and to be buried along with The Funniest Joke In The World; never to be resurrected again.
     

    1. Re:Sigh - what the heck ... by drinkypoo · · Score: 3, Insightful

      Sufficient to understand, that the underlying concept of UPnP is an abomination; a sick and distorted concept that deserves nothing less than an immediate death sentence, and to be buried along with The Funniest Joke In The World; never to be resurrected again.

      So how do you propose that my game on a machine on NAT arranges to receive UDP through the firewall? I'm supposed to manually configure firewall rules for each game? And then change them all if my IP changes?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:Sigh - what the heck ... by Imagix · · Score: 3, Informative

      IPv6.

    3. Re:Sigh - what the heck ... by Anonymous Coward · · Score: 3, Funny

      Well, speaking on behalf of other posters here - you are probably supposed to spend all of your time configuring some linuxy version of iptables or some such on a custom router. Then you won't have to worry because you won't have time to play your game...

    4. Re:Sigh - what the heck ... by drinkypoo · · Score: 0

      Neither my ISP nor any game I can think of actually supports IPv6. So you want me to pay for a tunnel, too? Because I'm not going to try to game over a free tunnel.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    5. Re:Sigh - what the heck ... by Imagix · · Score: 3, Funny

      Incentive to pressure your ISP to support a well over a decade old technology, going on two decades.

    6. Re:Sigh - what the heck ... by 0123456 · · Score: 3, Informative

      So how do you propose that my game on a machine on NAT arranges to receive UDP through the firewall?

      So go for convenience over security. But don't then complain when you install VNC on your PC and it automatically opens a port allowing everyone on the Internet to access it, and you didn't bother to set a password so your PC is now pwned by the first script kiddy who scans your router.

      UPnP is simply insane from a security standpoint. Random applications should not be opening random ports without explicit permission.

    7. Re:Sigh - what the heck ... by drinkypoo · · Score: 4, Insightful

      Incentive to pressure your ISP to support a well over a decade old technology, going on two decades.

      I have no viable alternatives. The ISP I'm using now is the best of three shitty options. I live in the USA, did you think I lived in the first world or something?

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    8. Re:Sigh - what the heck ... by harrkev · · Score: 1

      What is the problem with UPnp??? From what I understand, UPnP works like this:

      1) All devices inside the local network are considered "trusted"

      2) Trusted devices can poke holes in the firewall pointing only back to themselves.

      Assuming that UPnP is implemented properly, and assuming that an attacker is on the outside of the local network, there is nothing for an attacker to grab on to. Now, if an attacker is on the INSIDE of your LAN, then you are already boned.

      What am I missing?

      --
      "-1 Troll" is the apparently the same as "-1 I disagree with you."
    9. Re:Sigh - what the heck ... by udippel · · Score: 2

      While your logic looks okay at a first glance, it doesn't at a second.

      When a government has thousands of enraged citizens running towards the government building to set those on fire and loot them, some machine guns might be the means of choice. Though it ought to have been considered by the government du jour, what the reaction of the public will be, with the introduction of strict austerity measures, as well as jus primae noctis?

      There is no fundamental reason, really, to have 1000 games opening 1000 different ports for endless protocols on a home router. Strange enough, one can invite the whole world, chat with billions of people, even tell every other citizen of this world whatsapp, and needs only http. Just to give an example.
      Do not support the laziness of game coders.

      A firewall that can be configured arbitrarily by user applications on their request is about the worst hack possible to connect securely to another network.

    10. Re:Sigh - what the heck ... by 0123456 · · Score: 4, Informative

      What am I missing?

      Again, used to be that the most common way for a Ubuntu machine to get pwned was for the user to install VNC with UPnP enabled. They only wanted to connect over their LAN, but VNC went and opened a UPnP port, and... oops.

      Every new port opened on the router is a potential new security hole.

    11. Re:Sigh - what the heck ... by harrkev · · Score: 1

      Ahhhhh. That make sense. Thanks.

      --
      "-1 Troll" is the apparently the same as "-1 I disagree with you."
    12. Re:Sigh - what the heck ... by udippel · · Score: 1

      Reality. What users have in their PCs is not "Trusted Computing" - well, well, I know this is what the monopolist told everyone. But it surely isn't.
      If all the applications running on a PC were actually trusted, a firewall would not be necessary (aside from the odd closure of ports offering internal content only, like 137-139, 3306, etc.; and this can be done by static rules).
      No serious firewall can allow any user to reconfigure it.

    13. Re:Sigh - what the heck ... by Minwee · · Score: 4, Insightful

      What is the problem with UPnp??

      All devices inside the local network are considered "trusted"

      I really think you just answered your own question there.

    14. Re:Sigh - what the heck ... by jandrese · · Score: 1

      Wasn't the problem something like a script injection attack on a webpage can open up any random port on your router?

      --

      I read the internet for the articles.
    15. Re:Sigh - what the heck ... by clarkn0va · · Score: 4, Insightful

      Mod parent up. UPnP is insecure by design. It's very purpose is to take security and control out of the hands of the user, and put it squarely in the hands of whatever happens to be running on your network.

      It's too bad that most people don't understand enough about network security to configure their own router, and a double shame that the kludge we call NAT has further broken network applications, but convenient "workarounds" like UPnP could only ever lead to problems like the summary lays out.

      --
      I am literally 3000 tokens away from the chaotic crossbow --Stephen
    16. Re:Sigh - what the heck ... by clarkn0va · · Score: 1

      if an attacker is on the INSIDE of your LAN, then you are already boned.

      What am I missing?

      There are varying degrees of boned. UPnP lets the black hat turn a small exploit into a big one.

      Assuming that UPnP is implemented properly

      Well yes, there's that too.

      --
      I am literally 3000 tokens away from the chaotic crossbow --Stephen
    17. Re:Sigh - what the heck ... by xvan · · Score: 1

      No, unless you have java or another shit like that... I can't think why a browser would need to open a listening port.

    18. Re:Sigh - what the heck ... by tlhIngan · · Score: 1

      Sufficient to understand, that the underlying concept of UPnP is an abomination; a sick and distorted concept that deserves nothing less than an immediate death sentence, and to be buried along with The Funniest Joke In The World; never to be resurrected again.

      So how do you propose that my game on a machine on NAT arranges to receive UDP through the firewall? I'm supposed to manually configure firewall rules for each game? And then change them all if my IP changes?

      Suffice it to say, most games don't need UPnP nor special firewall configuration.

      Thanks to techniques like STUN, NAT traversal is made simple. For the most part, most NATs appear as "STUN Open" which mean a little trickery on the developer ensures two NATs can connect to each other. Of course, it requires an external matchmaking server, but those tend to be used anyhow for discovery.

      I know I never had to do anything on my router (other than disable UPnP and all that) and I still can play via PSN and Xbox Live, and Steam, etc.

      And I haven't had to touch firewall port settings in ages - usually just at the beginning to map in services like SSH and whatnot.

      IPv6

      Sorry, IPv6 isn't magic. In fact, you're probably going to run into even MORE connectivity issues with IPv6 than IPv4+NAT. Why? Because guess what? Practically all IPv6 endpoints are going to be firewalled by a gateway device. So you still have to create firewall rules (oh, and good luck when the IP changes either by prefix or when it's auto-generated!) to let your game/etc pass. And we'll be back to the same old troubles of spending hours debugging because someone's firewall isn't behaving.

      So I'm guessing we're still going to need STUN to get through IPv6 firewalling.

      And that's the problem with IPv6 - you still end up with the same headaches, multiplied because debugging is now made much harder (you can ping your IPv6 gateway? Good. That means absolutely zip because it could be using the default link-local route and address over the global prefix).

      IPv4+NAT is nasty, but it works, and is easily understood compared to IPv6. NAT also has the nice side effect of isolating internal network addressing from external, so should prefixes and such change, nothing bad happens and things don't need sudden reconfiguration because of it (firewall settings ossify - if your prefix hasn't changed in a couple of years, when it does and things break, it's a huge PITA to re-find where everything is again).

      Of course, those arguing for "purity" of IPv6 probably hold back development of stuff like NAT-PT and other things that could've had us on IPv6 years earlier.

    19. Re:Sigh - what the heck ... by devman · · Score: 1

      I play a lot of online games. I have had UPnP disabled on every network gateway I've owned precisely because it is ridiculously insecure. I have yet to find one that doesn't work properly with UPnP disabled. The only exception to this is when I was running a CS:GO server awhile back I had create port forwarding rules so clients could connect, but setting up dedicated servers on residential networks isn't something non-advanced users do.

    20. Re:Sigh - what the heck ... by dreamchaser · · Score: 2

      Configuring port forwarding is trivial on virtually any firewall, so yes, that's what you need to do if you want security.

    21. Re:Sigh - what the heck ... by drinkypoo · · Score: 1

      So go for convenience over security. But don't then complain when you install VNC on your PC and it automatically opens a port allowing everyone on the Internet to access it, and you didn't bother to set a password so your PC is now pwned by the first script kiddy who scans your router.

      You don't know me very well. If I am to remote into Windows I use RDP, and if I permit it at all it's only to the local network. And for all my statements that network transparency is irrelevant to most X users, if I want to remote Unix, I'll use an ssh tunnel. Sure, uPnP is a minefield for novices. But for me, it's immensely useful. Also, on Windows XP or later, VNC won't just magically open up your machine. Windows will ask you if you want to permit network connections to VNC, and it's up to you to decide what to do about it. You can, in fact, configure the windows firewall to only permit connections from your local network. This is the default for most services on Vista and later.

      uPnP is a wonderful source of opportunities for malicious hackers, but given some awareness of network security it need not in fact actually present a usable attack vector. My lady, my only user, is smart enough to ask me what to do if she gets a prompt she doesn't recognize. This puts her above, by far, the vast majority of non-power users.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    22. Re:Sigh - what the heck ... by Anonymous Coward · · Score: 0

      Yes. You're supposed to know how routing works if you want to administer a secure router.

    23. Re:Sigh - what the heck ... by drinkypoo · · Score: 1

      There is no fundamental reason, really, to have 1000 games opening 1000 different ports for endless protocols on a home router.

      In a perfect world, all of those games would communicate using the best possible protocol, and all communications would be cleared through a central facility. Problem is, "best" can be defined in many ways. Thus, we have all games using the same underlying protocol, but then building protocol on top of protocol in order to carry out their communications in the way that makes the most sense to the developers (or whoever drew up the architecture at the time, which might have been a schizophrenic hive-mind of whoever wandered by at the time and contributed some code) at the time. And all of those communications are cleared through the peer to peer network stack, which I then have the convenience of using with uPnP. Which, if you think about it, is just dynamic routing on a tiny scale. And if I wanted to, I could in fact protect uPnP cryptologically so that no unauthorized hosts could make requests, and I could diddle the daemon to refuse requests I didn't think it should be approving. But in practice, I'm just not having those kind of problems because I'm making other intelligent decisions.

      A firewall that can be configured arbitrarily by user applications on their request is about the worst hack possible to connect securely to another network.

      It's not arbitrary, it's not allowed to just forward anything to anywhere.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    24. Re:Sigh - what the heck ... by idontgno · · Score: 2

      Then you won't have to worry because you won't have time to play your game...

      Nah. You've just changed the game you're playing.

      XD

      I'm not sure how you win "iptables", but I'm not real sure how you win a lot of the games out there, so it's probably similar.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    25. Re:Sigh - what the heck ... by Ksevio · · Score: 1

      Well there's the old NAT-PMP, though not many support that. The real answer is IPv6, but then the game needs to support it and all the players.

      Some games can do NAT hole punching.

    26. Re:Sigh - what the heck ... by Anonymous Coward · · Score: 0

      If you think the NAT on your CPE is bad... wait until your ISP implements CGN...

      Also, I am surprised no one has touted the Open Home Gateway Forum...

      or pushed for more security in CableLab's DOCSIS 3.0... or in the IETF's homenet WG.

    27. Re:Sigh - what the heck ... by Anonymous Coward · · Score: 1

      I'm not sure how you win "iptables", but I'm not real sure how you win a lot of the games out there, so it's probably similar.

      Iptables is like The Sims. You spend hours setting it up, then watch packets bounce off walls and get trapped by shrubbery.

    28. Re:Sigh - what the heck ... by nestler · · Score: 2

      Use static DHCP on your DHCP server and a UDP port forward. Your IP won't change (due to static DHCP which always gives the same IP address to a given Ethernet address) so it should never need to be updated. This is pretty straight forward with Tomato firmware.

    29. Re:Sigh - what the heck ... by Mryll · · Score: 1

      It's nice to see somebody answer a question without being a dick :)

    30. Re:Sigh - what the heck ... by jxander · · Score: 1

      At least you have 3 shitty options. I'm limited to a single shitty option.

      --
      This signature is false.
    31. Re:Sigh - what the heck ... by Bengie · · Score: 1

      The reasoning is that devices on the local network cannot be trusted and the user should enforce security via the admin explicit poking holes instead of letting the computer, which is untrusted, to poke holes.

      Unfortunately, the weakest link isn't the computer, but the users. Unless you plan on telling the users what they can or cannot do, there is no point in using a "secure" approach because the first time the end user gets frustrated trying to configure their router, is that last time they will purchase that router and the first time they will disable all security in an attempt to make everything work.

    32. Re:Sigh - what the heck ... by SkunkPussy · · Score: 1

      Isn't it the case that any application you install on your computer can secretly open a upnp connection through your firewall to your computer without you being aware of this?

      --
      SURELY NOT!!!!!
    33. Re:Sigh - what the heck ... by Anonymous Coward · · Score: 1

      You should assign IPs by mac address using address reservation.

    34. Re:Sigh - what the heck ... by j+h+woodyatt · · Score: 1

      > So how do you propose that my game on a machine on NAT arranges to receive UDP through the firewall? I'm supposed to manually configure firewall rules for each game? And then change them all if my IP changes?

      Ladies and gentlemen, I give you Port Control Protocol [RFC 6887].

      --
      jhw
    35. Re:Sigh - what the heck ... by TyFoN · · Score: 3, Informative

      Got to love competition mandated by law.

      In my area, 15 minutes from the closest city which has about 60.000 inhabitants, I have about 20 providers competing on fiber, cable and copper. You can also toss in a few 4g providers that sell broadband you can carry around.
      I settled for fiber 100/100 with tv and phone for $100 a month. It's not the cheapest, but I'm hooked on the speed :)
      They also provide ipv6 and "bridge mode routers" with a fixed ipv4 address for my own router and a /62 ipv6 prefix.

      We used to have a public telephone company called Telenor, but after it became private it came with the catch that all competitors can buy capacity from them at cost + investment write-offs. It's been working wonders.

    36. Re:Sigh - what the heck ... by Bengie · · Score: 1

      nice side effect of isolating internal network addressing from external

      Which sounds great until two companies merge and they have conflicting IP addresses. In a properly designed and configured network, using IPv6, you can merge all of the networks you want and not have to worry about IP address renumbering.

      The biggest benefit of NAT isn't NAT, it's the stateful firewall, which can easily be exactly mimicked with a firewall+IPv6 setup. with IPv6, you shouldn't be hardcoding the prefix into rules if the prefix may change. Also, "if your ip changes"? With IPv6, the standard is that the outgoing IP changes every 15 minutes that refuses incoming connections. The only IP that stays the same is "public" address and that one accepts incoming connections, but is not normally used for WAN destined traffic. The "temporary" IP address should be the default case for outgoing connections.

      http://tools.ietf.org/html/rfc4941

    37. Re:Sigh - what the heck ... by Bengie · · Score: 1

      You should try some of the many console games that use peer-to-peer. Most PC games connect back to a central server, so no forwarding needed, but many console games have the clients connect directly to each other to keep server costs down. Even if you play console games that don't do this, it's only you anecdotal evidence. There are large numbers of games that need ports opened, and many require quite a few ports. You never know which port it will choose, so you either need to open a large port range or let uPNP do it on demand.

    38. Re:Sigh - what the heck ... by msauve · · Score: 1

      "any application you install on your computer can secretly open a upnp connection through your firewall to your computer without you being aware of this"

      How is that any different than a non-uPnP application opening a (HTTP/S, SSH, telnet, whatever) connection to a botnet command-and-control?

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    39. Re: Sigh - what the heck ... by Anonymous Coward · · Score: 0

      The NSA/GCHQ cannot eavesdrop IPv6 so well so the adoption has been and will be squashed. And THAT is the real reason why IPv6 hasn't taken off.

    40. Re:Sigh - what the heck ... by Bengie · · Score: 1

      That's great until you have several people playing the same game and you don't know which port will go to which device until run-time. Bad program design? Yes, but what are you going to do about it? you must support this case when you're talking about a general idea that must work for everyone.

      The reason for this many times is that if you have several people sharing the same IP all using the same program and all of them need to accept an incoming port but it can't be the same port, how is the program supposed to know which port it's assigned? It can't, unless you config the program some how, but most end users don't know what a port even is. what ever solution you propose, it should be 100% transparent to the end user.

    41. Re:Sigh - what the heck ... by Bengie · · Score: 1

      This is how UPNP works. People are saying UPNP is bad, which means they also think PCP is bad.. "Drugs are bad, m'kay"

    42. Re:Sigh - what the heck ... by devman · · Score: 1

      One could also DMZ the console, which is safer than enabling UPnP.

    43. Re:Sigh - what the heck ... by j+h+woodyatt · · Score: 1

      They're wrong.

      Misfeatures of UPnP: A) only for IPv4/NAT gateways; B) proprietary specification; C) defined as profile of SOAP over UDP (so very wide attack surface); D) allows every client to make 3rd-party port maps by default (so very insecure by design).

      Corrections in PCP A) works for IPv4/NAT and IPv6 gateways (NAT and w/o NAT); B) open IETF specification; C) defined as simple binary protocol (so very narrow attack surface); D) disallows 3rd-party port maps unless optional extension implemented (so less insecure by design).

      You need something that does this if you have a firewall (whether there is NAT or not). If you have an IPv6 gateway, then see RFC 6092 section 3.4 Passive Listeners for an explanation. That RFC is referenced by CableLabs and BBF specs, so it is what you should expect to see in most provider-provisioned home gateways in the near future.

      Seriously, PCP is what you need to use for this. Does this suck? Maybe. Depends on whether you think having firewalls everywhere denying all inbound traffic to passive listeners by default is a good idea. If you think that's a good idea, then PCP doesn't suck. Deal with it.

      --
      jhw
    44. Re:Sigh - what the heck ... by drinkypoo · · Score: 1

      Isn't it the case that any application you install on your computer can secretly open a upnp connection through your firewall to your computer without you being aware of this?

      On my Linux system, yes. That is the case. On Windows since XPSP2 with default configuration, only if you install it with Administrator rights. If you run an exe from your own account, no.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    45. Re:Sigh - what the heck ... by drinkypoo · · Score: 1

      Seriously, PCP is what you need to use for this.

      No, PCP may be what I'd like to use, but uPnP is what I have to use in both major senses of the word because it's what is supported.

      Or I could do as many slashdotters suggest and make my rules manually. But I don't want to. The computer works for me, not the other way around. If I start having a big PITAfest I just run away and do something else. If I'm paid, it's another story. If someone wants to pay me to do something that they would better do another way, it's their quatloos.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    46. Re:Sigh - what the heck ... by Anonymous Coward · · Score: 0

      > UPnP is insecure by design.

      I can't get people who say this to give me a straight answer to the following questions. Perhaps you will be the first:

      Is UPnP port forwarding more insecure than giving each machine on your LAN a globally-routable IP address? If so, why? If not, why not?

    47. Re: Sigh - what the heck ... by Anonymous Coward · · Score: 0

      You are clueless.

    48. Re:Sigh - what the heck ... by Anonymous Coward · · Score: 0

      ...first world...

      New World. Old World, New World, Third World. Why is this so difficult for Slashdorks to get right?

    49. Re:Sigh - what the heck ... by Anonymous Coward · · Score: 0

      > D) allows every client to make 3rd-party port maps by default (so very insecure by design).

      Miniupnp's default configuration requires that the requesting machine only install port maps that map back to itself. Given the number of explotable implementation bugs that have been discovered in other UPnP daemons, you'd be crazy to use anything other than a recent version on your CPE.

      > C) defined as profile of SOAP over UDP (so very wide attack surface)

      What is there to attack? Any vendor who's not crazy will
      a) use a battle-tested XML parsing library (or, just use miniupnp)
      b) not let their UPnP daemon listen on the WAN

      I agree that automated firewall hole punching could be useful for IPv6. (Though, on my networks, I forward everything other than CIFS and leave it to the machines on the network to decide their firewall policies.) I also agree that having a published IETF spec is useful. However, the UPnP spec appears to be freely available: http://upnp.org/sdcps-and-certification/standards/ , so it's not like UPnP is some inimplementable "standard".

    50. Re:Sigh - what the heck ... by antdude · · Score: 1

      Where is this? Lucky punk you are!

      --
      Ant(Dude) @ Quality Foraged Links (AQFL.net) & The Ant Farm (antfarm.ma.cx / antfarm.home.dhs.org).
    51. Re:Sigh - what the heck ... by Anonymous Coward · · Score: 0

      Well, World of Warcraft supports IPv6, surely you have heard of that one at some point... Still, many don't which is rather sad given how easy it is to port code to support it. Also, just about any location in the US is covered by Comcast, or will be soon if not. They support IPv6, and if your current modem/router from them doesn't, I'm sure you can just call them up and ask for a new one, they actually are pretty good about supplying customers with new modems and such.

      Ultimately, my point is, you likely DO have options, so don't sit here and pretend it is hopeless and cannot possibly happen, ever.

    52. Re:Sigh - what the heck ... by blackiner · · Score: 1

      UPnP is a little less secure, IMO. I only dabble in networking as a hobby so perhaps someone else in here more knowledgable can correct me, but the main reason is: stateful firewalls.

      A host with a public address behind a well configured firewall will have all incoming data dropped from any ports by default. Only established connections will be allowed in from the external network, which means the computer behind the firewall will have had to have sent something first. Furthermore, if you are *really* paranoid, you can have the firewall automatically drop everything automatically, regardless of the state of the connection, and then set up specific rules to allow certain types of connectivity (ie: only allow traffic to be returned into the internal network if it originated from the external server's port 80... and you can make it as arbitrarily complex as you want).

      UPnP on the otherhand just tells the router, "Hey, open this port, and send anything that arrives on it to me!", and then *everything* sent to that port from the external network will then be routed to the internal network, regardless of whether a connection had been established or not. This is necessary if you are hosting a server behind your firewall, but with UPnP it can happen rather transparently, without the user even knowing it is going on, wheras with a mere firewall, you will have to consciously go in and change the rules to allow incoming traffic from a certain port.

    53. Re:Sigh - what the heck ... by Agripa · · Score: 1

      I have actually gone backward with AT&T. I had IPv6 through tunneling for years but in the past few months AT&T started blocking protocol 41 so native IPv6 tunneling is no longer possible. Coincidentally they started blocking it about the same time that they started selling upgrades to support it.

    54. Re:Sigh - what the heck ... by Anonymous Coward · · Score: 0

      You're aware that if you're running UPnP-enabled software on your machine, and it asks your router to forward a port to that machine, but that machine is configured to drop all traffic sent to that port, then all traffic sent to that port on that machine by the router will be dropped, right?

    55. Re:Sigh - what the heck ... by udippel · · Score: 1

      Configuring port forwarding is trivial on virtually any firewall, so yes, that's what you need to do if you want security.

      I hope you don't believe this yourself!
      Port forwarding is the exact opposite of security. Though it it much better than UPnP, because at least you know what you do, and you're responsible when everything is pwned within a minute or a day.

      Security starts when you have a proper appliance with enough physical network interfaces and you set up a proper DMZ. Then you can run all your cr***y applications of all sorts with all ports open, and all your console apps, and still sleep well.
      In the DMZ, of course!!

    56. Re:Sigh - what the heck ... by blackiner · · Score: 1

      Depends... many consumer versions of OSs have very lax firewall configs by default. It may very well allow it. I certainly have never had to open the port when running transmission on Fedora, it seems like it just allows it regardless. And on Windows you get those little *this application wants to connect to the internet* popups, and if you hit allow it opens up the firewall for that app, for ALL ports I believe. And, I have sat there and not hit the button, and it looks like it just allows the traffic anyway.

    57. Re:Sigh - what the heck ... by drinkypoo · · Score: 1

      Depends... many consumer versions of OSs have very lax firewall configs by default. It may very well allow it. I certainly have never had to open the port when running transmission on Fedora, it seems like it just allows it regardless. And on Windows you get those little *this application wants to connect to the internet* popups, and if you hit allow it opens up the firewall for that app, for ALL ports I believe.

      Yes, Linux will let you do whatever you want to do. But Windows (XPSP2 or later, by default) opens up the firewall for that app, on whatever port rangs the app requested. It doesn't automatically open up all ports. And it only happens after you approve it, via the prompt. You can then go into your firewall settings and alter the ports. Those are also the only ports that the application requests the router forward to it via uPnP.

      And, I have sat there and not hit the button, and it looks like it just allows the traffic anyway.

      That hasn't been my experience. Some apps seem to pull in a web component that works even if you don't grant them firewall access, but that's outgoing-only. Unless your firewall is configured to block outgoing connections by default, then the app may have access to the internet until you respond to the prompt; but no ports will be forwarded to your machine until you do.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    58. Re:Sigh - what the heck ... by vandamme · · Score: 1

      Norway, but you know it was not the USA, which is where you live, obviously. Home of the free, brave, and Microsoft.

    59. Re:Sigh - what the heck ... by Anonymous Coward · · Score: 0

      UPNP: A protocol to allow arbitrary users to automatically punch holes in your firewall.

  8. What it's not about by andyring · · Score: 4, Insightful

    Yes, this is /. We can upgrade our router firmware or install other firmware. Joe Sixpack cannot.

    The blame for this should be laid squarely at the feet of the router manufacturers. IMHO, here's what Linksys/Cisco/Netgear/etc/etc/etc/ should do, at the very least:

    1. Be open and forthcoming about bugs found in their router software
    2. By default, routers should ship with automatic firmware updates enabled. This should be difficult to disable and robust enough that it'll *just work* with no user intervention.
    3. Tell this to their customers in plain English or $localLanguage on the product packaging. And NOT in fine print. Make it very obviously noticeable to the purchaser. This can and should be a signifiant selling point, really. If I'm at BestBuy/WalMart/etc. and see one router boldly telling me "We care about your security! To protect you and your data, this router will check weekly with $manufacturer and update itself to give you the most secure Internet experience possible." And it's sitting next to another router that says no such thing, I'd buy the one that will keep me safe.

    1. Re:What it's not about by JDG1980 · · Score: 5, Insightful

      By default, routers should ship with automatic firmware updates enabled. This should be difficult to disable and robust enough that it'll *just work* with no user intervention.

      The problem is that this kind of automatic update process can be a security hole in and of itself. If there is a way for a remote system to send updates to the router's firmware, then there is the potential for a malicious user to spoof the update and send their own custom-crafted exploit code.

    2. Re:What it's not about by Anonymous Coward · · Score: 1

      "We care about your security! To protect you and your data, this router will check weekly with $manufacturer and update itself to give you the most secure Internet experience possible." And it's sitting next to another router that says no such thing, I'd buy the one that will keep me safe.

      That's funny. I probably wouldn't even consider buying a router that's going to randomly change its behavior on me without my explicit intervention. I don't want to wake up one morning and have to spend half the day figuring out why my router suddenly isn't routing traffic the same way it was before.

    3. Re:What it's not about by Anonymous Coward · · Score: 1

      My thoughts exactly. "Easily upgradeable?" Have you seen the installation instructions for OpenWRT? It's fraught with stern warnings about ensuring your firmware version matches your router version and making sure you select the right version based on nvram, processor speed, etc. And it gives all kinds of warnings about bricking your router if you screw this step up. Easy to handle for us, not for your mom and pop.

    4. Re:What it's not about by Anonymous Coward · · Score: 1

      Also I have disabled features on my router because of holes. Yet keep an older version of firmware (new one fixes the holes) for the sole reason that they seem to have monkeyed up the range in the wireless part...

    5. Re:What it's not about by Grishnakh · · Score: 1

      The blame for this should be laid squarely at the feet of the router manufacturers.

      Ok, what good is that going to do? So a bunch of people get their home routers hacked, and you point the finger at the router mfgrs. Why should they care? What are you going to do about it? Declare that you're not going to buy from them any more? Haha, like they care; their customer base isn't Slashdot users, it's regular Joe Schmoes who don't read Slashdot or tech news, and just buy whatever the Best Buy salesman or Comcast representative tells them to buy. Moreover, Joe Sixpacks have a long history of never blaming mfgrs for security problems, and instead laying the blame squarely at the feet of "the hackers", as if that's going to do any good.

      IMHO, here's what Linksys/Cisco/Netgear/etc/etc/etc/ should do, at the very least:

      Why should they? What are you going to do if they don't? Give them a bad reputation? They already have a lousy reputation among Slashdot-folk, and it isn't hurting them any.

      1. Be open and forthcoming about bugs found in their router software

      Why? This will just make their products look bad to the Joe Sixpacks. Better to keep it quiet.

      2. By default, routers should ship with automatic firmware updates enabled.

      I'm not sure why they don't do this already, but it's probably because there's a chance something can go wrong with a firmware update, resulting in a bricked device; better to just ignore the problem and let the device run with an old, known-good firmware, because then Joe Sixpack will see that it's working and not blame the mfgr.

      If I'm at BestBuy/WalMart/etc. and see one router boldly telling me "We care about your security! To protect you and your data, this router will check weekly with $manufacturer and update itself to give you the most secure Internet experience possible." And it's sitting next to another router that says no such thing, I'd buy the one that will keep me safe.

      This is a pretty good point, and again I'm not sure why they don't do it already. I think someone else in this discussion said that Apple's routers actually do this.

    6. Re:What it's not about by Minwee · · Score: 1

      That's right. Installing an OpenWRT release made for a D-Link DIR 825 on a Linksys E3200 would be a bad thing. So would installing the official D-Link firmware.

      If both manufacturers were to produce updates their own hardware, instead of kicking a device to the curb and then never releasing an update again until they receive a court order requiring them to, then this wouldn't be a problem.

    7. Re:What it's not about by xvan · · Score: 1

      Oh, if we just had something that allowed us to authenticate the update origin.

    8. Re:What it's not about by Anonymous Coward · · Score: 0

      Something like a person administering their own router.

    9. Re:What it's not about by mcrbids · · Score: 3, Insightful

      The problem is that this kind of automatic update process can be a security hole in and of itself. If there is a way for a remote system to send updates to the router's firmware, then there is the potential for a malicious user to spoof the update and send their own custom-crafted exploit code.

      Sure, that's why you sign your updates with decent (open source!) cryptography and embed your public key into the router's firmware.

      --
      I have no problem with your religion until you decide it's reason to deprive others of the truth.
    10. Re:What it's not about by idontgno · · Score: 2

      If both manufacturers were to produce updates their own hardware, instead of kicking a device to the curb and then never releasing an update again until they receive a court order requiring them to, then this wouldn't be a problem.

      And if ethereal unicorns would shit gold bricks in my back yard, I'd be able to buy a new car.

      But out here in the real world, routers are commodity appliances with a support lifetime measured in months, and you certainly can't sanely expect vendors to kneecap their cashflows by walking away from guaranteed obsolescence and minimized (shortest possible duration) support.

      Profit uber alles, after all.

      --
      Welcome to the Panopticon. Used to be a prison, now it's your home.
    11. Re:What it's not about by mrchaotica · · Score: 1

      The other things manufacturers need to do is quit releasing "FooRouter 300N-xpyvbei83qr-100.1-a" and "FooRouter 300N-xpyvbei83qr-100.2-a" with completely different and incompatible hardware.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    12. Re:What it's not about by Anonymous Coward · · Score: 0

      and then we never have homebrew router firmwares again?

    13. Re:What it's not about by JDG1980 · · Score: 1

      Sure, that's why you sign your updates with decent (open source!) cryptography and embed your public key into the router's firmware.

      Yes, but if the people writing the factory firmware were that competent, routers wouldn't need updates every week to remain secure.

      How many show-stopper bugs are found in the open source firmwares? How many in firewalls like m0n0wall?

      The underlying problem is that 99% of electronics firmware is crap. This isn't limited to routers – the hardware design is usually the primary focus of engineering, and firmware is something slapped together at the last minute to get it out the door. Until that attitude changes, these problems will persist.

    14. Re:What it's not about by Bloke+down+the+pub · · Score: 0

      mfgrs

      Is that short for motherfuckers?

      --
      It's true I tell you, feller at work's next door neighbour read it in the paper.
    15. Re:What it's not about by bluefoxlucid · · Score: 1

      The blame should be lain on Tenable Network Security for being alarmist dumbasses.

      In order to use HNAP, you have to be able to connect to the router. In other words, you need to be on the physical side of the network that supplies HNAP. This should not be WAN--it's WIFI or LAN. Wifi also has WPS.

      WPS provides a short duration attack window for anyone within range to connect to your router. Short duration, user-initiated. It's your fault for pushing the button.

      HNAP on the other hand requires someone to be on the network. Without HNAP, you could achieve the same by ARP flooding, ping scans, sniffing the network for packets (especially wifi), and so on. You'd find where packets are going, take a guess at the subnet mask (hint: it's /24), and so on.

      Here's the punch line: HNAP is for homes, so the uncomfortable stuff above (ARP floods, ping scans! On a switched network you will not get far! Ha-HA!) is irrelevant. If I'm subject to your Ethernet switch preventing me from just sniffing packets and finding all the information, I'm probably inside your house OH SHIT!

      And as for making it easier to probe for vulnerabilities and authentication bypass? I can just spoof packets from odd IPs and MAC addresses--if the router even bothers to block attack attempts--and throw every vulnerability at it in a few seconds. Find one that works, hook up to it.

      Revealing information about a router so you can start probing for a vulnerability? Man, you can buy these off the shelves. People look for vulnerabilities all the time; then they note them down, find someone with the same software, and repeat the vulnerability. They also publish them online. They're not linking up to your wifi router and impromptu finding a previously undiscovered vulnerability in 20 minutes, man. Plus it's easier when you can actually log in: you log in, you read the network traffic looking at HTTP cookies and POST requests and such, and then you log out and see if you can A) magic up an authentication token; or B) do like on Clear's wireless routers and just POST commands un-authenticated, to which it responds by executing the command and telling you you're not logged in.

      This is a pile of non-issue. Oh it's information-leaky alright; but the practical security implications are laughably moot.

    16. Re:What it's not about by msauve · · Score: 2

      "By default, routers should ship with automatic firmware updates enabled"

      Let us know how that works out.

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    17. Re:What it's not about by Anonymous Coward · · Score: 0

      Maybe if you spent more time writing proper documentation and less time telling the world how smart your arrogant ass is, Joe Sixpack wouldn't have a problem with installing DD-Tomato-Open on their shitty hardware.

    18. Re:What it's not about by jonwil · · Score: 1

      Not if the router manufacturer uses digital signatures on their update packages such that remote updates sent from the automatic updater are verified with a signing key that only the manufacturer has to prevent spoofing.

  9. I read the headline as: by RogueWarrior65 · · Score: 1

    "Reuters Pose Biggest Security Threat To Home Networks"

    1. Re:I read the headline as: by Sarten-X · · Score: 1

      I did my time in end-user support. I've been the one that's has to explain to Granny that she doesn't need to panic every time sees a new horror story on the news.

      Reuters may not be the biggest security threat, but they're certainly one of the biggest threats to sanity.

      --
      You do not have a moral or legal right to do absolutely anything you want.
    2. Re:I read the headline as: by bobbied · · Score: 1

      "Reuters Pose Biggest Security Threat To Home Networks"

      Problem is that they also are the biggest boon to computer security since the network was invented. I look back with less than fond memories of having my mother's windows box connected directly to the internet w/o any kind of firewall or even a NAT between her and the wild west. Oh those where the days!

      I'd much rather have even a flawed router between her machine and the bad guys. Even if they can compromise the router, that's at least one more step they have to go though, making her lowly Windows' box all that safer from the script kiddies... Nothing is really going to fix a determined attacker, except turning everything off and locking it away. Now if I can just keep her from downloading all that coupon printing garbage or letting the grand kids install their infected games...

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    3. Re:I read the headline as: by Minwee · · Score: 2
  10. That's why I resisted as long as I could... by AudioEfex · · Score: 1

    I resisted wireless as long as I could because of this very issue. I can turn on my computer and see a dozen networks, and I live in the suburbs. Unfortunately, convenience and devices I wanted to use finally required it (can't use an iPad without wireless), so I caved a few years ago. Thankfully, I learned long, long a go that if I didn't want something on the Internet, I didn't let it near an Internet connected computer. I have an old laptop I use for personal things that is not connected to any internet whatsoever, and if I need to move files it's on a burned, finalized CD. Sure, it can still be read semi-remotely if someone wants to invest in that magnetic scanning tech that can read what data you are writing to your hard drive, but a) I don't have anything that would be THAT valuable to anyone, and b) if someone was going to use that on me, I've got far greater things to worry about.

    1. Re:That's why I resisted as long as I could... by ledow · · Score: 1

      Which is one of the reasons that I treat wireless networks as hostile in my home, and you have to log in via VPN even if you're connected to my wireless.

      It's not hard. If you don't trust wireless, and you don't trust the Internet, treat them as the same thing.

      I've gamed and accessed my home network using OpenVPN on every client (over wireless and remote) for as long as I've had wireless. No extra ping on any half-decent hardware, utter security and who cares if - as in my case - WEP is flawed and then replaced with flawed WPA and then replaced again?

    2. Re:That's why I resisted as long as I could... by Grishnakh · · Score: 1

      You sound totally paranoid. If you want to be quite reasonably secure and have WiFi, all you have to do is make sure you're using WPA2 encryption. Better yet, make sure you're using an alternative firmware like OpenWRT or DD-WRT, and keep WPS and uPnP off no matter what you use.

      I don't think I've even heard of someone getting their WiFi hacked when WPA or WPA2 was being used; people only get their home WiFi "hacked" when they either use no security whatsoever, or WEP (WEP is trivial to hack). And even then, people only "hack" them so they can get free internet access, or maybe send funny stuff to your WiFi printer, not so they can search through all your files. Think about it: the only way to hack WiFi is to be physically on-site. How many people are going to drive around from neighborhood to neighborhood looking for WiFi networks to hack from their van, so that they can then try to hack into your computer from there (several orders of magnitude more difficult a task)? No one is going to go to all that effort so they can look at your pr0n collection. The really serious hackers are doing it from eastern Europe and Russia, and they come in through your regular internet connection; WiFi is irrelevant here. And the information they're after is likely your banking information, and since it's impossible to access your bank's online services from an old laptop that isn't connected to the internet, that isn't helping you either.

    3. Re:That's why I resisted as long as I could... by pjbgravely · · Score: 1

      Don't forget to hard disable the microphone on the laptop if it has one. There is a malware that can communicate using high frequency sound, from a networked machine to un-networked one. Of course both machines have to be infected. Probably with a virus attached to a file of the networked box.

      --
      Star Trek, there maybe hope.
    4. Re:That's why I resisted as long as I could... by timeOday · · Score: 2
      Sure, lose sleep over the notion of somebody parking on your street to crack your WEP and snag your HTTPS streams for offline analysis.

      Meanwhile 70 million credit card numbers were stolen from Target.

  11. ipcop by Anonymous Coward · · Score: 0

    Inline with the PFSense comment, i'm running IpCop. It's arguably less maintained than pfs, but it does the job and likely stays off the radar due to the small user base. It'll also run on virtually any old machine you have lying around, so there's really no need to virtualize (other than a few saved watts / ft).

  12. design goals that emphasize usability over securit by jader3rd · · Score: 1

    design goals that emphasize usability over security

    I wonder why usability was able to sell more than security? Hmm. Let's think about that.

    Meanwhile, a January 2013 study from Rapid7 found 40 million to 50 million network-enabled devices, including nearly all home routers, were vulnerable to exploits using UPnP.

    Man, and I can't get my home router to do UPnP. It's bad that UPnP allows for the configuration of the router to come from a machine outside of the network, but that should get fixed and UPnP should be able to start behaving like it is designed to.

  13. POT (Personal Open Terminal) non-threatening by Anonymous Coward · · Score: 0

    with millions of suspected users all online at once 24/7 it's hard to resist wondering what the need to beak in is about?

  14. Sadly, no . . . by Kimomaru · · Score: 1

    Commercial, closed-source products just tend to have these problems and it's pie-in-the-sky to wish for a vendor to produce a secure product. If you want it secure, probably your best bet is an open source, open hardware mini server (like cubieboard or Raspberry Pi) and you're going to have to learn to do it yourself.

  15. Custom Router by shellster_dude · · Score: 4, Interesting

    After I found that my ASUS RT-15U was running telnet with a default password, open to the world which I couldn't kill or change the password on, I swore of embedded device routers.

    I have replaced it with a small Debian box with dual NICS, and bought a 24port switch from TPLINK. It was the best decision I have ever made. Perfect reliability, complete control, via IPTABLES. I've got auto blocking of malicious ips trying to hit my ssh or port scanning me via DenyHosts and PSAD.

    A couple other custom scripts and DNSMASQ, dhclient, snort, and python, and I have all the other services and features I want, and ONLY the services and features I want.

    1. Re:Custom Router by Anonymous Coward · · Score: 0

      If that was literally the best decision you ever made, you either make bad decisions or have no sense of proportion.

    2. Re:Custom Router by udippel · · Score: 1

      Don't overdo the 'Interesting' here, my dear mods!
      It doesn't look like a role model to replace some - agreed - s***ty router. While I'm a Linux person, Debian is not necessarily the distro of choice. There are other, specialised, Linux- and BSD-based solutions that run on maybe even smaller hardware; and therefore much more energy-efficient.
      A 24-port router is nothing of a 'must' here, neither. And TP-Link wouldn't be the switch of choice for me anyway.
      "couple custom scripts", what the heck, we need a solution for everyone, not only for nerds and geeks!

      Reasonable, okay, useful, okay, but very much of a singular solution.

    3. Re:Custom Router by Anonymous Coward · · Score: 0

      So then, every time that computer is down for any reason, your internet for the whole house is down. Depending on the nature of the problem, your internet would go down for minutes, hours, or even days. Just rebooting the server to apply updates would annoy everyone else in the house. You should probably ask them first. Either your wife/kids, or your roommates depending on what life stage you are in. You got yourself less freedom and more responsibility, unless you live alone. Even then, you are still slave to yourself. One of the reasons I pay for Hulu Plus is so I can watch my TV shows regardless of my laptop. The laptop could be in any state whatsoever, including not even in the building, and I can still independently watch my shows through a variety of devices. That's how people want their internet.

    4. Re:Custom Router by Anonymous Coward · · Score: 0

      I would argue that Debian is -the- distribution of choice, based on a lot of reasons that I'm not going to list.

    5. Re:Custom Router by Anonymous Coward · · Score: 0

      Same boat. I was thinking about getting a Netgear NightHawk, but then decided to just get an i5-4750(VT-X, VT-D, TSX-NI, AES, RNG, No HT) 3.2ghz Haswell quad core with 8GB of 8-8-8-24 1600mhz memory, an Intel i350-T2 server NIC, RAID-1 Samsung 840 EVO 120GB SSDs, and a L2 managed 24 port Procurve. Toss on PFSense and win. All packed inside a mini-ITX.

      My ISP doesn't enforce an IP limit, so I can have mutiple IP addresses. NAT 1:1, and the I350 NIC supports exposing a given port as up to 8 virtual NICs that show up as 8 separate hardware NICs. Each virtual NIC supports all HW-offloads, and each one is capable of making full use of the entire 1gb port. To keep things fair, it round-robins the virtual NICs, frame by frame. The NIC will DMA/Interrupt coalesce all 8 NICs into the same batch, as to keep interrupt overhead down. Because each virtual NIC exposes itself as a real hardware NIC, it can be directly shared to the guest via VT-D.

      Because the guests don't know about each other when using the NIC directly, the NIC has a built in switch that runs at full PCIe2x4 speed, so the frames don't need to go out to the switch just to get sent back.

      Because the motherboard has its own NIC, I'll use that as a management port and VLAN it off and only let PFSense be accessible over the management VLAN.

    6. Re:Custom Router by Anonymous Coward · · Score: 0

      rebooting the server to apply updates

      GP said they were running Debian, not Windows 95.

    7. Re:Custom Router by Anonymous Coward · · Score: 0

      After I found that my ASUS RT-15U was running telnet with a default password, open to the world which I couldn't kill or change the password on, I swore of embedded device routers.

      I have replaced it with a small Debian box with dual NICS, and bought a 24port switch from TPLINK. It was the best decision I have ever made. Perfect reliability, complete control, via IPTABLES. I've got auto blocking of malicious ips trying to hit my ssh or port scanning me via DenyHosts and PSAD.

      A couple other custom scripts and DNSMASQ, dhclient, snort, and python, and I have all the other services and features I want, and ONLY the services and features I want.

      ...and you get an "Amen" from a fellow geek.

      Conversely, "Joe Sixpack" doesn't have these skills nor does he want to be bothered with such hassles. He just wants his pr0n and "tube" and "book" and such without any hassles. The manufacturers of consumer devices know these facts about "Joe Sixpack" and cater to it.

      So this "custom approach", while geeky and "well thought out", is definitely not common. Sure, some "Joe Sixpack" types will try it, and usually "fail silently" with a setup that is so insecure a strong breeze can break into the network. But most "Joe Sixpack" types got to a store or online, get a little box called a "router" or "router / firewall", or worse, trust the hardware choice local ISP.

      In the world of "mass market goods", this stuff is "commodity" and meant to be cheep and disposable. The "manufacturers" find the lowest cost chip that does what the product spec calls for. Then they find the lowest cost programmers to code the simplest solution possible that will compile and load on the target while meeting the product specs. Then Marketing gets involved to make the GUI into whatever "visual statement" they want for their employer. After that, the lowest cost "job shop" to build a batch and ship it out. If a new batch is needed to meet demand, the product specs might be tweaked, the model number changed, and the new batch "bid out" to a range of "job shops" with the lowest cost shop getting the work. Ever wonder why Linksys has so many freaking models? It's probably a combination of chipsets, product specs, "batch approach" to product models, and lowest cost "job shop".

      Automatic upgrades? That can be good and bad. Or worse. Anyone remember when Cisco/Linksys rolled out upgrades that imposed a new "cloud paradigm" that locked users out of their Cisco/Linksys devices until the user created an account "in the cloud" to manage the device? And do you remember the consumer backlash to it? People scrambled to find the older firmware and reflash their devices.

      What might be better than "automatic upgrades" is the approach of "notify the user" that an upgrade is available. Then explain in simple terms why they should load it. And then make that upgrade a simple process for the end user. Unfortunately people's email addresses change. And manufacturers have not $$$ incentive to build the upgrades, and even less incentive to publicize any flaws in their products. Ok, so there are some "pipe dreams" in this idea.

      Would better coding "up front" be part of the solution? Sure, but cost is a factor since manufacturers want to keep costs down.

      Would keeping to a smaller and smaller slection of chipsets be part of a solution? Sure, but cost and "feature set" are factors since manufacturers want to keep costs down; they pay for features they might not use in a certain model.

      Would educating "Joe Sixpack" be part of the solution? Yes, but unlikely to happen since Joe has might more pressing issues in his life....like when the next iPhone comes out, or the latest changes to a buddy's page on "book", etc. etc.

      I don't see a simple or even easy solution for "Joe Sixpack", but for the rest of us geeks, so long as we can build the stuff we want and make it do what we want in the way we want, and we have the motivation to do a good job of it, let's keep doing our thing.

      secret word: novelist [oh how appropriate]

    8. Re:Custom Router by Anonymous Coward · · Score: 0

      Another option for you, DebWRT. This is a project to get Debian running on devices designed to be routers. Currently it is pretty functional, the weakness I note is the project currently uses OpenWRT's kernel build rather than getting a pure Debian kernel build operational. There is some support in place to kexec a Debian packaged kernel and there has been experimentation towards making such a kernel build, but it isn't there yet.

    9. Re:Custom Router by toddestan · · Score: 1

      I've found the typical consumer router to be pretty unreliable compared to an old PC acting as a router. It shouldn't be that way, with the router being much simpler with no moving parts compared to a full blown PC. Even more so since my router PC is over 15 years so. But sadly that doesn't seem to be the case. It's literally been years since I last had a problem with the PC I've used as a router (last time it went down I found that some of the capacitors had burst on the motherboard - soldered some replacements in and it's been flawless since). Sure, I do have to take it offline to update it or whatever, but that can be planned, which is much better than the typical Linksys junk which seems to cut out randomly every few weeks requiring a power cycle.

    10. Re:Custom Router by shellster_dude · · Score: 1

      Yes...just like when your router goes down, you loose internet...

    11. Re:Custom Router by lars_stefan_axelsson · · Score: 1

      I used to do that. But then I came to the realisation that I was running a server anyway, and I always wanted a workstation handy, so I've gone the way of the big iron on consolidated everything onto one machine. It's my router/firewall, file server, web server, workstation and everything else. It sits in my living room and for maximum convenience I even don't bother with different user accounts. Instead I use Chrome and my wife uses Firefox so that we can access our email, surfing sessions etc. just by switching windows. Runs Ubuntu 12.04 LTS with Mate desktop.

      Since it's consolidated I can spend more money on better components (CPU, 32 GB memory, raid storage etc.) and I save a couple of hundred dollars per year in electricity alone from not running a separate file server etc. like I used to. It also means less to manage. (The kids use another computer with windows 7 and when they mess that up, it's no major hassle. They just have to do without until I get around to fixing it. Which is good for them anyway... :-)

      --
      Stefan Axelsson
  16. Re:design goals that emphasize usability over secu by 0123456 · · Score: 1

    Man, and I can't get my home router to do UPnP. It's bad that UPnP allows for the configuration of the router to come from a machine outside of the network, but that should get fixed and UPnP should be able to start behaving like it is designed to.

    Considering UPnP is broken by design, that's not really an improvement. Replacing a security hole in the router by a hundred apps that want their own ports to expose their own security holes to the Internet doesn't help much.

  17. OpenWrt? by Millennium · · Score: 1

    Forgive me if I'm wrong, but wasn't OpenWrt based on this same firmware? Or is this bug with the VxWorks-based firmware that Linksys later switched to?

    1. Re:OpenWrt? by Minwee · · Score: 1

      Forgive me if I'm wrong, but wasn't OpenWrt based on this same firmware? Or is this bug with the VxWorks-based firmware that Linksys later switched to?

      OpenWRT is a Linux distribution designed for routers. It often uses kernel modules provided by manufacturers such as Linksys, but is not a clone of the entire system.

      You could also follow the first link in the summary, which describes the bug and has this to say:

      "Only routers running stock firmware are vulnerable. OpenWRT is not vulnerable to this issue."

  18. A big hole is the default password by bzipitidoo · · Score: 2

    The default password, when it is the same default password across all units of the same model or even the same manufacturer, is easy to exploit. Any website can send the user's browser some code that instructs it to attempt to log in via the user's router's web interface with the default password. It works because the user's browser is behind the firewall and therefore "trusted". Once logged in, it's trivial to reconfigure the router to open up all kinds of holes. Harder but still doable is getting the router to host and run malware itself.

    The admin password is the first thing I change on a new router. Manufacturers who still don't individualize the factory set password are responsible for a lot of these problems.

    --
    Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
    1. Re:A big hole is the default password by TheRealMindChild · · Score: 1

      That would have to rely on said browser having an exploitable XSS vulnerability to work, however.

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    2. Re:A big hole is the default password by udippel · · Score: 1

      Totally agreed, but one trouble here: It is not 'conducive' to have non-standard default passwords.!

      Just imagine, Tom, Dick and Harry buying routers. How does a manufacturer distribute the individual password? And make sure, that it is not thrown away, or misplaced, or torn or worn off? I already see the light of a class action suit filed by some dim-wit when the latter can not get her router back to life after a reset!!

    3. Re:A big hole is the default password by Anonymous Coward · · Score: 0

      An easy method to avoid the default password would be that the router
      (a) doesn't contain a default password,
      (b) denies all connections to the internet before the user has set a password,
      (c) until that time redirects any http request to an internal page where you can set your password.

    4. Re:A big hole is the default password by Anonymous Coward · · Score: 0

      Print it right on the box -- physical security is definitely beyond the manufacturer's control, and not much of an issue for these devices. If you want, use the serial number or the ethernet MAC address that are ALREADY printed on the box.

    5. Re:A big hole is the default password by Sique · · Score: 1

      Print the default password on the router's bottom side, or make it the serial number of the device (which then has to be different than the WAN MAC address).

      --
      .sig: Sique *sigh*
    6. Re:A big hole is the default password by Anonymous Coward · · Score: 0

      The reset button could set the password to nothing. Then, the interface could force them to set their own password before allowing them to finish setting up their network.

    7. Re:A big hole is the default password by mlts · · Score: 1

      Even better, print it in one location, then hot-stamp it into the plastic of the router's case, filling the indentation left by the letters with an self-curing epoxy (so the stamped password doesn't wear away over time). It won't be 100%, but at least if the sticker wears off, the password is still present. Another way is to have a sticker, then a metal tag that gets stamped by a press, and is attached securely in a recessed place on the case (so if the glue fails over time, the tag doesn't fall off.)

      Even better would be having the default SSID be unique with a number that isn't related to the serial or the Wi-Fi key.

      Of course the best of all worlds is having the router have a panel and screen that, after a reset, requires configuration from that for basic functions before it ever flips a packet between interfaces. That way, the user sets their own password, username, and password, so there is never a default for intruders to guess.

    8. Re:A big hole is the default password by mrchaotica · · Score: 1

      Manufacturers who still don't individualize the factory set password are responsible for a lot of these problems.

      Isn't that all of them? I'd love to know which manufacturers (if any) actually individualize the passwords.

      --

      "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

    9. Re:A big hole is the default password by 0123456 · · Score: 1

      Print the default password on the router's bottom side, or make it the serial number of the device (which then has to be different than the WAN MAC address).

      Which is exactly what our router manufacturer did. Don't remember who makes it, I think it's rebranded with the ISP's logo anyway.

    10. Re:A big hole is the default password by Anonymous Coward · · Score: 0

      How does a manufacturer distribute the individual password? And make sure, that it is not thrown away, or misplaced, or torn or worn off?

      The last three routers I bought, from three different manufacturers, all had the MAC-based password printed both on the box and on the bottom of the router. The sticker on the bottom never touches anything; it won't wear off without some pretty bizarre behaviour by the owner.

    11. Re:A big hole is the default password by Mryll · · Score: 1

      I suppose it should be a required step in the initial configuration of the router.

  19. ipfire by sal_park · · Score: 1

    what about http://www.ipfire.org/ ? Needs a bit more grunt than dd-wrt but it is very easy to upgrade....

  20. If only... by itsdapead · · Score: 1

    If only there were an easily upgradeable open source router operating system to which vendors could add support for their hardware leaving long term maintenance to a larger community.

    If only it supported routers with built-in ADSL (which was the dealbreaker last time I looked at DD-WRT - and it took me some digging to discover that was why none of the routers I wanted to use it on).

    If that's since been fixed - and supports a router I can actually buy somewhere - then mod me happy.

    Personally, I could put together a low-power Linux box, get an ADSL modem, an ethernet switch, wireless access point (sounds like Belinksysco crap would be just as big a liability in WAP-only or modem-only mode) but (a) that's replacing 1 always-on box with 2-3 always-on boxes (b) there's the non-zero chance that I could screw up and (c) it doesn't really help joe public who need a reliable, secure plug-and-go box.

    Any trustworthy all-in-one ADSL Modem/Routers/WAPs out there?

    --
    In a survey of 100 programmers, 111111 thought that duck-typing was a good idea.
  21. Usability? by Cosmotic · · Score: 1

    I dispute the posts assertion that home routers are designed for usability. The interfaces for home routers are typically confusing, slow, awkward, undocumented, ugly, not discoverer, poorly conveying, and inconsistent.

    --
    -Cosmotic ÔÔ
    1. Re:Usability? by WRD-EasyTomato · · Score: 1

      I think some are getting better as they try to have routers act as more of a hub of the house (lot of $$ to be made there). The interfaces will get better too as people are accustomed to smartphones and will stop tolerating the interfaces we've seen in the past. We made EasyTomato JUST to have a better interface and be easier to use (mainly for access control and bandwidth management.) EasyTomato is only a step in the right direction and it's only a matter of time before routers are a lot more pleasant to use.

  22. But Routers are good things! by bobbied · · Score: 4, Insightful

    So this article is saying that routers are *bad* things for security right? Not so fast...

    In my view, having a router, even an imperfect one, between you and the internet is a *GOOD* thing for security. Yes, routers might be security risks, but NOT having them is even WORSE of a risk.

    Does *anybody* out there remember what it used to be like? It wasn't that long ago that the standard internet connection was for ONE machine and used a PPP connection that pretty much put your Windows (mostly) box directly on the internet. When all this got started, we didn't even have software firewalls. Imagine having a windows 95 box with all the standard services on a routeable IP address. It WAS extremely risky. I remember having unsolicited popups coming up all the time and bothering me with all manner of advertisements. It was a mess and security was extremely lacking.

    But then we have the dawn of consumer's using routers and doing all the same exploits became harder because of the NAT. Then routers added stateless firewalls, then state-full firewalls and closed many of the avenues used by the "bad guys" to gain control of your system.

    Consumer grade routers have been a HUGE boon to network security in the consumer world. Do they have flaws? Many do, but their contribution to overall security is worth more to me than the risks they may pose. Give me a router, even a flawed one, over nothing. Making the bad guys work harder is a good thing for security, and a flawed router does that.

    It's not that we shouldn't be discussing how routers should be made more secure. Obviously we want them to improve. It's just that we cannot loose sight of how far we've come BECAUSE of these things.

    --
    "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    1. Re:But Routers are good things! by hAckz0r · · Score: 1
      What is the one thing worse than having a Bot on your desktop machine? Having a stealth Bot controlling your network, having access to all your hosts, playing man-in-the-middle for all your "secure" SSL/TLS banking and credit-card connections. Andy you have no clue that it is even there. At least when you get a Bot on your local desktop machine you will have clues that something is spinning CPU and taking up disk space, if you are smart enough to notice those things. When a bot controls and sees everything, while giving no indication, and you have no AV or utilities on embedded hardware to diagnose the problem, then you have a REAL problem.

      Yes, having a router is better than having no router, but only if YOU still own it. Once the bad guys p0wn it then it is no longer your friend.

    2. Re:But Routers are good things! by ttucker · · Score: 1

      Besides spying on you, the router its self could likely be used in a botnet as well. Think, origination of DDOS attacks, sending spam, anonymous hop for criminal activity (with your name on it).

    3. Re:But Routers are good things! by bobbied · · Score: 1

      I've got to point out that it is going to take a significant amount of effort to play the "man in the middle" for SSL/TLS sites. There is a *reason* we have trusted signing authorities and configure browsers to only accept certificates which are from trusted sources. So, no, SSL/TLS man in the middle is NOT a huge problem because you are going to have to steal a certificate or get the user to trust a signing authority you control. Having control over the network is an issue, but with the improvement in local firewalls and security of most things is making it harder and harder to actually DO anything from the outside of a host.

      BUT, STILL, you are generally safer WITH a router than just wiring up direct to the internet. You are better being on a 192.168.x.x address than some routeable IP by virtue of being behind the NAT. I'm not saying it's a perfect solution, nothing is, but it's better, even if your router has issues. Besides, most routers are really not that bad.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    4. Re:But Routers are good things! by ZorinLynx · · Score: 1

      There was actually a brief time when some ISPs tried to *BAN* routers! Yup, they said you couldn't use a router and had to connect your computer directly to the Internet. There were also clauses that tried to ban you from connecting multiple computers to one connection.

      This was in the days when cable and DSL access was just starting out. They would actually send a guy over to your home to set up the hardware AND install software on your computer. They would often refuse to install on anything that wasn't a Windows machine, so if you ran Linux or a Mac you had to set up a "dummy" windows machine for them to do the install on, then switch back to Linux when they left.

      It was a horrible, dark time, and I'm glad it's over.

      "No routers allowed", hah.

    5. Re: But Routers are good things! by hAckz0r · · Score: 1

      For the most part I agree, only trusted signing athorities do nothing for you when the protocol itself lends itself to MITM attacks. Where I work all SSL traffic is monitored in this way, for security reasons. Including this post.

    6. Re: But Routers are good things! by bobbied · · Score: 1

      For the most part I agree, only trusted signing athorities do nothing for you when the protocol itself lends itself to MITM attacks. Where I work all SSL traffic is monitored in this way, for security reasons. Including this post.

      Then, they are monitoring with acceptance of their own SSL certs by the browsers they control. I'm not saying the MITM attacks are not *possible*. I'm saying that you are safer with a consumer router doing a NAT sitting between you and the internet. If for no other reason than it makes the hacker's life a bit more difficult by putting another step between him and what he wants to do.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    7. Re: But Routers are good things! by hAckz0r · · Score: 1

      They can mitm using any cert installed in any browser that anyone is running so long as they own the network routers out to the Internet. They have no control over my desktop nor my cellphone that I accessed /. from, via wifi, to submit my prior post. From where I am now they do not.

    8. Re: But Routers are good things! by bobbied · · Score: 1

      Sounds like they have a handle on security, for the most part. However, I've lived under much more authoritarian network setups. We use a virtual machine for internet access that connects though a VPN connection to the company proxy. You don't get to the internet any other way, even if you are not on the company network. There are a few exceptions to this rule, but in general you go though the browser in the virtual machine. The Virtual machine has no access to the local network, only the VPN connection, and gets reloaded every day. It's not fool proof, but it's about as secure as I can imagine.

      But I've worked at places where network security was basically a joke. The thought they had good security, but it was easily and routinely side stepped. A guy I worked with had an SSH connection that would automatically be made with a server in his home when he send an E-mail to a specific address. So, any time he wanted, he could access anything inside the network by setting up a PPP connection though his home server. It came in handy for him I guess, but it was a security hole big enough to drive a bus though.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    9. Re: But Routers are good things! by hAckz0r · · Score: 1

      You just described our 'indirect internet access' and yes I once used ssh proxies to loop back and test our own security perimiter. Currently I use Qubes-OS to partition my personal desktop security domains. one vm to do "work", another for email that can only access the smtp/imap servers, attachments open in one time use disposable vm's, so no custom attachment payloads can exfiltrate anything. Lastly one Internet only vm browser domain for sites requiring persistance or special certs. Network wise they do not overlap, as you are inside or out and cant see any data from the other vm domains. Hardware, priv drivers, and even DMA are confined to a networking vm while all traffic through it is encrypted. Its better than the indirect method, but at some point I will be forced to give it up.

  23. this is just wrong by Gravis+Zero · · Score: 1

    the biggest security threat to computers is the user. users improperly configure things, wont take security precautions (like using weak passwords) and will outright download viruses/malware. far too many users are not competent enough to tell the difference of a real popup window and a website claiming they have a virus and they need to install their trojan horse immediately.

    --
    Anons need not reply. Questions end with a question mark.
    1. Re:this is just wrong by Anonymous Coward · · Score: 0

      and NSA isn't the worse one that *actively* break into systems?

  24. So, will a 2005-era routers get a firmware update? by BUL2294 · · Score: 4, Insightful

    I seriously doubt that Belkin will put out firmware updates for all the old $50 Linksys router models they inherited support for--instead opting to push users to buy replacement models they otherwise wouldn't need. The likely answer is NO--even with a class-action lawsuit. (In all actuality, a 2006-era 2.4GHz 802.11G WPA2 router is still more than plenty for the crappy broadband speeds available in North America...)

    This is what scares me about the Internet of Things when it comes to long-life appliances that you could own/use for decades... How long will manufacturers (many of whom have 0 experience so far with connecting their products to anything but a power cable) continue to support these devices? Ultimately, government regulation may be required in this space. God knows I wouldn't want my IoT refrigerator to get "bricked" (a really heavy, big brick!) after 20 years because the manufacturer went under & the fridge couldn't phone home... Or worse, because someone found a backdoor that had been in place for all models in use for 9 years before my model was developed...

    --
    Windows 3.1x calc: 3.11 - 3.10 = 0.00
  25. My router by ttucker · · Score: 1

    Is an Ubuntu machine with three NICs. The firewall is configured with the Shorewall utility. It only needs to be rebooted for kernel updates.

    1. Re:My router by eedwardsjr · · Score: 1

      I use Sophos' UTM product. http://www.sophos.com/en-us/pr.... It is not open source and grandma is not going to use this, but it is rock solid. Honestly the primary reason is country blocking and the daily email reports on the previous day/week/month's activities. You have to get a PC for it, but a small form factor ATOM processor box with works well and has a low power consumption.

  26. NAT should allow the packets, if you send packets by Marrow · · Score: 1

    NAT should setup a rule to allow your machine to get packets as long as you send some packets there first. Unless your game machine is acting as a game server and getting packets from many host, it should just work. Otherwise, you could/should setup a port forward to your internal machine.

  27. Re:So, will a 2005-era routers get a firmware upda by ttucker · · Score: 1

    I have been thinking this about the internet of things as well. Then when they roll out IPv6 we can put all of our extremely dated hardware directly on the internet!

  28. The fault of the device makers... by Lumpy · · Score: 3, Insightful

    there are options for more secure but they fight the hardware hackers instead of embracing them. If they would reach out to the communities and work with them or PAY these groups like OpenWRT to write their firmware they would end up with a better product.

    --
    Do not look at laser with remaining good eye.
    1. Re:The fault of the device makers... by Anonymous Coward · · Score: 0

      Samefag detected.

    2. Re:The fault of the device makers... by Anonymous Coward · · Score: 0

      You're Lumpy doing anoncoward replies avoiding a test apk challenges him to? It's obvious apk has Lumpy over a barrel.

    3. Re:The fault of the device makers... by Anonymous Coward · · Score: 0

      You're being made a fool of here http://slashdot.org/comments.p... . Reply to this using your registered user account here on slashdot http://games.slashdot.org/comm... since even I by this point suspect you are doing what apk said in you applying minus moderation to his posts beneath yours he did and not proving him wrong on your part. Only minus mods and running from you. If you run we all know you did it and apk was right and has you caught red handed.

  29. Re:NAT should allow the packets, if you send packe by Anonymous Coward · · Score: 0

    True, but in my days of playing Starcraft and Warcraft 3, connecting to Battle.net and hosting a multiplayer map resulted in your computer to begin listening for new connections on a port. I had to configure port forwarding to allow connections to come through. Technically, this would be a game server in a sense, but it's example of something even a casual gamer/user would do.

  30. The problem is lack of information and misinformat by inkrypted · · Score: 1

    It does not matter what kind of hardware or software you have or use without knowing what the best security practices are you will be vulnerable. People just want something easy to use. A good example is UPnP. used improperly it can open up the network to all kinds of vulnerabilities but people are willing to sacrifice their security because they don't want to take the time to learn about proper port forwarding. So the problem will continue until people take security seriously. Having said that their is nothing wrong with OpenWRT, DD-WRT, or Tomato firmwares but without knowing how to set them up securely it's still a huge problem. Lack of and misunderstanding of information does not help either alot of these communities associated with these firmwares have very poor documentation.

    --
    Chris Sheppard
  31. Shields Up at Gibson Research by Anonymous Coward · · Score: 0

    Are those results of the tests trustworthy?

    1. Re:Shields Up at Gibson Research by kmg90 · · Score: 1

      GRC? I would trust Steve Gibson with my flaky hardrive (spinrite) let alone telling me if my ports are wide open or not.....

  32. Paranoid much? by sjbe · · Score: 1

    Don't forget to hard disable the microphone on the laptop if it has one. There is a malware that can communicate using high frequency sound, from a networked machine to un-networked one.

    I think that is about as likely as getting molested by a unicorn.

    Seriously folks, I'm all for reasonable amounts of security but this sort of thing is just hide under the bed paranoia.

    1. Re:Paranoid much? by ColdWetDog · · Score: 1

      What's wrong with hiding under the bed?

      --
      Faster! Faster! Faster would be better!
    2. Re:Paranoid much? by sjbe · · Score: 1

      What's wrong with hiding under the bed?

      It's crowded with all the monsters under there.

  33. Re:So, will a 2005-era routers get a firmware upda by mrchaotica · · Score: 1

    This sort of issue is why the Free Software Foundation was created. It wasn't because Stallman had some kind of political agenda, it's because he wanted to fix the driver for his printer, but couldn't because it was proprietary. The "Internet of Things" has the exact same problem, and the exact same solution.

    --

    "[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz

  34. Re:So, will a 2005-era routers get a firmware upda by Anonymous Coward · · Score: 0

    I seriously doubt that Belkin will put out firmware updates for all the old $50 Linksys router models they inherited support for--instead opting to push users to buy replacement models they otherwise wouldn't need. The likely answer is NO--even with a class-action lawsuit. (In all actuality, a 2006-era 2.4GHz 802.11G WPA2 router is still more than plenty for the crappy broadband speeds available in North America...)

    This is what scares me about the Internet of Things when it comes to long-life appliances that you could own/use for decades... How long will manufacturers (many of whom have 0 experience so far with connecting their products to anything but a power cable) continue to support these devices? Ultimately, government regulation may be required in this space. God knows I wouldn't want my IoT refrigerator to get "bricked" (a really heavy, big brick!) after 20 years because the manufacturer went under & the fridge couldn't phone home... Or worse, because someone found a backdoor that had been in place for all models in use for 9 years before my model was developed...

    In your bricked appliance scenarios, the vendors would do exactly what they would do today for older appliances that do NOT have internet connectivity.

    They would laugh in your face at the thought of them giving you ANY support after a decade of ownership, and tell you to get your ass in the store for the "fix".

    Sorry, but name something in this world that has a warranty beyond 5 years. It simply doesn't exist anymore, and therefore your "long term" argument is pointless from a support perspective. You'll either pay someone to fix your old shit, or your will kindly get in line like all the other consumer sheep and go buy a new one to replace your disposable appliance.

    And the Internet of Things won't change that a damn bit.

  35. Yes, yes it was. by Anonymous Coward · · Score: 1

    Yeah. Script injection to do CSRF with DNS rebinding.

    http://media.blackhat.com/bh-us-10/presentations/Heffner/BlackHat-USA-2010-Heffner-How-to-Hack-Millions-of-Routers-slides.pdf

  36. SmoothWall by Anonymous Coward · · Score: 0

    I like my Smoothies. You can also physically separate your wap's from your wired network.

    F everyone else if they are going to crank out a bunch of crappy routers that have more in common with a steaming turd than electronic hardware that's supposed to be a secure hardware layer.

  37. ...or not... by Anonymous Coward · · Score: 0

    If the router allows packets on the LAN side with its WAN-side IP to access its LAN side services (take a moment now, if you need it), then a remotesite.com that resolves to both the attacker's site and to the WAN-side IP of the router can coax the browser into accessing the router's local services. Some DNS systems protect against this. No browser can.

    http://media.blackhat.com/bh-us-10/presentations/Heffner/BlackHat-USA-2010-Heffner-How-to-Hack-Millions-of-Routers-slides.pdf

  38. Lumpy's busy "eating his words" by Anonymous Coward · · Score: 0

    From where he libeled me before this post http://yro.slashdot.org/commen... and I made him "eat his words" there in the post parent to mine in that reply using verifiable facts with people in the security community!

    Lumpy ran like the weasel he is after that. Figures. He talks big on many things but when push comes to shove? You see Lumpy do a "Run, Forrest: RUN!!!" like he is now avoiding this test of mine to see if he has been downmodding my posts for years here as I suspect.

    He hasn't (& I suspect he WON'T reply using his registered user account LUMPY on slashdot here -> http://games.slashdot.org/comm...

    (Since I am nearly sure he has been doing what he did there to me, for years directed my way - downmoderating my posts "hit & RUN" (Forrest, RUN, lol) style...)

    APK

    P.S.=> We'll see IF he does (he could have done those downmods using sockpuppets too possibly, but I don't think he's that smart in this case) - if he doesn't? He only proves me right, as usual...

    ... apk

  39. Is it really any better? by Alef · · Score: 3, Interesting

    This is an honest question.

    Is there any penetration testing or statistics that suggests that dd-wrt and the likes are more secure, or is this an it-runs-Linux-so-it-must-be-good knee-jerk assumption?

    I used to run dd-wrt on a router some years ago and liked it feature-wise and performance-wise. However, my confidence in its security took a pretty big hit when I read about this gaping security hole in 2009. It's the kind of issue that makes you doubt that some of the developers really know what they are doing.

    1. Re:Is it really any better? by un1nsp1red · · Score: 1

      I think it's just that it's open, so at least security vulnerabilities can be spotted (though there's obviously no guarantee). You don't have the same visibility (and, often, community) with closed-off, proprietary firmware.

    2. Re:Is it really any better? by Anonymous Coward · · Score: 0

      is this an it-runs-Linux-so-it-must-be-good knee-jerk assumption

      No, it's more like "now that I have complete control over this device, I can better secure it".

  40. Food usually works. by Dareth · · Score: 1

    Food usually works. If not that, there is always money.

    --

    I only look human.
    My mother is a halfling and my dad is an ogre, so that makes me an Ogreling
  41. My router's security by Anonymous Coward · · Score: 0

    iptables -P INPUT -s ! 127.0.0.1 DROP
    iptables -P OUTPUT -d ! 127.0.0.1 DROP
    iptables -P FORWARD DROP
    iptables -A INPUT -p udp --dport 1194 -j ACCEPT #OpenVPN

    iptables -t mangle -I OUTPUT -m owner --uid-owner proxy -j MARK --set-mark 1
    iptables -A OUTPUT -j ACCEPT -m mark --mark 1
    iptables -A OUTPUT -j ACCEPT -m state --state ESTABLISHED,RELATED

    Absolutely no need for new outgoing connections from localhost, or any outgoing connections from any internal machine that are not set up to use the proxy.

    We don't do blind proxying, and the proxying rules are also incredibly strict.

  42. Lumpy's busy "eating his words" by Anonymous Coward · · Score: 0

    From where he libeled me before this post http://yro.slashdot.org/commen... and I made him "eat his words" there in the post parent to mine in that reply using verifiable facts with people in the security community!

    Lumpy ran like the weasel he is after that. Figures. He talks big on many things but when push comes to shove? You see Lumpy do a "Run, Forrest: RUN!!!" like he is now avoiding this test of mine to see if he has been downmodding my posts for years here as I suspect.

    He hasn't (& I suspect he WON'T reply using his registered user account LUMPY on slashdot here -> http://games.slashdot.org/comm...

    (Since I am nearly sure he has been doing what he did there to me, for years directed my way - downmoderating my posts "hit & RUN" (Forrest, RUN, lol) style - yet NEVER disproving my points validly (odd that, eh? NOT...)

    APK

    P.S.=> We'll see IF he does (he could have done those downmods using sockpuppets too possibly, but I don't think he's that smart in this case) - if he doesn't? He only proves me right, as usual...

    ... apk

  43. Re:So, will a 2005-era routers get a firmware upda by Anonymous Coward · · Score: 0

    I think the grandparent's point is that even if official support doesn't extend for the life of an appliance like a refrigerator, it remains useful after the support expires. Especially if we buy appliances of high quality, we have a reason to expect that they'll probably chug along usefully after the warranty runs out. Warranties were never supposed to imply that this device will work for exactly x-many years. It's a guarantee that it will work for at least that long. But if these are "smart" devices that outlive their software support, then the hacking wolves of the internet can take them down even if the compressors and motors are working fine. Tech support will tell you that your only alternative is to buy a new fridge, which is immune to the hack that turned the old one into a lettuce-freezing spambot. Of course, once it's off warranty, you'll again be on your own against the wolves of the day, and it won't be long before you'll need yet another new fridge.

  44. Re:NAT should allow the packets, if you send packe by Bengie · · Score: 1

    NAT is a general concept, not a standard. One NAT may implement exactly that, but others may not. This is something hard for programmers to design for.

  45. Re:So, will a 2005-era routers get a firmware upda by mattsday · · Score: 1

    I agree, except it's better to push people on to 802.11n in the 2.4Ghz space; it uses the radio space more efficiently and won't slow down your neighbours. It also adds range and reliability. Considering most complaints aren't going to be about the routing performance but the wireless coverage, upgrading to n would be a boon for many, especially dual-band if their devices can run on 5Ghz.

    --
    Now there's one hoopy frood who really knows where his towel is!
  46. How does application programming fit in? by Marrow · · Score: 2

    I think that programmers are going to assume they can talk to the remote host, and then timeout/fallback when that communication fails to take place correctly. If you are going to connect to a server either with tcp or udp, you are going to do a gethostbyname and then send a packet. The NAT appliance is going to see the packets and set up its translation table so that outgoing packets get re-written with the correct source address/port. And the incoming packets from the dest/port are going to get re-written to talk to the client program.
    What messes things up is that the client has to push through the NAT first to setup the translation table. Which works fine unless you are acting as a server and are waiting for an unknown host to talk to. Then the translation table is empty, and your firewall is blocking everything.
    UPnP is a way to create servers without doing administration on the firewall. The application is not aware of any of this unless it tries to use UPnP to poke a dynamic hole in the firewall.

  47. Lumpy how'd "eating your words" taste? by Anonymous Coward · · Score: 0

    Where you libeled me & ran when I used facts vs it -> http://yro.slashdot.org/commen...

    (You sure "talk a good game" -> http://games.slashdot.org/comm... but you can't even produce a MERE SCRIPT, for Pete's sake...!)

    You aren't even on the leve of a "script kiddie", & full of HOT AIR, windbag!

    * :)

    (You know it, I know it, & so does anyone reading AND laughing their asses off @ you now... lol!)

    APK

    P.S.=> Answer the question in the subject-line Lumpy - & WHY won't you reply as Lumpy your registered user account name here on slashdot in the next link I posted below?

    Is it since it will remove the unjustifiable downmods you applied to my other post here -> http://games.slashdot.org/comm... IF you post as your registered account here on slashdot of Lumpy?

    I think so.

    Yes - I suspect that IS the case here (simply logging out of a registered account & trolling by ac is a common troll trick around here OR using alternate registered 'luser' accounts sockpuppets to do the job will also, & Lumpy is LOADED with those & trolling - which doesn't matter: He PROVES he's all talk, no action (or skills, OR brains, lol))...

    ... apk

    1. Re:Lumpy how'd "eating your words" taste? by Anonymous Coward · · Score: 0

      APK, a few years ago I might have flamed you, but after all these years of watching you on slashdot, I'm pretty sure you need mental health care. Please don't take that the wrong way, it's not an insult. It's sincere. People who need it, need it through no fault of their own. It's not shameful. I want to do the opposite of making you feel bad about yourself -- I want you to be happier.

      Please, please try to step back and look at what you're doing here. How much of your life have you wasted hounding "enemy" posters? How much time have you spent writing these repetitive playground-level taunts? That's not how you gain the respect you so clearly desire -- you get that by posting with merit and substance, and this obsessive behavior isn't helping you do that.

      Even if you think you have posted that kind of material, I assure you that you're drowning it out. People associate the initials "apk" with rabid-dog behavior, because that's at least 95% of what you do. Furthermore, you're always betraying your insecurity, in that a mature, well adjusted networking expert wouldn't even feel the need to pull all this petty vindictive shit. They'd be secure enough in their arguments that they could just laugh off slashdot idiots after flaming them a little bit. But with you, it's nuclear armageddon salt-the-earth mode as soon as anyone dares argue with you. People treat you like a troll (or ignore you) because your behavior tells them there's clearly no way to reach you with reason.

      This stuff simply isn't accomplishing what you want it to -- it doesn't impress either the targets of your harassment or the peanut gallery -- and it sure isn't good for you. At the very least you should step away for a bit, try to calm down and get some perspective. And like I say, I really am sincere in hoping that you get some professional counselling. I'm certainly not qualified to help you, but I can see that you need it.

      (For what it's worth, I'm a random AC who doesn't have a registered account, and never has. I'm sure you'll take me for one of the people you've obsessed about in the past, but honest, I'm not.)

    2. Re:Lumpy how'd "eating your words" taste? by Anonymous Coward · · Score: 0

      Lumpy you're not qualified to judge anyone's mental state minus degrees, state license, and an exam in a professional psychiatric environment. You have delusions of grandeur you can. You saying you're a "random AC" gives away you are Lumpy. Talk about projecting.

    3. Re:Lumpy how'd "eating your words" taste? by Anonymous Coward · · Score: 0

      "after all these years of watching you on slashdot" sounds like you stalk apk. You said it.

    4. Re:Lumpy how'd "eating your words" taste? by Anonymous Coward · · Score: 0

      Apk proved Lumpy libeled him http://yro.slashdot.org/commen... in his reply to Lumpy and he's wrong according to you? Please. Get over yourself with your advice. You speak like you speak for everyone here too and admit trolling idiots like you Lumpy are around and that when attacked apk should just sit there and take it? It's clear you've had your behind handed to you by apk at some point speaking like you do, for everyone here, like you represent this place. Once more get over yourself. You don't. If more people did what apk did then the troll problem might not be as bad. Ever think about that, Mr. allegedly "random AC" (bs)? From what I've seen of watching apk he gets the best of moron like Lumpy (obviously you posting as anoncoward) as shown in the link above. Lumpy do you honestly think you've fooled us? Think again.

  48. Re:So, will a 2005-era routers get a firmware upda by Anonymous Coward · · Score: 0

    God knows I wouldn't want my IoT refrigerator to get "bricked" (a really heavy, big brick!) after 20 years because the manufacturer went under & the fridge couldn't phone home...

    No problem there. No refrigerator built today will last longer than 8 years.

  49. Re:No Shit by DahGhostfacedFiddlah · · Score: 1

    The part of a "home network" that is connected to the 'net is the biggest threat?

    It's also the part that's doing the simplest thing (assuming you haven't networked your light switches). No bumbling grandma clicking every popup in sight, no kids downloading their warez. A router should be a rock-solid appliance that shouldn't be able to be "hacked" in any meaningful way without physical access.

    Bottom line, it's surprising - or at the very least troubling - that routers are such a security problem.

  50. Sometimes there's little you can do (VDSL sucks) by Phil+Urich · · Score: 1

    My current ISP uses VDSL2 for all their current plans, and they only offer modem+router combos (and refuse to even allow you to put them into bridge mode). The problem is that VDSL2 requires a cert from the ISP to work, so even if I could find a compatible VDSL2 standalone modem I wouldn't be able to use it.

    There is only one other primary ISP available to me, and they are a cable provider, and also only offer modem+router combos. At least for them they'll remotely put their device into bridge mode, but you're still stuck with a router connected to the internet in your home and you just have to trust them that it'll be fine (and I've heard they're far from stable).

    It seems like my only options if I want to run my own router hardware are to pay for an expensive business plan (I mean, at least I hope they still offer modem-only solutions for businesses) or to just stick with my old ADSL plan. It's slow, but I can use my own router with their inoffensive standalone modem, and as a bonus my plan is old enough that I don't have usage caps, unlike seemingly every other plan in Canada now (unless you pay an extreme additional premium).

    --
    I remember sigs. Oh, a simpler time!
  51. Belkin too with USB flaw by Anonymous Coward · · Score: 0

    Just read where Belkin routers have a exploit to access USB drives hooked to their routers. Go figure, the security of routers is broken. Manufactures make router stupid proof for idiot consumers who can't read or understand directions. Heck its why for years Wireless routers came out of box with wireless security turned off. So idiot people could connect to their router and not waste countless hours with tech support.
    Two things not to do with a router, don't turn off firewalls, don't hook anything to them except through Wireless secure connections and LAN ports.
    These Router makers use rather weak and poorly thrown together firmware. Its why so many of them issue a lot of revisions of firmware just to fix all the crap that breaks.

  52. Re:So, will a 2005-era routers get a firmware upda by BUL2294 · · Score: 1

    It's not a question about warranty or even availability of replacement parts, it's a question about opening themselves up to extremely long support schedules, something they have never had to do before. If I call an appliance repairman for a 40 year old fridge, he'll likely be able to find the right replacement part... But that model no longer holds true in IoT. Look at cars (at least in the US)... Auto manufacturers have taken on the responsibility that all of their past models could face a recall, even 15+ years after the fact. (NHTSA still opens cases for cars sold in the '90s). The same would have to be said about Internet-connected devices--specifically household appliances.

    The problem is that we're talking about operating systems, web hosting software, network stacks, databases, device drivers, etc., that would need to be supported for, easily, 20+ years. Think back to 1994--what software that existed then is supported now??? NONE. So, imagine you buy in 2014 an IoT refrigerator full of the latest & greatest Android 4.4.x and/or Linux 3.13.x FOSS software--what sort of support would you expect for any of that in 2034??? Would you expect Amana, GE, Kitchenaid, Electrolux, Miele, Kenmore, etc., engineers to be fixing Linux 3.13.x kernel security holes in their 20-year old appliances? FOSS or not, as a consumer, I would expect that appliance to continue to work & not get bricked by malware that was deposited remotely...

    --
    Windows 3.1x calc: 3.11 - 3.10 = 0.00
  53. Re:So, will a 2005-era routers get a firmware upda by Anonymous Coward · · Score: 0

    Relax, don't worry, be happy. The "Internet of Things" is a fad. It will disappear without a trace soon enough, and then you won't have to worry about 10- or 20-year update support for your fridge.

    IoT isn't even a particularly new idea. I'm pretty sure I was hearing about the inevitable domination of internet enabled kitchen appliances ten years ago. It didn't happen then, and it's not going to happen now, because...

    Starry-eyed idealism: ANDROID IN THE FRIDGE IS A WHOLE NEW PARADIGM OMG!! It will change how we do EVERYTHING!

    Reality: Android in the fridge is dumb. If you buy a fridge with android in it, it will be about a month before you get sick of fucking with the android device every time you open the fridge just so that it can "automatically" notify you when you've used something up. And don't believe anyone who tries to sell you the idea that "sensors" can perfectly ID everything that goes in and comes out.

    Maybe I'm too cynical, but to me the IoT fad is a classic case of mistaking the existence of high geek-appeal solutions as proof that there are real problems which average people will pay money to have solved.

  54. Re:So, will a 2005-era routers get a firmware upda by BUL2294 · · Score: 1

    I agree with you, in theory. In practice, however, nobody is fixing bugs/security holes in obsolete platforms. Let's say the IoT existed in 1994 & you bought a new Kenmore IoT fridge running Linux 1.x. Fast forward to 2014--who today is doing anything with the Linux 1.x kernel? Nobody--including Kenmore support engineers. Your fridge was pwned probably 15 years ago...

    --
    Windows 3.1x calc: 3.11 - 3.10 = 0.00
  55. Re:design goals that emphasize usability over secu by jader3rd · · Score: 1

    Considering UPnP is broken by design, that's not really an improvement. Replacing a security hole in the router by a hundred apps that want their own ports to expose their own security holes to the Internet doesn't help much.

    I feel like I can be responsible for anything that runs on my machine, so I'm okay with that.

  56. Re:So, will a 2005-era routers get a firmware upda by Carnildo · · Score: 1

    Let's say the IoT existed in 1994 & you bought a new Kenmore IoT fridge running Linux 1.x. Fast forward to 2014--who today is doing anything with the Linux 1.x kernel? Nobody--including Kenmore support engineers.

    In 1998, I purchased a computer running Windows. Shortly afterwards, I installed Linux 2.2 and a webserver on it. Strangely enough, the computer is still working, is running a modern kernel with full support for the hardware, and somehow managed to avoid being pwned at any point in the intervening 15 years.

    The nice thing about open-source software is that you generally don't need to run obsolete software on ancient hardware. That Kenmore IoT fridge would probably run a Linux 3.x kernel without problems, as long as the software was genuinely open-sourced.

    --
    "They redundantly repeated themselves over and over again incessantly without end ad infinitum" -- ibid.
  57. that depends by Anonymous Coward · · Score: 0

    If your product can not be reasonably or safely configured by its target market, then while it is tempting to blame the individuals, it is the manufacturer who has failed.

    Yes consumers failed, and consumer groups, it is, or should be just as much our responsibility, as well as these [reminding you how untrustworthy companies are] companies to make sure they stop short cutting product security. Putting in, as worthless as this has shown time and time again, a regulating body with heavy fines and or incentives for creating bad/good security may deter this. Then again look at the lack of security within government and my idea pretty much would be for nothing.

    I go back to the argument that people should get together, organizations, watch groups, security researchers, and start filing massive lawsuits against these companies. Since the internet was unleashed on the masses we continue to put up with story after story on gaping holes that companies ignore, and or they are {pathetically} worried about people not buying the product because they feel it isn't "user friendly". This stuff should be left to people that can be certified to install then it set-up to the users needs, certified because should the installer decide to abuse his knowledge and exploit the systems [an inside man for hackers] he can also be held accountable.

    The arguments over who is responsible for everyone. And we really shouldn't even be discussing this if proper agencies or regulatory bodies were in place to stop this, or at least minimize it.

  58. I accomplished EXACTLY what I want #1/3 by Anonymous Coward · · Score: 0

    To send trolls a CLEAR message: You're bogus downmods "advantage" just *might* be one you can screw with others with, but NOT me (Lumpy libeling me & having it exposed to "name & shame" him WAS necessary - & yes, it worked: He's been posting like MAD all month, but after that yesterday? He's gone "silent"... so, yes, it was effective AND IT WORKED - I've dealt with wannabe bullies ALL MY LIFE (I grew up & live in a pretty bad violent urban environs, & you learn fast to take on bullies to take them out, & usually once you give them a GOOD PUNCH IN THE NOSE or JAW they stop... might take more than one, but it works, ALMOST every time...get it? Good!). So, when you downmod bomb me (which happens here quite a lot, the majority of the time on my posts on hosts especially, and I don't spam them - I only post them WHERE THEY ARE PERTINENT or APPY... funny, no one EVER 'bitches' on all the AdBlock ones though, eh? Is that because it's "Open Sores"? Well, it's inferior & doesn't DO as much, point-blank, period... & if others can do that, then, so can I on hosts... or is there a "double-std." here when it comes to "Open SORES" crap vs. anything else? Is that what the deal is here?? Fuck that!)

    APK

    P.S.=> I find it "odd" (not, jsut another discriminatory example of b.s. here) I had to bust my message up into 3 parts here, but you didn;t have to... apk

  59. I accomplished EXACTLY what I want 2/3 by Anonymous Coward · · Score: 0

    Cotinued from -> http://slashdot.org/comments.p...

    No, your downmod bombing advantage was one I wanted to send a message on too... for a year, I wouldn't allow myself (sort of a personal promise to NOT abuse power I always had, just to see how I'd fare without it (call it not wanting to be the NSA with absolute power corrupting absolutely, but his time I had to use it)) to NOT use what I could always do (post unlimitedly) - but when that FOOL Lumpy libeled me & I'm told "Oh, that's OK" NO, it is not... it is an attempt @ damaging my professional reputation & that IS the worst form of libel... I had to shit all over him exposing him in doing it, and yes, he's ceased posting... it works. Name & Shame is just as good as a punch in the face of any bully I found out).

    So, the b.s you're feeding me, based on the results here? IS B.S. from YOUR end LUMPY (yes, it's you, I am nearly certain of it)... funny Lumpy also won't post where I dared him to as well - he KNOWS it will show everyone here that when my downmods disappear from a thread he was the parent in, the downmods will disappear, and it will also be PROOF he cheats the moderation system (ie afaik you cannot downmod in a post using a registered username & then come in again as that username & post without removing all your downmods you put on others).

    APK

    P.S.=> Last part's coming up in seconds & it IS THE MOST IMPORTANT PART (what this site really needs to stop trolls, but only thing is, I don't think they WANT them stopped)... apk

  60. Re:NAT should allow the packets, if you send packe by udippel · · Score: 1

    NAT should setup NOT a rule to allow your machine to get packets as long as you send some packets there first.

  61. Re:Sometimes there's little you can do (VDSL sucks by Anonymous Coward · · Score: 0

    That's not a VDSL thing, that's due to the way your ISP has implemented it (AT&T I am guessing).

    I'm in the UK, I have VDSL2, and while they currently supply their own modem (and would rather you used it, but they don't stop you using something else), they are going to provide another option where they don't provide the hardware, they leave it up to the ISP who is buying the connection (or the end user if the ISP doesn't want to). Users on older connections can still use other VDSL2 modems if they want, but it isn't that necessary because the telco supplied modem works well and is just a simple ethernet bridge.

    The router that you connect to that modem has to speak PPPoE with simple username/password authentication, so basically anything will work as long as it has ethernet (and/or a built in VDSL modem). No certificates or complicated setup needed.

  62. accomplished EXACTLY what I want 3/3 by Anonymous Coward · · Score: 0

    Continued from -> http://slashdot.org/comments.p...

    As to your "wannabe shrink" advice? Care to show us your qualifications?? YOU Lumpy, don't have them - period. Then again, that's libelous too, now isn't it?? You're a REAL PRIZE pal, you have NO regard for laws do you, you little shit???

    Odd you stopped posting though after I exposed you libeling me though isn't it -> http://yro.slashdot.org/commen... after you've been on a "posting spree" for months now, funny you cease suddenly eh? Not - it had to be done, a little "name & shame" with facts & truths you can't dispute.

    No more than anyone here can on my hosts posts (issuing bogus downmods on them, but nobody does on adblock posts & it's SHIT compared to hosts - anyone doesn't *like* that? They're FREE to debate me in my hosts posts, I freely declare it there... only thing is, you've given up even *trying* that since I scorch your asses each time you do, & you KNOW it, hence the hit & run downmods from Lumpy, and yes, you Lumpy won't post where I asked you to since I suspect it WILL show you cheat the easily cheated so-called moderation system here).

    APK

    P.S.=> Slashdot's BIGGEST problem? You can't face an accuser (even courts of LAW allow that) with downmodders. That says WORLDS about this place, no id'ing the 'detractor/attacker' & it says WORLDS about those who designed it, 1 of 2 things (both are no good): First, it says they are deceitful little backstabbers who operate that way themselves, OR, secondly, that they LIVE ON FIGHTS & arguments (like newspapers do well on, controversial topics, knowing how oddly, even people who hates fighting (me believe it or not, but has to be done @ times) will watch one... & they LIVE on views/posts here or any website, but most allow you to see who your detractor is when that happens on post ratings... NOT this place - THAT needs a fix, bigtime)... apk

  63. Then one of us doesn't understand NAT by Anonymous Coward · · Score: 0

    Might be me, but I doubt it.

    1. Re:Then one of us doesn't understand NAT by udippel · · Score: 1

      Even an AC can be right. I was reading something else into the grandparent, who is right, of course. Mea culpa maxima.

  64. Perhaps rule is the wrong word by Anonymous Coward · · Score: 0

    Mapping might be a better word

  65. Buy a Mikrotik by Anonymous Coward · · Score: 0

    I use Mikrotik routers at home and in SOHO environments. They have models in all price ranges and are extremely powerful for what you are paying. They run a custom version of Linux (RouterOS) on their proprietary boards which use very little power.

  66. Lastly, as to being an "expert"? by Anonymous Coward · · Score: 0

    Everyone is: Anyone you MEET, knows more about something than YOU do... we're all idiots, & we're all experts, in something... & the MORE I know/learn? The more I find out I have to learn - especially in computing.

    Now I do know 1 thing: When someone LIBELS me, clearly? I am not going to "sit around & take it", especially when it's designed to ruin my professional status OR reputation, e.g. -> http://yro.slashdot.org/commen...

    Which THAT, the post parent to it, CLEARLY is (just for me posting FACTS Lumpy couldn't dispute I posted parent to HIS libelous reply to that post parent to his of mine).

    Got it? Good...

    APK

    P.S.=> I wrote the moderation staff here today with a question, & am awaiting their answer/decision - whatever it is? I will ABIDE by it too (unlike you scumbags around here, Lumpy)... apk

  67. Re:So, will a 2005-era routers get a firmware upda by BUL2294 · · Score: 1

    But you bought an off-the-shelf PC in 1998 with standard components. I'm talking about a (mythical) fridge with unique components, unique software, unique drivers, etc. Sorry, but an IoT device will likely never run more than a "+ 0.1" version higher of an underlying OS & related software ("+ 0.2" for Linux)--given track records of manufacturers working on old products. They won't open source everything for fear competitors would use it competitively against them. To add, even if they did open source the whole IoT fridge, you're assuming that someone would actively pick up the project... Simply open sourcing something & dumping it on the Internet doesn't mean anyone's actively interested & working on that project.

    --
    Windows 3.1x calc: 3.11 - 3.10 = 0.00