Slashdot Mirror


Duplicate SSH Keys Put Tens of Thousands of Home Routers At Risk

alphadogg (971356) writes A setup mistake has apparently left hundreds of thousands of home routers running the SSH (Secure Shell) remote access tool with identical private and public keys. John Matherly, founder of a specialized search engine company whose technology is used for querying Internet-connected devices, found more than 250,000 devices that appear to be deployed by Telefónica de España sharing the same public SSH key. A different search found another 150,000 devices, mostly in China and Taiwan, that have the same problem. Matherly said in a phone interview on Wednesday it is possible the manufacturers copied the same operating system image to all of the routers.

114 comments

  1. No surprise... by jasno · · Score: 5, Informative

    Most embedded guys are batting out of their league and don't have a clue when it comes to security... and I say that as an embedded guy who often has to do exactly that to get the product out.

    Most embedded development I've done is far from 'software engineering' - it's whack and hack until the tests pass(often because you loosened the testing requirements).

    --

    http://www.masturbateforpeace.com/
    1. Re:No surprise... by sinij · · Score: 5, Insightful

      Government already demands product certification (e.g. FIPS), it is time corporate and individual consumers started doing the same. We expect our power supplies to not electrocute us, there is a certification program to ensure that is the case, why is when it comes to data security we are so lax?

    2. Re:No surprise... by BVis · · Score: 0

      1) "Gubmint Bad", or
      2) General ignorance, or
      3) Billions of lobbying dollars from the manufacturers ensuring that the cost of each unit doesn't go up $1, or
      4) ...
      5) PROFIT

      --
      Never underestimate the power of stupid people in large groups.
    3. Re:No surprise... by gmack · · Score: 1

      They could do that, but then Telefonica wouldn't be able to buy the routers from China for $15 each (non wholesale price for the exact model Telefonica had in my house when I lived in Spain).

    4. Re:No surprise... by internerdj · · Score: 3, Informative

      My first job was a contract to a network equipment manufacture. I spent most of my time in their hardware division. At least for that particular company, hiring was based entirely about making hardware. Lots of electrical engineers, a few structural guys to do placement, software engineers were only for the network management division. A lot of the guys who were tasked with writing the embedded stuff were out of their league to write code period, but project management was so physical engineering heavy that they didn't understand what was going wrong. So yeah, I've seen the same thing.

    5. Re:No surprise... by bobbied · · Score: 1

      Most embedded guys are batting out of their league and don't have a clue when it comes to security... and I say that as an embedded guy who often has to do exactly that to get the product out.

      Most embedded development I've done is far from 'software engineering' - it's whack and hack until the tests pass(often because you loosened the testing requirements).

      Gee man, get a spine and at least raise a stink about the problem next time. I understand that sometimes you gota just deliver what you got for business reasons but if you keep doing that without making a point about the quality and security of the solution, eventually they will *rightly* hold you responsible for the failures. Such stuff can get hard to hide on a resume. Do the *right* thing as often as you can and when someone forces you into doing the wrong thing, document the issue, if for nothing else but to CYA.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    6. Re:No surprise... by brunes69 · · Score: 2

      FIPS is a joke and doesn't really do much of anything to ensure real security. Its just a compliance checkbox. An appliance running a piece of software can be 100% insecure from the ground up and be FIPS certified quite easily.

    7. Re:No surprise... by Anonymous Coward · · Score: 0

      IMHO, we're trying to be optimistic that no one would be interested in our computing resources.

      I think in general, most computer users think that if they can drive a car, they should be able to use a computer. I've been starting to wonder if we shouldn't have a similar licensing program for users? I know, computer users can't physically damage anyone until you take into account cyber bullying and those help desk calls that seem so idiotic, you wonder where their head is. Tech Support probably wouldn't get nearly as much volume if there was enough testing to say, sure this person has a fundamental grasp of technology.

    8. Re:No surprise... by sinij · · Score: 3, Insightful

      FIPS is not a joke - it ensures that that your cryptographic algorithms are implemented correctly and meet the standard. So you don't generate matching private/public keys or all 0 keys and other preventable but non-obvious to people outside of crypto mistakes. FIPS does not guarantee that you use these algorithms intelligently, there are other certifications that do that.

    9. Re:No surprise... by Lumpy · · Score: 2

      On the same note, Most CS guys could not survive 10 minutes in an embedded systems world. And it's not because those of us in Embedded systems don't have the skills, it's because the Idiots in upper management wont let us have the resources to do it right. If I can give you 900% more security by raising the cost of the box by $0.10 each then you freaking do it, not the "it will probably go unnoticed, so it's not that important" crap I hear.

      --
      Do not look at laser with remaining good eye.
    10. Re:No surprise... by Anonymous Coward · · Score: 0

      FIPS does not help this. It would blame the owner for not replacing the default SSH keys in the first place.
      SSH keys are typically asymmetric. That makes it difficult for me to understand how this could have worked at all. Maybe a long private key could have fit into a short public key field???

    11. Re:No surprise... by NotInHere · · Score: 2

      Yes please, require 10 certifications until you can connect a router to the internet. Best is the build is signed, and the user's access to the system is restricted, otherwise they can install malware because of infected computers. Of course every single of those 10 certifications needs money, but everybody can pay 1.000.000$ for releasing a build, so thats no problem. With government certifications, it would be ensured that insecure and uncertified router firmwares like dd-wrt are forbidden, which is good for users because of security and companies because then they can deliver an even better experience to their customers.

    12. Re:No surprise... by ColdWetDog · · Score: 1

      IMHO, we're trying to be optimistic that no one would be interested in our computing resources.

      I think in general, most computer users think that if they can drive a car, they should be able to use a computer. I've been starting to wonder if we shouldn't have a similar licensing program for users? I know, computer users can't physically damage anyone until you take into account cyber bullying and those help desk calls that seem so idiotic, you wonder where their head is. Tech Support probably wouldn't get nearly as much volume if there was enough testing to say, sure this person has a fundamental grasp of technology.

      This works out so well for driving. No, the cat is out of the bag. If it is a 'utility' then it has to be so simple that anything with opposable thumbs can use it.

      --
      Faster! Faster! Faster would be better!
    13. Re:No surprise... by brunes69 · · Score: 3, Insightful

      It is a total joke.

      FIPS 140-2 ensures your algorithm is part of a standard set - big deal. It does no investigation at all as to how you use that algorithm or why you use it. If you are using AES with a FIPS-certified library, you get the checkbox. Nevermind the fact that the private key you are using is sitting in plain text on the disk.

      Its the same as all federal standards - FedRAMP, FIPS, FISMA, ISO 27K. They all do *SOME* things, but none of these standards, or any intersection of them, actually do anything with regards to real secure engineering. Note, I am not even sure it would be close to practical to do this. I am just raising awareness that saying that an application is "FIPS certified" is next to useless.

      Source: I have dealt with getting applications certified in all of these umbrellas, and more. It is an extremely time consuming and expensive process for all involved to get certified - but in the end does very little in terms of real application security. But it sure makes the auditors a lot of money!

    14. Re:No surprise... by sinij · · Score: 2

      First, there is no such thing as perfectly secure information system. The best we could do is mitigate identified risks. The best any standard could do is specify how to mitigate specific risks.

      In case of NIST CAVP (part of FIPS testing most people are familiar with), the risk they are mitigating is that cryptographic algorithm you are using is flawed in some way. This certification program is hugely successful, there are robust standards and specs, and hardly anyone these days end up with bad algorithms because free certified reference implementations and free testing vectors were made available.

      Second, different aspects of FIPS program focus on different risks. For example, at higher certification levels (e.g. CMVP FIPS 140-2 Level 3 or 4) the program provides very robust and comprehensive assurance that both algorithm and methods of use of these algorithms within cryptographic module is secure. I am too lazy to dig through the specs, but I am positive that at level 3 it explicitly examines key storage. The flaw with FIPS is actually opposite of what you state - the level of scrutiny ramps up so rapidly that it is impossible to satisfy it only with a software implementation at above level 2. As a result, overwhelming majority of certifications are against lowest tiers that are limited in scope.

      Now, people look at CAVP certification (algorithm testing for software product) and make ignorant statement that the ENTIRE FIPS PROGRAM is ineffective. Even when it is very evident that it accomplishes exactly what it promised to do. To leave you with an example - PCI (payment transactions) requirements cap at FIPS 140-2 level 3. This is stuff that touches MONEY! FIPS 140-2 level 4 is spook-level robust, they even have a requirement to trip zeroization if you attempt to freeze or x-ray the chip.

    15. Re:No surprise... by OrangeTide · · Score: 1

      Sure, we can start doing product certification. You won't be able to buy $15 routers anymore though, they'll go back up to $150.

      --
      “Common sense is not so common.” — Voltaire
    16. Re:No surprise... by brunes69 · · Score: 1

      FIPS level 3 has nothing to do with software, that is the level which requires safeguards against physical tampering - tamper-evident seals etc. Again, nothing to do with the actual operation of the software. Level 4 takes Level 3 up a notch requiring even more hardening around "the module"... but AGAIN, nothing about how your software actually USES the module. Such a thing is totally outside the scope of FIPS.

      FIPS is an outdated standard. It made sense when it was created and crypto was not well understood and poorly standardized. Today it adds little value because almost all software on earth uses standard crypto libraries.

      Don't even get me started on PCI, which isn't even worth the paper it is written on.

    17. Re:No surprise... by StikyPad · · Score: 2

      FIPS may not be a joke, but most government networks are, especially, but not limited to, those outside of the DOD and IC. They are (in large part), administered by people who follow proscribed procedures, not people who understand what they're doing or why. While some "rogue" administrators will implement best practices beyond those they're required to do, they are the exception, not the rule -- especially admins who actually understand what they're doing rather than overestimating their own competence, which is its own problem. One need only look at the recent public government network compromises to see the consequences of these security procedures, and then apply the iceberg principle -- for every compromise that's seen, there are almost certainly many more that go unseen.

      And of course, all the best technical precautions in the world can't protect you from social engineering, insider threats, and/or 0-day exploits. If we've learned nothing else in the past year or two, it's that the deck is stacked very highly in favor of attackers, especially targeted attacks by determined state actors.

      Given the above, and the high-profile targets that government networks represent, I would be surprised if most, if not all of them, have been compromised. We like to make a lot of noise about China attacking us, but we almost never mention the country known for the "best" malicious software, which is Russia. Google "Turla," or "Uroboros," for example, and they're hardly mentioned in popular media, let alone in official statements. I suspect that the Russians are either as good as us at avoiding detection, that we just don't want to rattle any sabres by mentioning them publicly, or a little of both.

      I think Kaspersky was spot on when he said: "this war can't be won; it only has perpetrators and victims. Out there, all we can do is prevent everything from spinning out of control. Only two things could solve this [permanently], and both of them are undesirable: to ban computers -- or people."

      http://www.spiegel.de/internat...

    18. Re:No surprise... by sjames · · Score: 1

      And they'll still be insecure.

    19. Re:No surprise... by Anonymous Coward · · Score: 0

      You must be kidding right ?

      WIth embedded you must work within spec which are really tight.You need robust code. The best dev are embedded. They often are real engineer with a degree not mere software dev "hacks" . Think about software for medical equipment, flight instrument, Nasa ... and you think these guys don't know about security ? Hell they wrote the book! You're a joke. And please stop spreading bullshit. .

    20. Re:No surprise... by jasno · · Score: 1

      Are you kidding?

      Yes, some, usually large, companies have very competent engineering teams doing embedded work. Often, they're some of the smartest guys around(although IMHO the Verilog guys are smarter on average...YMMV). Then there are hoardes of engineers around them who do most of the integration, grunt work, bug fixing, etc. Their work is usually not thoroughly inspected by the smart guys.

      Then you have the thousands of small companies doing embedded development. They usually have one guy who is somewhat competent but needs to be fluent in everything from hardware bringup to adding a web configuration dialog. These are the guys that do things like try to stick ubuntu on their ARM board. These guys usually do not have a very comprehensive view of security, and even if they did they don't have the time or the budget to do it right.

      If I had a nickle for every company I've worked for who just wanted to integrate off the shelf(usually FOSS) components together and ship it as soon as it was barely functional...

      --

      http://www.masturbateforpeace.com/
    21. Re:No surprise... by Anonymous Coward · · Score: 0

      FIPS is absolutely a total joke:

      1. It mandates algorithms intentionally broken by the NSA.
      2. No, you can't disable those algorithms because then ou aren't FIPS-compliant -- it's not "you must support one or more of these algorithms," it's "you must configure exactly this set of algorithms".
      3. It is hideously out of date.
      4. FIPS certification requires a FIPS-certified environment. It's FIPS all the way down...
      5. It is not actually possible to have a FIPS 140-2 compilant system in the real world.

      Why #5? Well, it turns out that the only way to have a FIPS-compliant system is to:

      a) Have NIST (or whoever) do a FIPS certification on a single, physical system.
      b) Take those bits and physically deliver them (like on a CD) to another system OR use a FIPS-complaint transport to "securely" transport the data to the target system. Note that the target system can't participate in a FIPS-compliant secure transfer, since ... well, it's not yet complaint.

      So, use of SSH, FTP, or any other non-CD-based transfer mechanism instantly gets you out-of-spec. I wouldn't be surprised if the "copy" command is also out-of-spec, FIPS being such a crazy standard.

      How many systems do you suppose were built using gold-master CDs from the OS vendor?

    22. Re:No surprise... by Anonymous Coward · · Score: 0

      Your claims are complete bullshit, and you're an idiot.

      FIPS compliance is tiresome when it's required, but it's not the impossible feat you make it out to be.

    23. Re:No surprise... by OrangeTide · · Score: 1

      Only in ways that the certification fails to cover.

      --
      “Common sense is not so common.” — Voltaire
    24. Re:No surprise... by sjames · · Score: 1

      That depends. If the certification process is highly regulated, they'll find new and more spectacular ways to fail. It the certification itself is left for the market to figure out, they'll vote with their dollar and select for the rubber stamps and drive the people who actually know the standard and expect it to be met into another line of work.

  2. WTF? by Anonymous Coward · · Score: 3, Insightful

    Isn't TFS supposed to explain what it's talking about?
    1. Why does a router have public-facing SSH? The reason to use SSH on your router is to configure it, over a wired connection from your PC, innit?
    2. Why does a router come with SSH keys already installed? Don't you generate your own SSH keys?

    1. Re:WTF? by jeffmeden · · Score: 1

      Isn't TFS supposed to explain what it's talking about?
      1. Why does a router have public-facing SSH? The reason to use SSH on your router is to configure it, over a wired connection from your PC, innit?
      2. Why does a router come with SSH keys already installed? Don't you generate your own SSH keys?

      Given that they were deployed by one particular provider (Telefónica de España in this case) they probably requested a special firmware from the vendor for their CPE to allow remote management. And then did a bad job of keeping the master key safe (by putting a copy of it on 250,000+ devices). And then the vendor used it elsewhere, too.

      Honestly, after the Carna botnet, does anyone think the internet isn't a raging sea of completely compromised devices?

    2. Re:WTF? by Anonymous Coward · · Score: 0

      Isn't TFS supposed to explain what it's talking about?
      1. Why does a router have public-facing SSH? The reason to use SSH on your router is to configure it, over a wired connection from your PC, innit?
      2. Why does a router come with SSH keys already installed? Don't you generate your own SSH keys?

      The NSA keys have to get in there SOME way...

      CAPTCHA: Crafted

    3. Re:WTF? by Anonymous Coward · · Score: 1

      I could be wrong, but Telefónica (Actually Movistar) uses a Internet portal to manage your router: Portal Alejandra.

      In fact, some routers had their configuration pages crippled so you have to configure them throug the portal.

    4. Re:WTF? by Anonymous Coward · · Score: 0

      If I understand well the article, this is not an account SSH key pair but the SSH key pair used to identify the device.
      That is the public key that ends up in your .ssh/known_hosts file the first time you connect to a host.

      It is very likely that the device also share a common public key in the .ssh/authorized_keys file for the account used for remote access (probably to allow configuration via the ISP portal) but that is not a problem since public keys are designed for that.

       

    5. Re:WTF? by mrchaotica · · Score: 1

      The answer to both those questions (and more!) is the same: users are stupid, so make the router as easy as possible to configure even at the cost of security (assuming the programmer even notice that the security got fucked up).

      I'm surprised the damn things don't have public-facing telnet or UPnP (and for all I know, they might).

      --

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

    6. Re:WTF? by gmack · · Score: 1

      Isn't TFS supposed to explain what it's talking about?
      1. Why does a router have public-facing SSH? The reason to use SSH on your router is to configure it, over a wired connection from your PC, innit?
      2. Why does a router come with SSH keys already installed? Don't you generate your own SSH keys?

      Given that they were deployed by one particular provider (Telefónica de España in this case) they probably requested a special firmware from the vendor for their CPE to allow remote management. And then did a bad job of keeping the master key safe (by putting a copy of it on 250,000+ devices). And then the vendor used it elsewhere, too.

      Honestly, after the Carna botnet, does anyone think the internet isn't a raging sea of completely compromised devices?

      I don't think so. The pubic and private keys are only good for outgoing connections and not incoming.

    7. Re:WTF? by bobbied · · Score: 1

      Honestly, after the Carna botnet, does anyone think the internet isn't a raging sea of completely compromised devices?

      It's the World Wide Web and the Wild Wild West all at the same time.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    8. Re:WTF? by jeffmeden · · Score: 1

      I don't think so. The pubic and private keys are only good for outgoing connections and not incoming.

      Not funny. Anyway, having the private key is a valid way to authenticate inbound (if so configured) and its often enabled by default as it is thought to be a pretty good way to do it (until you put the same keys on a quarter of a million devices).

    9. Re:WTF? by nyet · · Score: 1

      The host key pairs are NOT used to authenticate the incoming user.

      They're used to prevent MITM attacks (by uniquely identifying the endpoint), so this statement

      "It’s hard to say if the key errors means that a remote attacker could log into all of the devices, as it would depend on how the routers are configured for remote authentication."

      It's complete bull; the article is written by a clueless moron.

      Attackers would have to use the keypairs to setup MITM attacks for EVERY machine they wish to compromise.

    10. Re:WTF? by msauve · · Score: 1
      "The host key pairs are NOT used to authenticate the incoming user."

      Are you speaking with specific knowledge of the device in the article? Because, in a general sense, keys can be, and are used for ssh authentication.

      AUTHORIZED_KEYS FILE FORMAT
      AuthorizedKeysFile specifies the files containing public keys for public key authentication; if none is specified, the default is ~/.ssh/authorized_keys and ~/.ssh/authorized_keys2.

      The device at hand is said to run Dropbear, which is "Compatible with OpenSSH ~/.ssh/authorized_keys public key authentication." The article does not provide detail on how the keys are used/configured, only that they match on many thousands of devices.

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

      Why in the world would you add a device's public host key to the authorized key file?

    12. Re:WTF? by msauve · · Score: 1

      Why in the world would you add a device's public host key to the authorized key file?

      Which authorized key file are you asking about?

      One can picture an ISP, who has to securely support many installed devices, going to a manufacturer and saying: "Here, put this private key in the devices, so when we connect we know it's one of our devices. And put this public key in the authorized_key file, so we can can connect easily without every support agent needing to know a password which works on all those devices." So, there's one case where they might put a device's public key (some proxy-type device used by ISP support staff to manage the CPE devices) into the CPE devices.

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

      Right, you would put Telefonica's pubic key into the authorized_keys on each device file but never the local device public key. The simple fact is that unless they are far more stupid than the article suggests this cannot be used to break into the routers.

    14. Re:WTF? by msauve · · Score: 1

      It shouldn't be a security issue. So what if they all have the same private key? It's very doubtful that those devices ever initiate connections, even less likely that private key is used for important authentication/authorization. It's probably only used so Telefonica can verify they're ssh'ing to one of their own devices before making changes.

      On the other side, having a public key in authorized_keys increases security. As I pointed out, it eliminates a need for a whole bunch of support personnel to know a password which is good on many thousands of devices. The security of those devices (presumably owned by and the responsibility of Telefonica) is entirely dependent on Telefonica keeping the matching private key, well, private. One can picture, say, a Linux box with the private key installed (known/accessible to only a trusted few superusers) on which every support agent is given a user account from which they can ssh to manage the CPE. All ssh connections can be logged. Agent leaves? Delete their account - there's no worry about them taking a password which gives access to a bunch of customer routers.

      The only issue would be if they used both sides of the same key pair on the device - then every device would have the info needed to get into any other device. That would be exceedingly stupid.

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    15. Re:WTF? by thegarbz · · Score: 1

      The reason to use SSH on your router is to configure it, over a wired connection from your PC, innit?

      What is this 2014? The PC I bought this year doesn't have a wired connection.

      2. Why does a router come with SSH keys already installed? Don't you generate your own SSH keys?

      Users are never trusted with such things. Also I've never seen one where the SSH key was configurable. I believe something like this should automatically happen on first powerup without any visible indication to the user that it is or has happened.

    16. Re:WTF? by nyet · · Score: 1

      Again, why would you use the host key for this purpose? Most likely the client would generate the key (no relation to the host key) they would want preloaded. The manufacturer has no reason to use the host key as both a host key AND a key in the authorized_key file. That is simply stupid.

    17. Re:WTF? by msauve · · Score: 1

      What are you babbling about? Define your terms, if you can. Which is the host? Which is the client? WTF are you talking about?

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
  3. "possible" by Anonymous Coward · · Score: 1

    Matherly said in a phone interview on Wednesday it is possible the manufacturers copied the same operating system image to all of the routers.

    Well, yes: 99% certainty is a "possibility".

  4. FTFY by Anonymous Coward · · Score: 2, Informative

    John Matherly, founder of a specialized search engine company whose technology is used for querying Internet-connected devices

    Translation -

    John Matherly, founder of a company who randomly portscanned over 350,000 internet-connected devices whithout their user's consect, for the sole purpose of enriching his company's bottom line.

    1. Re:FTFY by sinij · · Score: 2

      Yes, clearly what John Matherly did was by far more harmful than idiotic design decisions that resulted in such unforgivable "barn doors open" security holes. Because if he didn't disclose this vulnerability, nobody else would have found it and everyone would still be perfectly safe.

      /sarcasm

    2. Re:FTFY by Anonymous Coward · · Score: 0

      John Matherly, founder of a specialized search engine company whose technology is used for querying Internet-connected devices

      Translation -

      John Matherly, founder of a company who randomly portscanned many millions of internet-connected devices, for the purpose of trying to get people to wake the fuck up and start protecting their hardware.

      FTFY. And do you think this is the first global portscanning project? The second? The Tenth? Your wildest imagination is probably still low by half. His is the first to allow quasi-free browsing of the results, which is pretty generous considering there has only been one such project in the past (the carna botnet research data). If a vulnerability is seen in Shodan, the bad guys certainly knew about it years ago.

    3. Re:FTFY by Anonymous Coward · · Score: 0

      Translation - John Matherly, founder of a company who randomly portscanned over 350,000 internet-connected devices whithout their user's consent, for the sole purpose of enriching his company's bottom line.

      ++

      Anyone know what IP range this guy uses? I'd love to add it to my firewall block list.

    4. Re:FTFY by Anonymous Coward · · Score: 0

      Translation - John Matherly, founder of a company who randomly portscanned over 350,000 internet-connected devices whithout their user's consent, for the sole purpose of enriching his company's bottom line.

      ++

      Anyone know what IP range this guy uses? I'd love to add it to my firewall block list.

      All of them. Seriously he uses many cloud servers to do the scanning. Too many to block.

  5. Not the same as root user keys by Anonymous Coward · · Score: 0

    This is the fingerprint, not the root user's key.

    1. Re:Not the same as root user keys by jeffmeden · · Score: 0

      This is the fingerprint, not the root user's key.

      They are identified as having the same fingerprint (which is derived from the same source as the private key). So, someone with the private key for one device (ahem, anyone who has a copy of the firmware and knows how to use binutils) can authenticate to all devices.

    2. Re:Not the same as root user keys by F.Ultra · · Score: 2

      No they cannot, they can pretend to be the device to some user though without ssh complaining that the key is wrong. If they use the same ip and if they somehow can get between the user and his router.

  6. Anyone use it? by Anonymous Coward · · Score: 1

    Do the majority of users ever log into their device via ssh? So if everyone has the key you can decrypt other people's traffic, but the leaked keys in question probably don't allow for login.

    1. Re:Anyone use it? by bobbied · · Score: 1

      Of course they do... The whole point of having this set to the same thing on routers was that an ISP was providing their customers equipment (the router) and wanted to be able to manage the equipment for the customer so they arranged for access with the router manufacturer. The problem was the manufacturer then sold hardware with the same firmware image to general customers and thus exposed the key and security hole to a much larger audience....

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    2. Re:Anyone use it? by Anonymous Coward · · Score: 1

      "But it is questionable whether SSH should be running on a home router anyway"

      Use SSH they said. There is no winning with this crowed.

  7. not really "at risk" by JonathanP.Bennett · · Score: 1

    Not a great idea for the keys to be the same, but not really a security risk if ssh is never used. Now, the fact that there is an ssh port open to the world without the end user setting it up, that could be a problem.

    1. Re:not really "at risk" by sinij · · Score: 1

      I assume they have cert-only authentication enabled, in such case this would be not unlike having management interface with 'admin/admin' facing the world.

  8. A small note by Anonymous Coward · · Score: 0

    Often, the exact same problem happens when people clone/copy virtual machines, although the scope of security risk is obviously less in this case.

    Ideally, newly copied virtual machines should be assigned new SSH host keys.

  9. what most people don't think of doing by ihtoit · · Score: 1

    ...when the router comes out of the box it was shipped in, is power it up with the only network connection being a wired from port 1 to a pc, through which the router is locked to accept administrator connections from the currently conencted IP and machine ID ONLY (and the IP reserved for that machine), and ONLY via the wired LAN interface - from which point, you then change the wireless SSID and all the passwords FROM the defaults, and all that before you even physically connect it to the WAN cable. That way anything behind your router remains as practically secure as it's possible to get while connected to the Internet. Major problems such as that computer becoming permanently disabled are an easy fix, just perform a WAN-disconnected factory reset of the router and reconfigure it for another machine.

    --
    Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    1. Re:what most people don't think of doing by msauve · · Score: 1

      What's this "machine ID" you speak of? The MAC address? It's pretty easy to configure the same MAC on a different machine.

      Most people don't think of doing it that way because it's not a good way of doing it.

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    2. Re:what most people don't think of doing by jeffmeden · · Score: 1

      What's this "machine ID" you speak of? The MAC address? It's pretty easy to configure the same MAC on a different machine.

      Most people don't think of doing it that way because it's not a good way of doing it.

      That part was a little bizarre (if you are physically connected directly from PC to router it doesnt matter much what ID the PC might have) but as a whole it creates a pretty tight way of ensuring integrity of the router configuration. In particular, not allowing any inbound access from the WAN until a hard password is set, and not allowing any association to the WLAN until a hard encryption key/passphrase is set. However, these are two steps most users don't want to bother with (and more importantly, will call tech support to help them with when they fail to complete the tasks). Security, as we have currently designed it, is pretty hard for the layperson. Vendors optimize their devices for the path of least resistance (read: path of least tech support) to minimize costs, and we shouldn't be a bit surprised.

    3. Re:what most people don't think of doing by ihtoit · · Score: 1

      If your WIRED Admin system is plugged in to your LOCKED DOWN router how is someone OUTSIDE the LAN going to see it?? All they're going to see is an IP which accepts TCP packets. That could be a computer or it could be a data centre. Or it could be an NSA honeypot. Or a backbone connection via a rotary dial telephone in a small room a hundred feet below Kings Cross Station.

      Can you tell if I'm directly connected to the Internet or through a router or through a tethered mobile phone through a proxy? On a wired or wireless connection? On a dektop, phablet or a piece of rock with hammer and chisel? Or did I dictate this message with a piece of string and two paper cups to my friend up the road who then typed it in on a Telnet session then uploaded it using semaphore?

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    4. Re:what most people don't think of doing by Anonymous Coward · · Score: 0

      it could be the machine's MAC address or it could be the hostname or it could be a static IPv4 address. What does it matter when you can't access the router without a bruteforce because he's changed the login credentials?

    5. Re:what most people don't think of doing by msauve · · Score: 1
      What are you babbling on about? Most consumer NAT routers I've dealt with disable admin access from the "public" interface by default.

      Take the TP-LINK TL-WR841N, currently shown as Amazon's "#1 Best Seller in Computer Routers":

      Remote Management IP Address - This is the current address you will use when accessing your router from the Internet. This function is disabled when the IP address is set to the default value of 0.0.0.0...

      Similarly with the #2 Asus RT-N66, but they don't even tell you how to do it in the manual, you have to search their FAQs or go wandering around the Advanced Settings/Firewall page to enable remote management.

      So, what's this thing that "most people don't think of doing?" You mentioned trying to lock management to a specific PC on the "private" side. I pointed out that MAC addresses are easily spoofed, so that doesn't provide any real additional security from other devices also on the private network.

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    6. Re:what most people don't think of doing by ihtoit · · Score: 1

      the Virgin Media Netgear routers don't. Neither did their old Terayon modems. They'll both allow admin connections from anywhere by default.

      --
      Political debates have me rolling my eyes so much I think I got optical whiplash. I should sue. - Foamy The Squirrel
    7. Re:what most people don't think of doing by Anonymous Coward · · Score: 0

      remind us all again how you access a locked down router via wireless when the only admin access is set to a specific machine through a reserved IP on a wired connection?

    8. Re:what most people don't think of doing by Anonymous Coward · · Score: 0

      not to mention from that point also requiring a physical wired connection direct to the router via one of its LAN ports.

  10. This is a general problem by gweihir · · Score: 1

    It does concern ssh-keys, disk-encryption keys, etc. If the people doing this do not understand how encryption works, or are botching initial entropy gathering, the same or pretty close keys can end up on a lot of deployed devices.

    In general, this has to do with developer inexperience and (for older ones) incompetence.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    1. Re:This is a general problem by Anonymous Coward · · Score: 0

      Some of us can be inexperienced AND incompetent regardless of age.

    2. Re:This is a general problem by sinij · · Score: 1

      Cryptography knowledge in software development is very shallow. Most only know to integrate OpenSSL (without FIPS module). Ask them about entropy, and they start talking about the heat death of the universe. Even Linux kernel guys, who otherwise tend to be knowledgeable, would tell you that /dev/urandom is a desirable and secure choice.

      /rant

    3. Re:This is a general problem by gweihir · · Score: 1

      I do not dispute that. But if you are inexperienced, being incompetent is not really your fault IMO, and hence "inexperienced" is the main characteristic.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    4. Re:This is a general problem by gweihir · · Score: 1

      You are right about software developer. They routinely do not understand crypto, but they also routinely do not understand non-trivial algorithms, data structures and any other CS concept as soon as it is a bit more advanced.

      I'm a security person, and generally there is nothing with /dev/urandom. You have to make sure it is properly seeded though, otherwise you are screwed. On the other hand, using /dev/random in an entropy-starved situation is also bad, because it may effectively cause a lock-up. (Yes, this can happen in practice.)

      The problem is that the kernel-folks cannot resolve this issue. It has to be done on application side. For example, if you really cannot include some individual secure seeds, start up with a possibly bad temporary seeding generated from things like MAC and serial numbers (can be put into /dev/urandom) and after a while and some more entropy gathering, replace with a long-term key.

      Gathering entropy with application knowledge is not really difficult. For examples routers get a lot of entropy from precise packet timings. Do that until you have an estimated 10k bit of entropy, pump that into /dev/urandom, and only in the most bizarre will you have less than the 128 bit or so needed for a good seeding. There are numerous other possibilities. The problem with all of them, as you pointed out, is that you have to know what you are doing.

      Still, this is really pathetic. It is not that expensive getting a competent security consultant company with engineering credentials to look at what you do and recommend improvements if needed.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  11. Be A Good Geek by Guy+From+V · · Score: 2

    Every geek should be a good netNeighbor or netRelative and suggest or guide anyone we care about or don't wish to be fucked over by .gov/corporations/prick wardriving kids and suggest something along the lines of DD WRT or TomatoUSB on their routers that may be ripe targets...maybe even offer to help them secure them, I'm getting pissed at all this crap that is going to get all of them and us reamed. I also like the idea of sticking it to all the evil and/or stupid bastards that let this stuff happen. I let an elderly neighbor of mine know a few months ago by naming my SSID something that might alert their kids or whomever is their "IT expert" (who happened to her daughter) to email a disposable account I set up so I could explain what was up and I spent 20 minutes getting it going for them. I told her to let me know if it needed any fixing with another one-time email anytime remotely. But really, Toastman's TomatoUSB is very stable and needs hardly any tweaking or fixing...probably less than stock firmware. Especially for the crappy Cisco FW that was on it - disaster waiting to happen. They are even on 5ghz N band now, the only other one than me (I'm on both 2.4 & 5). PS InSSIDer is a great wireless app.

    1. Re:Be A Good Geek by ColdWetDog · · Score: 1

      SCRAGGLY NECKBEARD GEEK: "Hi neighbor, I'm a geek and I'd like to help you configure your router so you aren't at risk for man-in-the-middle attacks and other security risks."
      NEIGHBOR: "Wut? A guy called on the phone from Microsoft the other day and helped me through all of that."
      SCRAGGLY NECKBEARD GEEK: "No no no. That's one of the problems I need to help you with."
      NEIGHBOR: "But he already fixed it. Besides, you're weird looking and I don't want you messing with my computer."
      SCRAGGLY NECKBEARD GEEK: "It's OK, I just have to work with your router."
      NEIGHBOR: "That's in the garage - I still don't want you messing with my tools."
      SCRAGGLY NECKBEARD GEEK: "This is really important!"
      NEIGHBOR: "Go away or I'm calling the Police."

      --
      Faster! Faster! Faster would be better!
    2. Re:Be A Good Geek by Guy+From+V · · Score: 1

      Take a valium, If you read my post I let them email me if they needed help and we aren't strangers.

    3. Re:Be A Good Geek by Anonymous Coward · · Score: 0

      I think it was more in jest about your advice of "Every geek should be a good netNeighbor or netRelative and suggest or guide anyone we care about [...]" that he was targeting with his reply. The one thing you left out was just how bad of a precedent you are setting to convince your neighbor to email you for some good advice. Good advice is fine but they would have no idea if you were a perp who just wanted to help them install a RAT on their PC so you could steal their banking information and empty their accounts.

    4. Re:Be A Good Geek by Guy+From+V · · Score: 1

      I guess I left out a lot of info, but I get the point. The gist of this whole scenario is that my neighbor's daughter is pretty hot so it ended up being all good.

  12. Costs matter these days by Anonymous Coward · · Score: 0

    We all know costs matter and security is not worth the investment in many companies mindset. Router firmware has always been a weak link for so many reasons. Its now become a viable access point of breech only because more and more routers have been implemented. I have no doubt most consumers have no clue about updating firmware or how the settings of a router affect security or function. Consumers basically want Plug N Play for everything tech. Its why we are seeing software and operating systems updating on their own, security scanning in the background and a general consensus of not leaving it up to the end user to do much of anything. So when the hardware makers screw up, then who is it that will fix it?

  13. Fantastic! by Anonymous Coward · · Score: 2, Insightful

    In the meantime, I can't even get my Canon wi-fi printer to connect to my router, but some script kiddy can see all my porn.

    What the hell is wrong with software these days?

    1. Re:Fantastic! by Lumpy · · Score: 1

      Blame the executives. They are 100% the fault of crap products, crap firmware, and crap software.

      --
      Do not look at laser with remaining good eye.
  14. UL (Underwriters) is a private, for-profit company by raymorris · · Score: 4, Informative

    Most electrical equipment mass-marketed in the US is tested by UL (Underwriters Laboratories). Many consumers and most large purchasers recognize the UL mark as indicating a degree of safety. Contracts can specify that products an components meet various UL standards. That's why your router's power suppy wall-wart probably has the UL mark, and doesn't generally catch fire.

    The "Gubmint" doesn't force UL certification or listing, purchasers choose UL listed products. There's no "billions of lobbying dollars", in fact companies PAY to have their products tested, because if they are recognized by UL they don't sell nearly as well. Not only do individual consumers recognize the UL logo, but purchasing agents for Walmart and Target know they'd rather buy and sell UL tested products, so if you want Walmart to order 500,000 fire safes from you, you better have UL test it.

    So no, it doesn't have anything to do with "gubmint" or "lobbying" - UL or another organization could check the firmware in the router just like they already check the power supply circuit.

  15. Re:UL (Underwriters) is a private, for-profit comp by sinij · · Score: 1

    There are already programs in place. One example, NIST certifies private security testing laboratories to test according to FIPS standards. It just nobody asking for certified products outside of the government procurement.

  16. Why isn't port 22 blocked by default? by danbob999 · · Score: 1

    By the router's firewall? Why is SSH enabled to begin with?

    1. Re:Why isn't port 22 blocked by default? by Anonymous Coward · · Score: 0

      That would make those keys far less usable, which w Would kinda defeat the whole point.

  17. What are the actual risks to your network? by nuckfuts · · Score: 1

    OK, this is clearly a bad thing, but I don't think it means that your private LAN is immediately accessible to people all over the world does it? Multiple routers using the same keys means you could be tricked into logging in to someone else's router without knowing, but that would still require some way of directing your traffic to the imposter's device to begin with, such as DNS hijacking.

    Knowing someone's keys would also allow you to encrypt/decrypt traffic as that device, facilitating a man-in-the-middle attack, but still, you need a way to get in the middle between two devices. This is not something that's trivial to do from one arbitrary location to another.

    I'm not suggesting this isn't a serious problem, but I don't think it's as bad as, say, remote administration being enabled with a known default password.

    1. Re:What are the actual risks to your network? by nyet · · Score: 1

      No, in this case, knowing the host key would let you pose as the host.

      Then again, you don't even generally need the host key to post as the host because 9 times out of 10 nobody actually verifies that the presented host key matches the expected host key.

      If the host is unknown, generally they simply assume the key is correct.
      If the last stored key and doesn't match the one presented, they generally ignore the error that ssh spews telling you of a potential MITM attack.

    2. Re:What are the actual risks to your network? by F.Ultra · · Score: 1

      They probably will but ssh will force you to manually remove the key from the known_hosts file if the key doesn't match, atleast openssh does that.

    3. Re:What are the actual risks to your network? by PetiePooo · · Score: 1

      OK, this is clearly a bad thing, but I don't think it means that your private LAN is immediately accessible to people all over the world does it? Multiple routers using the same keys means you could be tricked into logging in to someone else's router without knowing, but that would still require some way of directing your traffic to the impostor's device to begin with, such as DNS hijacking.

      Finally, a breath of sanity... Thank you, nuckfuts! A shame this is the bottom thread in the post.. at least when I got here.

      There is a huge difference between a host key and a user key. These consumer devices all share the same host key, which is only used by the client to verify that the host you're connecting to is the host you think you're connecting to. This is the key in /etc/ssh/ssh_host_rsa_key for those with access to a Linux shell, and is never encrypted or password protected. How do I know this? Because there's no way to determine what user keys are in a host's authorized_keys file with just an unauthenticated connection. However, when a client connects, the server always sends the host's public key along with a challenge signed by the host's private key.

      The host key is only ever used for authentication, never for authorization, which is to say it identifies the server you're connecting to, but in no way grants any privilege to access it. The only risk here that I can think of is a MITM attack. Since the host key is well known, someone could fiddle with your DNS or local ARP tables and make a victim connect to their evil server without the scary "MAY HAVE BEEN COMPROMISED!!!" warning you get when the destination host key doesn't match what's in the known_hosts file.

      If someone can paint a more frightening scenario (based on known host keys, not user keys), I'd like to hear it. If you don't understand the difference, don't bother trying.

    4. Re:What are the actual risks to your network? by msauve · · Score: 1

      Which is probably the exact reason Telefonica wanted the same private key on all their managed CPE - who wants to manage a 250000 entry known_hosts file?

      --
      "National Security is the chief cause of national insecurity." - Celine's First Law
    5. Re:What are the actual risks to your network? by F.Ultra · · Score: 1

      They would need that anyway since each new ip would add another row so it's probably more that they wrote a single image to all devices instead of autogenerating a new ssh key upon first boot.

  18. Re:UL (Underwriters) is a private, for-profit comp by m.dillon · · Score: 1

    Kinda Apples and Oranges. UL testing is fairly straight-forward. The quick explanation - they stress the device in various ways and see if it catches on fire. Checking a crypto setup to a reasonable level of satisfaction can't be done externally. The code for the entire system must be examined, and that is relatively difficult to do.

    -Matt

  19. Re:UL (Underwriters) is a private, for-profit comp by sjames · · Score: 1

    After the recent crypto fiasco, a NIST certification might be seen as a mark of shame.

  20. Sounds good, but shelves full of UL say otherwise by raymorris · · Score: 3, Insightful

    > Back then you could justify the increased costs associated with getting the UL stamp of approval as a benefit to the consumer's safety.
    > Today, if you tried this, you'd get absolutely buried.

    That "sounds good", especially if it plays well with your personal political feelings. However, go pick ten random electrical products at your local big box store. Notice that at least nine, if not all ten, do in fact have the UL mark. The actual fact is that today almost all manufacturers do indeed "justify the increased costs associated with getting the UL stamp of approval". You can be surprised that they do, but you can see with your own eyes that they do. If that doesn't fit your current ideas, your ideas must be mistaken.

  21. connection attempts to my home router from UoM by Anonymous Coward · · Score: 0

    Ever so often I check to see whats running on computers that attempt to connect my home router. This ip address http://141.212.121.200/ was from The University of Michigan.

  22. Idiots by Anonymous Coward · · Score: 0

    in fact companies PAY to have their products tested, because if they are recognized by UL they don't sell nearly as well

    So they're paying to sell less?

  23. Purchasing a WRT by hcs_$reboot · · Score: 1

    I first ensure the wrt is openwrt compliant. Then the 1st thing I do after purchase is installing openwrt.

    --
    Slashdot, fix the reply notifications... You won't get away with it...
  24. Telefonica has done this for ages by Anonymous Coward · · Score: 0

    The last 3 DSL routers I've had in 8 years from Telefonica all came with remote access (WAN side) enabled, albeit from a certain IP range only. I close that down as soon as I get the new router but needless to say most people won't know how to do it or actually even care.

  25. My typos are not UL approved by raymorris · · Score: 1

    Apparently my post was not tested for typos.

  26. IoT by kernel_user · · Score: 0

    This is exactly the kind of thing that will happen with the Internet of Things if that term still exists in a few years. Billions of devices connected to the internet, designed by amateurs with no security in mind.

  27. Re:UL (Underwriters) is a private, for-profit comp by thegarbz · · Score: 1

    Not only do individual consumers recognize the UL logo, but purchasing agents for Walmart and Target know they'd rather buy and sell UL tested products, so if you want Walmart to order 500,000 fire safes from you, you better have UL test it.

    So no, it doesn't have anything to do with "gubmint" or "lobbying" - UL or another organization could check the firmware in the router just like they already check the power supply circuit.

    You're assuming perfect certification and a lack of counterfeiting. The running joke at the moment is that CE stands for Chinese Engineering rather than being the European equivalent of UL. We see products in Australia a lot carrying both the UL and CE logos, because frankly the same products are sold all over the world. It quickly becomes apparent when dismantling them that either the certification is fake or that the certification isn't worth the paper it's printed on. In fact early last year if I recall someone was fatally electrocuted by an after market mobile phone charger which among other things carried the UL and CE markings. Chinese made of course.

    I too have bought a 2A charger from fleabay that had a UL marking on it. I caught it early enough but when I was pulling about 0.8A it got hot enough that I was afraid it may burn my house down, and into the bin it went.

    I've also seen a water filter with a TUV certificate claiming it removes 100% of everything down to a certain size. If anyone has seen such TUV certificates for filtering equipment before, they'll know TUV has never printed 100% on anything.

    For a certification scheme like this to work you need perfect certification combined with perfect customs and border control to prevent fakes entering the country. That is a little harder to achieve.

  28. It's rare by Ketorin · · Score: 1

    A cheap home router with SSH enabled...

    Where can I buy this?

  29. not perfect, just better than nothing by raymorris · · Score: 1

    >. You're assuming perfect certification and a lack of counterfeiting

    No, I'm pointing out that it's better than NO testing or certification. If 5% of the products are counterfeit, that means 95% aren't. Compare the safety of what's one the shelves at Walmart vs what street vendors sell in Mexico or China. It does in fact work.

    > For a certification scheme like this to work you need perfect certification

    There's no "would need". UL has been testing products for over a hundred years, so it's not theory. UL certified products do in fact have a much better safety record than untested products. UL LISTED products are in the middle.

    1. Re:not perfect, just better than nothing by thegarbz · · Score: 1

      Compare the safety of what's one the shelves at Walmart vs what street vendors sell in Mexico or China.

      Well that's kind of my point. These stories while sensational are actually quite rare. I think you were being generous to my argument about 5% being counterfeit, in the western world it would be lower. But equally low are the number of products we have major security issues with. Yes it seems like every week there's another story about some small embedded device with a problem, but every week 20 new such devices hit the market. 10s of thousands of home routers? I have about 5 routers in my home, so the effect is like the size of a suburb.

      You get just as many fake products as you do security issues. The only thing security certification would do is link the two together with the end user being none the wiser.

      Also I didn't mean to imply UL testing wasn't perfect only a technical level. What I meant to say is that it was imperfect in the sense that the mark means something. Kind of the same reason why microsoft started using holographic CDs, Castrol oil now has a holographic sticker embedded in the plastic case, etc. A certification where the end user can't tell if the certification is true or not is imperfect. I compare that to a perfect scheme like the ones used in hazardous area applications (except for FM approval of course which is just like UL). The IEC scheme requires a full certificate serial number to be printed on the product barcode and the user can at any point go to their website and see the certificate which also describes the product in detail.

      UL could go down that route by issuing certificate numbers to be stamped on products. Same goes for any other certifier who currently simply permits the use of their logo without any ability for an end user to trace the certification back to the certifier. Right now, the mobile HDD next to me has the UL logo on the label. I have no idea if it is legit or not, and have no way of finding out.

  30. Re:Sounds good, but shelves full of UL say otherwi by BVis · · Score: 1

    You're seeing an agenda where none exists. Yes, most electrical devices found in the home today have the UL mark on them; I never said otherwise. My point is that currently that is inertia from a decades-old system. If you tried to implement a brand new UL-type company TODAY, you would never succeed. Anything that increases costs, even if it adds significant value, is seen as evil and "unnecessary regulation", and therefore to be avoided at all costs. Especially when the value added is something that the average consumer does not and does not care to understand.

    --
    Never underestimate the power of stupid people in large groups.
  31. "admit it" by Anonymous Coward · · Score: 0

    after i "accidentally" got a login/password correct on a home-ip on port 80 i commenced to add a port-forwarding rule for port 80 to ...#NO CARRIER

  32. All router makers have bad security, none have fir by raymorris · · Score: 1

    > . I think you were being generous to my argument about 5% being counterfeit, in the western world it would be lower. But equally low are the number of products we have major security issues with.

    Being in this industry, it seems to me that ALL major router manufactures have had multiple major security problems. NONE of them have had major "catch on fire" problems to my recollection. So the assertion that the number of devices with security problems is the same as the number that have fire problems is false in the extreme.

  33. * or counterfeit, but UL tests for fire by raymorris · · Score: 1

    My reply didn't exactly match your comment, but I'd say it's true for counterfeiting too. Pick a random electronic device at a random big-box store. It's probably NOT counterfeit. It probably DOES have lax security.

    Even more, I'm talking about testing like UL does. UL focuses primarily on fire safety, and it works - our electronic devices rarely catch fire. Fire safety is a success. Data safety is a miserable failure - I can personally hack most devices.

    1. Re:* or counterfeit, but UL tests for fire by thegarbz · · Score: 1

      I don't think the point was to actually have UL look into it, but rather create a security certification scheme.

      But while your comments are true in the general sense I think there is more to it than that. I don't think I've been to a random big-box store in years. Now that could be our local market where the big-box stores do their best to screw users with ridiculous prices, but one thing that is very popular in Australia for instance is drop shipping. In many cases I have no idea at all where the device comes from. It certainly doesn't come from the people from whom I order. The odds of it being counterfeit are high enough in that regard. There's also been a massive uprising of brandless and Chinese imports. I'm not talking about recognised Chinese names like Hauwei or TPLink but rather names that just look like cheap knock-offs of the real thing.

      Likewise while every major vendor has had a security SNAFU, I don't recall seeing a major vendor who has had a SNAFU affect every one of their products. Routers are especially guilty in the constant change department. My best personal example of this was buying a Linksys router and having it die after a week (no idea why). I took it back to the store and when I got it home it looked the same, except for different firmware and different hardware revision codes. Best of all when I went online to check if the firmware was current, it wasn't, and the real kicker was the latest firmware worked only on an EVEN NEWER revision code.

      1 product, 1 model, 2 weeks, and at least 3 different revisions on the market, probably more in stores which don't move stock very quickly.

  34. Re:UL (Underwriters) is a private, for-profit comp by arglebargle_xiv · · Score: 1

    There are already programs in place. One example, NIST certifies private security testing laboratories to test according to FIPS standards. It just nobody asking for certified products outside of the government procurement.

    FIPS 140 certification, which I assume is what you're referring to, is almost worthless in terms of determining how resistant to real-world attack a product really is. It would have done nothing to prevent the problem discussed here. Its main use is as a measure of how desperate a vendor is to get government contracts, which is also why no-one asks for it outside government procurement.

  35. Re: Sounds good, but shelves full of UL say otherw by Anonymous Coward · · Score: 0

    UL listing is important because many businesses will only buy equipment certified by a Nationally Recognized Testing Laboratory (NRTL). UL isn't the only NRTL, here's a list. That market can obviously support more than just UL. I think that if businesses started insisting on certifications for security, the market could support a few security certification labs.

  36. Re: UL (Underwriters) is a private, for-profit com by Anonymous Coward · · Score: 0

    I don't think you know what you're talking about. This would have been caught and prevented if they went for FIPS testing.

    "Cryptographic key management (generation, entry, output, storage and destruction of keys)"

    Which needs full documentation and testing.

  37. test by Anonymous Coward · · Score: 0

    please ignore