3 ms·
> 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 su
by 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
- Silhouette 11y agoIt's on fcc.gov, so it's probably legit. But legit what? For example, I don't see any indication of whether it's an existing policy, a draft/proposal for future policy (which is what most of this discussion seems to be about) or something else. Who is required or recommended to read it? What happens if they don't do what it says? Most significantly, it also doesn't seem to specify what constitutes a U-NII Device for the purposes of these rules. It would be bad if the rules had the effect of blocking custom firmware on something like a wireless router when that device included a self-contained radio component that was a black box and itself constrained to follow the normal rules for transmission equipment. On the other hand, if we're talking about running custom firmware on that radio component and/or on the main device but with the ability to reconfigure the radio component to perform outside the authorised spec, it seems to me that prohibiting the installation of that firmware is exactly what is intended, and for good reasons.