12 ms·
The FCC Might Ban Specific Operating Systems
- jjtheblunt 11y agoConjunctive mode verb ("might") in the title -> bullshit.
- gress 11y agoDid you read the article or are you just deciding it's bullshit because of the title?
- walshemj 11y agoQuite true under the current rules you can get done for exceeding the regs ie mod your equipment to emit more than the permitted maximums. I have a 200mw wifi card that with a the right antenna would massively exceed the permitted power.
- monochromatic 11y ago1. Subjunctive, not conjunctive. 2. Mood, not mode. 3. This isn't subjunctive anyway. 4. But it wouldn't make the article bullshit even if it were. (But funny enough, "were" is subjunctive.)
- deleted 11y ago[deleted]
- deleted 11y ago[deleted]
- jordigh 11y agoWhat I don't get it is, why make the software enforce certain frequencies? If the hardware should never be able to broadcast on a certain frequency, why not build the hardware with that limitation?
- gress 11y agoPerhaps because that's more costly? Sometimes the disallowed frequencies exist within a range of allowed frequencies. A hardware limitation would involve filter stages that would add cost.
- lexicalscope 11y agoThis is already done in scanners to prevent scanning cellular frequencies as required by FCC regs.
- CamperBob2 11y agoYou can't. RF hardware and signal processing don't work that way... at least not for free.
- lexicalscope 11y agoYou can make it difficult and very hard in practice through antenna and component design in the case of small internal radios - in radios with external antennas it becomes a great deal harder though, and in radios that are open for modifications it becomes even more difficult. That being said though - this is meant to apply to software defined/modular radios - that is systems wherein the entire point is that it does what the software tells it instead of having hardwired components meant only to receive certain frequencies.
- rcthompson 11y agoIn addition to the other answers, allowed frequencies differ in different countries/jurisdictions, so it's probably cheapest to make a single piece of hardware that can handle all frequencies in all jurisdictions, and then impose region-specific restrictions in software.
- lexicalscope 11y agoThis is because this is entirely intended for software defined radio and modular radio - around which the entire point is the RF component does not contain as much signal processing logic, and that is done in software. Restricting software defined radios to specific frequencies in hardware would take away the entire point of modular/software defined radio.
- lexicalscope 11y agoThis title is kind of click-bait - they aren't prohibiting operating systems, they _might_ be prohibiting installation of operating systems that are not approved on certain types of devices that allow software defined radio - that is, transceivers that can be tweaked easily by software. That is not at all the same thing as banning an operating system. This is already present insofar as hardware requirements in radios - radios cannot be permitted to listen on frequencies reserved for cell phones, and must not be restricted in such way as they can be easily modified to enable it (e.g., a header/jumper). This really just extends this requirement that it is non-trivial to enable illegal broadcasting or reception on software defined radios. Now - insofar as if this should impact open source operating systems, we have a good question. I don't think it does that - my interpretation, potentially wrong of course, just as the article's could be wrong, is that you would have to restrict the actual firmware in question to a blob that communicates with the hardware in a secure way. This would prevent open/free components insofar as the actual driver, but would not permit the operating system itself from being installed. They mention this, but only at the end of the article. I also doubt the impact of this for non software-defined/modular radio systems. I don't see a way this would really impact everyday wifi or non-modular systems in a way most people would care about. That isn't to say it isn't _bad_ but once again, it just seems super misleading and alarmist. Whether or not the FCC should or shouldn't do this is a different question, but the link's title seems intentionally misleading.
- archimedespi 11y ago> This is already present insofar as hardware requirements in radios - radios cannot be permitted to listen on frequencies reserved for cell phones, and must not be restricted in such way as they can be easily modified to enable it (e.g., a header/jumper). This really just extends this requirement that it is non-trivial to enable illegal broadcasting or reception on software defined radios. Cough, cough, HackRF(https://greatscottgadgets.com/hackrf/ https://greatscottgadgets.com/hackrf/) + GNURadio(http://gnuradio.org/ http://gnuradio.org/) don't seem to have these limitations.
- lexicalscope 11y agoAs I recall, they got around this by not being FCC licensed - in other words, HackRF is classified as a kit/developer component, and is not legal to operate unless you hold an independent license from FCC (e.g.: if you're a Ham you can use it on Ham frequencies you are licensed for). Read the disclaimer at bottom > HackRF One is test equipment for RF systems. It has not been tested for compliance with regulations governing transmission of radio signals. You are responsible for using your HackRF One legally. Realistically you're not going to probably get in trouble, but I _will_ caution you - if you use this kind of equipment illegally, the FCC does have radio direction finding equipment and will send someone out to find you if you piss them off - they've done this for people that were on Ham frequencies without authorization, people doing nasty things on government frequencies, and anything disturbing people who paid for a license. Re: GNURadio The software itself has no requirement - there is no "if you run radio software, it has to do X" and there still is no requirement under proposed rules for that as far as I can tell - it's just if you build hardware, your hardware must enforce that only certain software can be installed :).
- aidenn0 11y agoNote that the FCC still hasn't stopped manufacturers from using RP-SMA connectors on their routers, despite ruling that they are "commonly available" in 2000.
- dublinben 11y agoCan you elaborate on why the FCC would ban a commonly used antenna connector?
- jauer 11y agoAdding higher gain antennas without decreasing transmit power is a common way for people to exceed authorized transmit power. The regulatory theory was that by using a "uncommon" connector only people who know to decrease transmit power (the "professional installer") would be changing antennas: https://apps.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm?id=29031&switch=P https://apps.fcc.gov/oetcf/kdb/forms/FTSSearchResultPage.cfm...
- aidenn0 11y agoThey actually ban all commonly used antenna connectors, to prevent you from exceeding ERP limits on WiFi. The RP-SMA was introduced because it was not commonly used. Since then a large market has formed for RP-SMA antennas, so it should no-longer be allowed, however the FCC has indefinitely stayed requirements for not using them.
- Vexs 11y agoI thought to myself: "This looks like a good time to stock up on SDR equipment, in case this ever goes through." And then I realized this is exactly the same thing gun enthusiasts thought when they though Obama would limit their guns/bullets, and stocked up on them, and I thought it was silly. I guess we're a lot more similar than I would have thought, made me think a little bit more about it. I'm reminded a bit of that "first they came for me" poem/story.
- aylons 11y agoSpecifically, SDR kits are usually rated as professional and test equipment, which are not certified by the FCC. The OP is about consumer products and other FCC-certified products.
- fnordfnordfnord 11y ago>SDR kits are usually rated as professional and test equipment The cheap ones aren't even that. They're repurposed/upcycled television DTV receivers.
- kuschku 11y agoOften by people manually modifying ones they bought themselves. And, interestingly, many satellite receivers allow users to just enter a frequency in the supported range and they will happily load and display the data on that frequency.
- csirac2 11y agoFWIW I haven't seen anything in the new rules (admittedly I have focused on SDR and U-NII regs) which pretends to cover anything but intentional radiators (i.e. transmitters).
- csirac2 11y agoI think they're not rated as anything. They simply have no manufacturer-supplied licensing/approvals whatsoever. So it is up to the user to gain an appropriate license and operate them to the conditions stipulated by that license.
- powera 11y agoHow is this not equivalent to a theoretical "The ATF Might Ban Specific [Gun] Operating Systems"? The ban isn't on the OS, the ban is on the gun (or in this case, high-powered radio).
- anigbrowl 11y agoA driver is not an OS, notwithstanding the legitimate and well-founded objections to driver signing as it affects open source operating systems...but I'm willing to firgive a little hyperbole in the pursuit of attention. On the other hand: I firmly and respectfully disagree. The user always knows their life better than anyone else. Linux exists because users could modify their device. OpenWrt exists because users could modify their device. CyanogenMod exists because users could modify their device. Ultimately, a software community which believe users are fundamentally unqualified is a broken community. I trust users to take responsibility for their own lives. Sure, philosophically I feel the same way. But as soon as I begin broadcasting, I'm not just living my life any more, I'm affecting yours, too. Probably not by much, but possibly by a lot - what if my actions impact your ability to live your life? Externalities are an economic fact. The article itself discusses ways that ignorant or indifferent radio users could cause trouble for others. Pre-emptive regulation of the sort the FCC engages in is annoying, but what other mechanism is proposed to prevent spectrum abuse? We saw from the Marriott Hotel case that where economic incentives exist, some actors will opt to defect and collect an economic rent.
- pdonis 11y ago> as soon as I begin broadcasting, I'm not just living my life any more, I'm affecting yours, too Do you have a wifi router? If so, you are already broadcasting. Have your neighbors complained that they can't use their wifi because of your broadcasting? The huge missing piece in this whole discussion, to me, is: how much of a problem actually exists? How many people actually have problems using wifi because someone else is violating the FCC rules? My sense is that the number is very small. > Pre-emptive regulation of the sort the FCC engages in is annoying I think it's much worse than annoying. Perhaps you don't do any hacking on any device that has a wifi radio; if so, it might only be annoying to you. But if even a small number of people who want to innovate (and won't be doing anything that would break the rules anyway) are prevented from doing so because of pre-emptive regulation, that is a big price to pay. Particularly if, as I suggested above, the magnitude of the actual problem is small. > what other mechanism is proposed to prevent spectrum abuse? The article suggests two: social norms, and aggressive enforcement against actual offenders--as in the Marriott case.
- aianus 11y agoThis is like banning guns cause people sometimes use them illegally to kill other people. Not very American. Just go after people who are causing illegal interference and leave the people who 'might be able to' alone.
- feld 11y agoYeah, there is a gun problem in this country and this is a terribly flawed analogy.
- aianus 11y agoA random American has a 1/10,000 chance of dying to a gun this year. Half of them are suicides. Hardly a 'gun problem' worthy of banning guns. I have a higher chance of crashing my motorcycle and dying that way, do you support banning motorcycles too?
- eponeponepon 11y ago...and what're the odds globally of a random person dying from a gunshot? I could ask about specific other nations with different firearms laws, but let's start with the general case.
- aianus 11y agoI'm from Canada and it's not illegal or particularly difficult to own firearms yet our rate of gun violence is about 7x less than the US. Sounds like there is a separate, bigger problem in the US besides the legality of firearms and plenty of progress can be made without going nuts and banning firearm ownership (or open-source radio firmware) outright.
- scrollaway 11y agoIf you're going to lecture someone on numbers, at least get your arguments right. 1. You should separately account for "random Americans" and americans that actually own guns. I, too, would have a higher chance of crashing my motorcycle... if only I owned a one. 2. Vehicular transportation is a worldwide leading cause of death. It is a problem that is defining the beginning of the 21st century, what with self-driving autos and all. You're setting a pattern in bad analogies. 3. Do you enjoy having that extra 1 in 10k? Do you realize it's really not that high? By your already-biased numbers, there's a 3% chance that someone in your non-gun-owning household of 5 will die with more holes in their body than they were born with.
- shmerl 11y agoNasty. The last thing we need is FCC mandating DRM by law.
- matheweis 11y agoI was slightly surprised about a week ago when I came across the NPRM by accident and realized the comment period was already over. But, I'm more taken aback though by the reactions here to this guy's (admittedly alarmist) thoughts... From reading the comments here, it sounds like only a couple people scanned past the headlines. TL/DR, Eric (Who is actively involved in the OpenWrt project), makes a very good case that the FCCs proposed rules will require DRM for software on all devices with radios, thus preventing the use of third party OS like OpenWRT (although he thinks the rules could probably be applied to computers, phones, etc. too). Sure, the FCC won't "ban" OpenWrt et al, but lets not be pedantic here; if there are no devices left that allow you to legally (or otherwise) install your own firmware, projects like that will die a death by a thousand cuts.
- lexicalscope 11y agoI actually completely agree with you on this - what they're proposing is going to stifle a lot of wireless hacking and will be overall harmful to try to avoid what is probably already at best a marginal problem. Most people that overpower their equipment already burn it out very quickly, and I don't think I'd worry about it as much as they are. I think the alarmist point of view on this actually hurts his points though - because it comes off as a less legitimate concern than I think it actually is. It is something we should be concerned with, because FCC rules are often hard to change once they're made.
- McGlockenshire 11y ago> if there are no devices left that allow you to legally (or otherwise) install your own firmware, projects like that will die a death by a thousand cuts. There are still major manufacturers that recognize the enthusiast and tinkerer market, and they'd be missing out if they didn't sell hardware that has a radio separated from the SoC in order to comply with the proposed regulations. Unfortunately I can count these manufacturers with only one hand. Buffalo is one of them. Hell, they even sell their hardware with DD-WRT already installed.
- csirac2 11y agoThe FCC responded to Ars saying that the line about DD-WRT was clumsily worded. I'm under the impression that if the OEM/importer demonstrates in their filing that their proof of conformance documentation will always be representative (valid) of the device no matter what the user can do through user-accessible features and menus, i.e. they can prove that the radio module is locked down in some way other than the main device firmware, this should be sufficient and does in fact meet the requirements. After all, preventing APs from stomping on licensed spectrum due to wrong country selection seems to be half of what's driving all this anyway.
- mschuster91 11y agoNitpick: a 1kW amp wouldn't be sufficient only on the AP side in order to expand your WiFi range. You'd need a damn good RX amplifier with damn good antennas or have a 1kW TX amp on the other station, too, in order to get wide-range communication.
- fencepost 11y agoMy contribution to the commentary: I feel that the proposal to regulate device firmware and effectively ban non-vendor firmware is both overbroad and will result in significantly increased security risks faced by the general public (myself included). If the FCC chooses to go forward with this, it should also require and put in place penalties to enforce MANDATORY security updates from vendors within tightly constrained timelines, including to products which the vendors no longer sell or wish to support. I have used various third-party firmware replacements (generally OpenWRT, occasionally DD-WRT) to replace firmware on routers with known security holes, undoubtedly including some for which patches were years late if ever delivered. I have done this for myself, friends, family and customers. If the FCC mandates that I may not legally replace the firmware with secure versions unless they come from the equipment vendors without also taking steps to ensure the availability of those security fixes, then the FCC is acting to ensure that the state of network security in the United States is AND WILL REMAIN unacceptably poor.
- csirac2 11y agoThey are struggling with a very simple problem. If you configure your 5GHz U-NII device to the wrong country, and turn it on, it will stomp all over licensed/restricted spectrum. That's because unlike 2.4GHz, 5GHz has been carved up very differently in different parts of the world (each place has had its own evolution of technology and spectrum pressures). To such a degree that this isn't even about power and frequency. As an FCC registrant seeking to slap FCC stickers on your new/imported devices, you'll be required to submit proof of conformance documentation which demonstrates you've properly implemented radar avoidance in your frequency hopping/spread spectrum algorithms. Finally, the FCC has made it obvious that this aimed at the transmitter module, not the overall device. And so, "banning" OpenWRT and other 3rd-party/alt firmwares would only be required if that's the only half-arsed way a manufacturer can hope to comply with the new regs. In future, I'd hope hardware becoming better isolated from radio components, this ruling (and similar around the world) are essentially mandating region-locked devices, so we might see something similar to what's happening in mobile phones (Eg. baseband radio firmware separately versioned/updated from OS firmware).
- dbbolton 11y agoApologies for the off-topic comment, but I feel compelled to say that a #6D6D6D anchor color with a #444444 body text color on a white background is a terrible UX choice. I guess they expect me to hover over the entire paragraph to see if it contains any links.
- ijktdot 11y agoIn 5 years we'll all just be using a SoC as the entire computer, so likely there will be no free operating systems considering they'll also make it illegal to tamper with any approved operating system bootloaders/firmware so can't replace anything on it.
- deleted 11y ago[deleted]
- deleted 11y ago[deleted]
- aqwwe 11y agoDo they do this because they don't have the resources to enforce the law?
- godgod 11y agoHow not draconian of the FCC. /sarc. I feel like Freedom is being banned everywhere by every western government.
- sandworm101 11y agoGo ahead and ban new OSes on radio hardware. These are radios. Anyone can build them (see the ubertooth). My startup will be called "locked down radios" and our products will come with a very serious EULA instructing you to never ever ever cut that one little wire blocking you from flashing on new software. (serious business to do now. The new Muppets show is on.)