A Solution To the Security Guidelines Proposed By FCC For Home Routers (imgtec.com)
An anonymous reader writes: Back in March 2015, the United States Federal Communications Commission (FCC) issued a security document that included a series of provisions related to the use of wireless devices. In order to comply with these security guidelines, some manufacturers of home routers and other networking equipment decided to lock down the software powering these devices. This caused an outcry from the open source community who demanded that the FCC and manufacturers would not restrict the free use of the operating system and associated software running on their devices. Now Imagination Technologies is presenting a proof of concept demonstration that addresses the next-generation security requirements mandated by the FCC and other similar agencies. The demo makes use of a feature of MIPS Warrior CPUs called multi-domain, secure hardware virtualization. This technology allows developers to create system-wide, hardware-enforced trusted environments that are much secure compared to current solutions. The platform used for the demonstration runs three virtual machines (VMs) on a MIPS P-class CPU integrated in a router-type evaluation kit; this approach securely separates the OpenWrt operating system from the Wi-Fi driver, allowing them to co-exist in isolation and thus comply with the FCC guidelines.Ars Technica has more details.
As I see it, this non-solution is incompatible with open source. How about just simply shipping them with an OS that complies with the FCC rules and let it be the user's responsibility not to put software on it that doesn't comply with the FCC rules?
Take a leaf out the CB / Ham radio guidebook.
Manufacture the boards with a wire link on them that disables whatever feature it is you're not permitted to have, along with a note saying "hey guys, please don't cut this wire link, we need it to legally sell this equipment in this jurisdiction. Seriously now promise you wont cut it, it's the black one marked J2 next to the LCD driver IC"
+1!!!
Really poor editorial choice on Slashdot's part for posting this without commenting on this highly apparent contradiction.
This technology allows developers to create system-wide, hardware-enforced trusted environments that are much secure compared to current solutions.
The communication between the VM running the Slashdot-posting subsystem and the VM running the grammar-checking subsystem malfunctioned. Again.
.
"...system-wide, hardware-enforced trusted environments..."
Sounds expensive already...
"This technology allows developers to create system-wide, hardware-enforced trusted environments that are much secure compared to current solutions."
Your technology may be secure, but it's not *much secure*.
Really? I thought reporting news was supposed to be unbiased.
The problem was never that it couldn't be done. The problem is that its simpler to not do it. This 'solution' doesn't change that.
HAHA. Yeah, freedom, hows that going for you. The state says as such, and you will obey
since the summary explicitly mentions that one of the VMs is running OpenWRT, I'm unsure quite how you mean this. Can you explain?
Such doge.
The FCC rules mandate that the end user isn't able to, in any practical manner, use Wi-Fi channels that aren't part of the unlicensed spectrum in the US. This whole thing came about precisely because people running open source software on their routers were using channels that are only legal in Europe and Japan, thus causing interference with other equipment that's licensed to use that spectrum in the US.
Essentially, they just need a way to make it so that radios shipped in the US aren't capable of hitting licensed spectrum, but that's not practical from an economies of scale perspective (I.e manufacturers save on cost by making the same chips for all markets, and then using software to disable different channels on a regional basis.)
In principle, I like the idea of making the radio subsystem be virtualized, and just have a software interface that controls the radio. This could actually improve open source compatibility because you don't even need to worry about i.e closed source broadcom drivers. Kind of like how running Linux or BSD in a virtual machine means you don't have to worry about whether or not your physical hardware is compatible with your chosen OS.
Rather than shipping with a radio which can broadcast on any frequency, you make an american model with a radio that broadcasts on the American frequencies and cannot be tuned outside that range in software?
... really needs no encouragement through hardware support. Just retract that turd already, FCC.
The open source community clearly needs to lobby the FCC harder. Of course, this is bad, but not doing it is worse. Try and see if, like the EU, the US gov't would be willing to subsidise "grass roots" movements that lobby itself.
Being unbiased doesn't mean just blindly repeating press releases, in fact, that's one of the most common sources of bias in reporting. To be unbiased you have to be critical as well.
It seems a huge part of what the FCC doesn't like are people setting their radios to other regulatory areas and using the nice "clean" spectrum allocated for commercial/government use. None of their proposed solutions really solve the problem, as motivated individuals can just pick up a device next time they are out of the country and put it in their apartment building anyway. Given how low power wifi is already, its likely they would never catch you.
But all this is just BS, because running an out of spec wifi AP doesn't really solve anything. Its not like anyone is going to go to the trouble of modifying all their devices to talk to an AP using a licensed band, or can communicate back to a wifi device attached to an amplifier.
The FCC/congress though is the real problem. Their corprate first attitude, has basically sold/given all the spectrum to organizations which hate the idea of individuals not having to be locked into paying monthly extortion..
Just imagine what the US would be like if instead of selling the spectrum used for just one of the recent spectrum auctions (take wimax for starters) they had instead allowed unlicensed use... The explosion of technologies in the extremely limited ISM bands suggests at just how useful this spectrum could be, instead of sitting around mostly unused.
Maybe we should just stop looking for solutions and legislation to fix things that aren't a problem?
I mean it's not like the FCC is very good in enforcing the rules they have.
Does this address the problem of FCC licensed amateur operators that can legally operate on adjacent frequencies and higher power levels?
Competition Good, Monopoly Bad.
... was to lock down the radio while still allowing user-updates to the firmware? I seem to recall a recent slashdot article (don't have a link handy sorry) that announced that this is exactly what Linksys was choosing to do.
File under 'M' for 'Manic ranting'
the easier solution would be for the regulatory transmit power limits to be baked into the *radio* itself, leave the router software completely alone. the drives NEED to be able to be updated along with the rest of the firmware, and without hoop jumping. if you lock parts of the firmware, who's to say there isn't something else in that inaccessible area besides "just" the radio driver.
So one of the VMs can nicely include the NSA backdoor? How convenient.
HAHAHAHAH
That's NOT a solution. I want to LOWER my power output. If they (FCC) take away that ability, I will be really pissed off!
Get your grubby hands off my router!
Then move to a remote island. In the civilized world, you do not own the public airwaves and your rights do not allow you to cause interference for others.
Having a WiFi driver that the developer is locked out of repairing is no kind of solution. Having a WiFi driver that can't handle new features developed after the user gets the product is no solution either. And locking hams, who can legally use different frequencies and more power, out of the system is no solution either.
Bruce Perens.
Consumers are free to build their own unregulated routers. I can see while the specialized open router markets should be concerned, but I suspect it will not really be hard to find 'unlocked' routers.
There is a real problem with the security of millions of routers. Those a fairly key devices in the average persons home AND they are pretty powerful if used in a cyberattack.The security for these devices is horrible and code auditing should really be the focus, not firmware lockdowns.
Stop buying routers. Instead get a Raspi and USB wifi adapter capable of master mode. Put together a preconfigured "router" distro for it that can simply be loaded onto an SD card and configured via a web interface like a normal router.
This whole thing came about precisely because people running open source software on their routers were using channels that are only legal in Europe and Japan, thus causing interference with other equipment that's licensed to use that spectrum in the US.
The report originally cited by the FCC doesn't say anything about open source firmware. As far as we can tell, the interference was caused by devices running proprietary software that either was buggy or had been modified to not comply with the local regulation. If you know otherwise, please share your sources.
We tried that. Too many open source users can't be arsed to comply with the FCC rules, or expose every option possible and damn the rules (not their responsibility, as you suggest), so that now open source as a whole will pay the price.
Now you've lost open source access to Wi-Fi radios. Police your community or you can bet that software defined radios will go the same way.
The router is running a closed source unchangeable OS, that is running some VM's on it. A true open source solution would have all the software running on the router chosen by the owner, not just a subset.
nobody except government loons want to hack your wifi any more. there are billions of pornos already. what would you be snooping a wifi for? world of warcraft passwords?
silly fantasy concerns. the true concern is the Google/YouTube-Facebook-Twitter-Microsoft-CIA surveillance. the entirety of Windows and Microsoft devices are spyware. android and chrome are google. spyware. google tracks everywhere you surf with many different servers like google-analytics and gstatic. facebook.net and twitter too. pinky and the brain fantasies.
Cheapo Mini-itx system that has on-board ethernet with a wireless card adaptor. That's what I have at my house.
FTFY.
Check out my sci-fi/humor trilogy at PatriotsBooks.
100 years ago: "MMAALLEESS: Police your community or we won't let you marry young girls any longer"
50 years ago: "MMAALLEESS: Police your community or we won't let you have automatic weapons any longer"
etc.
How about we overthrow the state and do as we will, or die trying.
It's from the same company that publishes a tiny crap of a shim for closed GPU drivers and calls it "open source GPU driver".
Take no stock in them.
Or ... just STOP USING SHITTY SOFTWARE DEFINED RADIOS THAT CAN BE MODIFIED AT RUNTIME.
There is absolutely no need for that. Make your chips not suck, get the god damn firmware right the first fucking time, embedded it in ROM and leave it the fuck alone. Don't allow changes to functions/parameters that allow non-legal settings.
THE REST OF THE SYSTEM THEN CAN'T DO ANYTHING THE FCC PREVENTS EVEN IF IT IS RUNNING OSS SOFTWARE.
This isn't difficult in the least, its that no one cares about the handful of people using an OSS version of the software. The mind blowing part is that you guys think there are enough of you that the manufactures give a shit about your silly little side projects :)
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
Ah, gotcha. I had interpreted it as meaning "you can't put any open software on it". Barring hardware-only enforcement of the radio restrictions (unlikely for economic reasons) I don't see a solution that doesn't have some proprietary unchangeable software, but I see your point.
It's bitztream, the angry, yelling, penis-envying, autism-hating Slashdot troll!
OMG why do you use all caps all the time you fucking fucktard!
OMG WHY DO YOU USE ALL CAPS ALL THE TIME YOU FUCKING FUCKTARD!
why do you use all caps all the time you fucking fucktard!
or had been modified to not comply with the local regulation.
And how, pray tell, was it modified? Be specific.