FTC Forces Asus To Improve Router Security (helpnetsecurity.com)
An anonymous reader writes: The FTC is actively trying to make sure that companies secure the software and devices that they provide to consumers, and a settlement with Taiwan-based hardware maker ASUSTeK Computer is one step towards that goal. The complaint was raised after well-meaning hackers exploited a weakness on Asus routers and left note on victims' drives notifying them of the matter. Later, a researcher discovered an exploit campaign that abused vulnerabilities to change vulnerable routers' DNS servers. According to the settlement, the company will have to establish and maintain a comprehensive security program subject to independent audits for the next 20 years.
That's not a bug, it's a feature!
HexaByte - he's a square and a half!
This forces procedure changes. It doesn't force improved security.
It's a good thing. But, don't get a false sense of security.
I guess Caveat Emptor is now being taken care of by mother government...
Modern app appers know that ONLY apps can app apps, so they should force ASUS to use APPS on their routers instead of LUDDITE firmware!
Apps!
Did anyone else read the headline as:
FTC Forces Anus To Improve Router Security
?
I've generally preferred Asus routers to its peers for quite some time. They've been great with providing firmware updates four years after release (d-link, I'm looking at you), doing simultaneous dual-band as advertised (netgear, I'm looking at you), their firmware is responsive and generally very stable (Belkin, I'm looking at you). Their mid-range units support multi-wan and make excellent print servers, and they've been very supportive of the modding community - most of their gear supports merlin, padavan, ddwrt, openwrt, and tomato, and their recovery mode is near-brickproof.
Yes, it's obnoxious that they had security issues, and yes, I replaced my N56U with a linksys ea6900 (and regretted until tomato was installed), but they're definitely better than most in my experience.
More to the topic, I wonder if this will yield some case precedent for these requirements industry wide. I can dream...
Apple, you have TOO MUCH security!
ASUS, you have TOO LITTLE security!
Make up you're friggin' mind Uncle Sam... Security is either good for everyone, or bad.
Doesn't have a third party firmware option available. End of Rant..
Personally, I use a couple of Linksys offerings that have excellent OpenWRT support. I have a fleet of WRT4300's and a 1900ac that actually come with a variant of OpenWRT and are well supported. They all have Layer 2 capable switch hardware (so you can do VLAN stuff) which is nice. The WRT4300's are about $40 used on E-,Bay and the 1900AC retail at about $135 new and $120 used. Running OpenWRT gives you a lot of capability.
"File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
Leaving routers wide-open to attack AND MARKETING THEM AS SUCH is not.
If Asus had marketed these as "here's a router, here's how you can hack it, here's how to plug the holes, and please don't do anything stupid like put it on a public network without fixing the holes and changing the passwords first"
and sold it to hobbyists rather than regular consumers, then there wouldn't (or rather, shouldn't) be any reason to drag the FTC into the matter.
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
The FTC, of all the entities that could possibly muscle in on this matter, wants a company to do something to increase consumer safety?
Ok, what does the story not tell? Are they going to demand that the routers be locked down to the point where the customer has no way of replacing the crappy firmware with something usable?
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
The government can force a company to harden its encryption (ASUS) but not soften it (Apple)? I'm on Apple's side in their conflict with the FBI, but I think this case with ASUS illustrates the primitive state our laws are in.
TP-Link routers ship w/ 11 yr old OpenSSL. Netgear & dlink ship with root access backdoors.
DD-WRT or Tomato if can't run either I get neither.
All the while the FCC and the EU are working on preventing users from protecting themselves by modifying the routers firmware:
http://tech.slashdot.org/story...
So the US FTC wants a Chinese manufacturer to provide security for Americans on the internet. That sounds about right. Heaven knows the US government has always kept our personal data secure.
Just one question.
Where is the FCC positioned in this cluster-fuck.
I just bought an Asus router (RT-N12). Does anyone know if it is exploitable? I'd heard Asus was one of the better ones. I've heard that Tomato runs on this model. Should I switch my firmware to Tomato, or is it sufficient to upgrade to the latest firmware from Asus?
If I can be modded down for being a troll, can I be modded up for being an orc, or a balrog?
Only to prevent transmitting outside of the appropriate bands.
That's all the FCC cares about, and they want protections put in place to prevent a user from using say, channel 14 in North America.
Now, until now, most manufacturers simply used location specific firmware to lock down the transmit channels, but the next generation set will probably incorporate protections stored elsewhere - either an EEPROM, or maybe even fuses blown on the radios itself that say what channels are allowed. Which means it doesn't matter what software says - the hardware (or radio firmware, which is unmoddable) locks out the request to change to an invalid channel.
Anyhow, it's really a case more of manufacturers not taking responsibility for their product - no more "sorry, your product is unsupported" come time for a manufacturer-introduced vulnerability.
Just flash these routers with DD-WRT. I found an old router that I got for free some time ago from SamKnows (an European company doing broadband performance measurement). When the campaign was finished, the thing was just lying in a cupboard. Got it revived with DD-WRT and it works fine now. Great stuff!
8 of 13 people found this answer helpful. Did you?
"The complaint was raised after well-meaning hackers exploited a weakness on Asus routers and left note on victims' drives notifying them of the matter."
Do Asus routers have drives? I doubt it.
Your wrong! For Christ sake. GO READ WHAT IS HAPPENING from the people that *know what they are talking about* and work in the industry! The Save Wifi coalition which is made up of developers including those which have designed the wifi chipsets, lawyers with a technical and legal comprehension of the FCC rules, and key representatives from major router manufacturers. The group has repeatedly stated that the result of the FCC rules regardless of the claimed intent is going to result in manufacturers locking devices down. Manufacturers are already locking down devices as a direct result of these rules.
1. Here is a summary that never made it to Slashdot:
http://slashdot.org/submission/5574003/tp-link-confirms-wifi-freedom-is-dead--all-routers-to-be-locked-down%26gpsrc%3Dgplp0&btmpl=popup#identifier
2. Here is confirmation from one rep from TP-Link that they will be locking down *all* new routers as a direct result of the new rules (and they aren't the only ones, Buffalo, Netgear, Rosewill, and others have stated this or it can be seen that they are doing it):
http://ml.ninux.org/pipermail/battlemesh/2016-February/004379.html
3. You can read the older comprehensive post about the issue from a key Save Wifi participant here:
http://prpl.works/2015/09/21/yes-the-fcc-might-ban-your-operating-system/
4. You can read the newer post here:
http://wwahammy.com/seriously-the-fcc-might-still-ban-your-operating-system/
5. You can contribute funds to fight this here:
https://www.gofundme.com/save_wifi_round_2
(original round of funding was https://www.gofundme.com/savewifi)
APK Hosts File Engine 9.0++ SR-4 32/64-bit http://www.start64.com/index.p...
Gets data for blocking ads, trackers + known bad sites via 10 reputable security community sites.
* Accept NO substitutes!
(Better resources in power/cpu/ram + other IO than locally setup DNS servers AND certainly less problems in security than routers have been showing for years now too...)
APK
P.S.=> Does more for speed (hardcoded favorites + adblocking), security (adblocking + blocking known bad sites/servers & dns issues avoiding DNS), reliability (vs. downed or dns poisoned dns), & anonymity (avoids dns request logs) vs. ANY other SINGLE "so-called -solution'" out there, bar-none, for less using what you already natively have - unlike "AlmostALLAdsBlocked", UBlock, Ghostery etc. it's also not detectable & blockable by ClarityRay/BlockIQ + it uses FAR LESS RESOURCES yet does far more (especially vs. DNS security issues)
... apk
fix your stuff but not too much
It's simpler to lock the entire router than to lock only the radio firmware, and ensure that the unlocked part of the firmware talks only to the approved radio firmware.
Guess which route the manufacturers will take. Don't think twice.
The good part is this is a proposed rule-making, and the FCC doesn't actually want to mess up Vint Cerf and Dave Taht. IMHO it was a bug in their spec (;-))
The bad part is that several vendors think that locking down the entire router is a good and cheap idea, and that no-one like the FTC will object.
The good part is that the FTC does exist, after all, and there is now a growing community of people with locked-down routers that contain a compliance-critical bug, on that takes the router right out of compliance (the glibc dns bug, if it's as bad as we fear).
Those vendors will now need to fix every locked-down device they've shipped with the bug, for free, or look forward to both a class-action suit and petitions to the FTC to ban them from the US.
--dave (Lawyers planning a suit, please post here, especially Canadian ones) c-b
davecb@spamcop.net
Fusable links would be excellent, but the usual hack is to lock down everything in software, which IMHO is suicidally shortsighted.
davecb@spamcop.net
IMHO, those vendors will get FTC bans and class-actions suits. Please! Starting tomorrow, by preference (;-))
davecb@spamcop.net
Can I install it on my router?
APK Hosts File Engine 9.0++ SR-4 32/64-bit http://www.start64.com/index.p...
Gets data for blocking ads, trackers + known bad sites via 10 reputable security community sites.
* Better on power/cpu/ram+ other IO resource use vs. local DNS servers & certainly less security issues vs. DNS servers + routers - Blocks all ads + known bad sites, all the time (not like "AlmostALLAdsBlocked" bribed by google to let ads through)
APK
P.S.=> Does more for speed (hardcoded favorites + adblocking), security (adblocking + blocking known bad sites/servers & dns issues avoiding DNS), reliability (vs. downed or dns poisoned dns), & anonymity (avoids dns request logs) vs. ANY other SINGLE "so-called -solution'" out there, bar-none using what you already natively have. Unlike Adblock\UBlock\Ghostery it's also not detectable & blockable by ClarityRay/BlockIQ + it uses FAR LESS RESOURCES yet does far more (especially vs. DNS security issues)
... apk
See subject & I provided for Ash-Fox prove of it here http://slashdot.org/comments.p...
(See Routers alone = shit (here's proof #1-15/15) titled posts there - & THAT IS ONLY A FRACTION OF WHAT WENT ON & STILL IS GOING ON TO THIS VERY DAY for using them for 'security' alone!)
* It appears nothing can fix it.
(NO, not even my program's data. The problem's largely in their configuration OR software in the course of my reading those articles over time I bookmarked...)
APK
P.S.=> Wish I could help, but I can't on that much - however, I DO HELP by providing my program to help others on that front of security (& speed, + reliability too)... apk