4 ms·
> * Contrary to some of the FUD being posted in this thread, the regulations don't appear to be about custom firmware for the UIs or even signalling on a device
by PhasmaFelis 11y ago
> * Contrary to some of the FUD being posted in this thread, the regulations don't appear to be about custom firmware for the UIs or even signalling on a device*
This is incorrect. Various sites have done a really shitty job at linking directly to the relevant documents, but see this: https://apps.fcc.gov/kdb/GetAttachment.html?id=1UiSJRK869RsyQddPi5hpw%3D%3D&desc=594280%20D02%20U-NII%20Device%20Security%20v01r02&tracking_number=39498 https://apps.fcc.gov/kdb/GetAttachment.html?id=1UiSJRK869Rsy...
Note that vendors are required to "Describe in detail how the device is protected from 'flashing' and the installation of third-party firmware such as DD-WRT."
This is specifically about blocking all use of custom firmware.
- Silhouette 11y agoWhat is the legal status of that document? I was looking at one that 'thejosh linked to: https://www.federalregister.gov/articles/2015/08/06/2015-18402/equipment-authorization-and-electronic-labeling-for-wireless-devices https://www.federalregister.gov/articles/2015/08/06/2015-184... That seems reasonably clear in what it's talking about, or at least what they're intending to cover. For example: "The Commission proposed to require that an applicant for certification explicitly describe the RF device's capabilities for software configuration and upgradeability in the application for certification. This description would include all frequency bands, power levels, modulation types, or other modes of operation for which the device is designed to operate, including modes not enabled in the device as initially marketed. Also, an applicant for certification would have to specify which parties will be authorized to make software changes (e.g., the grantee, wireless service provider, other authorized parties) and the software controls that are provided to prevent unauthorized parties from enabling different modes of operation." There's no reference to specific firmware platforms like DD-WRT or OpenWRT there. Is this a case of some documents describing preliminary consultations and others a final situation that differed from what was contemplated originally? For that matter, is it actually the case that some routers don't fully isolate the radio control software as intended by the regulations, in which case installing custom firmware like DD-WRT or OpenWRT really would be a risk, in which case the intent of the regulations really would be to prohibit the installation of that custom firmware in that particular context because it does present exactly the threat they are trying to control?
- Sanddancer 11y agoYep, that's exactly the problem. We even have a few posters in this discussion talking about how they hate these new requirements because it means they can't run their routers illegally anymore. A lot of the fuss seems to be that the draft documentation of things that hardware vendors should consider and put in their certification request is, "what happens if an end user installs a third-party firmware like dd-wrt." They're seeming to take that as prohibiting all third-party firmwares, instead of prohibiting third-party firmwares on devices that require binary blobs. A router maker who has a baseband that can't be modified wouldn't be affected by this at all.
- PhasmaFelis 11y agoI've already covered a lot of this in my response to Silhouette, so I won't repeat it here, but: > We even have a few posters in this discussion talking about how they hate these new requirements because it means they can't run their routers illegally anymore. Are you under the impression that the sole purpose of custom router firmware is to access restricted channels? Custom firmwares contain many very useful, legitimate tools, and also happen to enable region-shifting for users who want to keep their old router when they move, which unfortunately lets malicious or ignorant users access locally unauthorized channels. As for the rest, the U-NII Device Security document I posted above is pretty clear about prohibiting all unsigned firmware, explicitly including DD-WRT.
- PhasmaFelis 11y ago> What is the legal status of that document? It's on fcc.gov, so it's probably legit. It dates back to March, so it's conceivable that it's been modified or superseded since then; I haven't been able to find anything to indicate so, but I'd be happy to be wrong. Basically, there seems to be a lot of confusion stemming from blogs that heard about the document that I posted, but only linked to the document that thejosh posted. I found this doc via the CNXSoft post that appeared on HN yesterday [1], which mentioned the "protected from flashing" line and linked to Etherpad notes from a presentation, which linked to the U-NII Device Security v01r02 document that I posted above. It's kind of a ridiculous chain, so I can see why people were confused. You're right that none of the documents directly linked in this thread talk about blocking custom firmware; when people are talking about that, they're thinking of the U-NII Device Security document, not the "Equipment Authorization and Electronic Labeling for Wireless Devices" proposed rule. > Is this a case of some documents describing preliminary consultations and others a final situation that differed from what was contemplated originally? Possibly. They may also be describing different aspects of the FCC's evolving wireless policy. I haven't followed the rabbit hole deeply enough to determine for sure whether the FCC is still currently on track to block custom firmware, but it appears that they were as recently as March. > For that matter, is it actually the case that some routers don't fully isolate the radio control software as intended by the regulations, in which case installing custom firmware like DD-WRT or OpenWRT really would be a risk Oh, yes, certainly. Most of these firmwares are designed to be useful for users all over the world; IIRC, the one I use (Tomato) lets you select your region from a pull-down, and then enables the channels appropriate to your claimed region. (You can achieve the same thing by downloading the manufacturer's firmware intended for a different region; custom firmware is not required.) I think this was well-meant on their part, but I agree that it is a problem, and it makes sense for new routers to block access to block access to unauthorized channels on a level that custom firmware can't touch. I just think that blocking custom firmware entirely is throwing the baby out with the bathwater. [1] https://news.ycombinator.com/item?id=10137470 https://news.ycombinator.com/item?id=10137470