By Jonathan Corbet
October 14, 2015
There has been a lot of concern recently that
a new
set of rules [PDF] from the
US Federal Communications Commission (FCC) could lead to locking-down of
home router devices. It appears that the worst-case scenario feared by
many will not come to pass, but that has not stopped a large, high-profile
group of developers from putting together
a detailed counter-proposal
to the FCC that could change the game entirely. Not content with fending
off the lockdown threat, this group seeks to push the pendulum the other
way by forcing router software to be open. The result, it is said, would be an
Internet that performs better and which is much more secure.
Lockdown worries
The FCC's concern in this area relates to spectrum use, of course. WiFi
routers are radio transmitters, so they must abide by the rules on how
they can transmit; these include limits on allowable frequencies, maximum
power, and
more. To gain the required FCC certification, a vendor must
demonstrate that a router cannot be operated in ways that violate those
rules. Regulatory compliance was used as an excuse for years by WiFi
chipset manufacturers that did not want to release drivers or hardware
documentation. That excuse has broken down over the years, but, for a
while recently, it seemed that the FCC was contemplating a required
lockdown of router firmware as a way of ensuring compliance. By some
readings of the proposed rules, the installation of distributions like
OpenWrt on home routers would no longer
be allowed.
Blocking third-party firmware installation would be a clear step backward
for a number of reasons. Routers as shipped by vendors are often insecure
from the outset and, given that almost none of them ever receive software
updates, they all become more insecure over time. Independent router
distributions, instead, can be updated to fix security problems; they can
also enable all kinds of functionality that was not envisioned
or enabled by the original vendor. And free-software distributions, in
particular, have been the platform on which a great deal of networking
development has been done. Improvements in IPv6 functionality, bufferbloat
reduction, and more have been implemented by the free-software community on
open routers.
In an attempt to head off a router lockdown, a group of influential
developers has filed a
letter to the FCC [PDF] calling for the proposed rules to not be
implemented. Since the filing of the letter, the FCC has stated
that it does not intend to block third-party firmware installation. But
the letter goes far beyond simply asking the FCC not to lock down routers;
indeed, the FCC has been asked to open them up radically.
New mandates requested
The letter asks the FCC to change its certification requirements for WiFi
routers and add a new set of mandates. The first of those is that the
source code for the router's "device driver and radio
firmware" must be made freely available in a
"buildable" form so that this code could be reviewed by
outsiders. There is no mention of requiring that this code be made
available under a free license, though the rest of the document makes it
clear that this is what the authors would prefer. It also does not require
that users be able to install modified versions of the software; this was,
your editor has been informed, an oversight during the drafting process.
Requiring the release of this code would clearly change the situation for
router developers and users. It would bring about an end to binary-blob
WiFi drivers, which would be a welcome change indeed. Even if a given
driver were to be made available under an incompatible license, clean-room
techniques could be used by others to develop a free driver. Opening up
the radio
software would shine a light into a dark corner of these systems, teaching
us a lot about how they work, even if the software could not be replaced.
A crucial piece of consumer-level infrastructure would become more open.
The advantages of this openness would be many, starting with the ability to
audit the software for security issues and to fix them when they are
found. Given the record of vendors in this area, improving the community's
ability to provide security support can only be a good thing. The letter,
though, asks the FCC to go further and to require the provision of security
updates. In particular, any vulnerability with a CVE number that affects a
router must be fixed by an update within 45 days of disclosure during the
warranted lifetime of the router.
Finally, the FCC is asked to make it clear that lockdown of router devices
is not required by its regulations:
Additionally, we ask the FCC to review and rescind any rules for
anything that conflict with open source best practices, produce
unmaintainable hardware, or cause vendors to believe they must only
ship undocumented “binary blobs” of compiled code or use lockdown
mechanisms that forbid user patching.
The letter appears over a large number of well-known names, including Dave
Täht and Vint Cerf (the principal authors) along with Jim Gettys, David
P. Reed, Bruce Schneier, Daniel Geer, Kathleen Nichols, David Farber,
Steven Bellovin, Linus Torvalds, Paul Vixie, and many more, including an
obscure LWN editor. As a whole, it
makes an impassioned case for free-software development as the best path
toward high-quality and secure networking software.
Toward a better Internet
As a defense against further lockdown-oriented rules, it is likely to be
effective, especially since the FCC is claiming that it does not intend to
impose such rules. The mandates may find a more difficult reception,
though. There seems to be no doubt that there would be fierce resistance
from vendors and manufacturers; overcoming such resistance could be hard in
the absence of wider public understanding of the nature of the problem.
To some, an open-routers mandate might actually look like a step backward
for security, and for the security of the wireless spectrum in particular.
But most users have no desire to run their routers out of compliance; there
does not appear to be anything resembling a widespread interference problem
caused by modified devices. On the other hand, routers with security
vulnerabilities and even deliberate back doors are widespread indeed.
Rules that address the latter problem will do far more to ensure that our
routers behave themselves than anything aimed at locking down access to the
radio hardware.
It would be surprising if this letter to the FCC were to convince them of
that point on its own. But one has to start somewhere, and this is a
strong start with a lot of big names behind it. With luck, it may just
push us toward a world where our networks work better, our hardware is more
secure, and routers serve the interests of their owners. That seems like
an outcome worth going for.
(
Log in to post comments)