Difference between revisions of "Save WiFi"
(initial entry) |
|
(No difference)
| |
Revision as of 08:57, 1 August 2015
The FCC wants to require device makers to lock down wifi-capable devices. This means wifi routers, as well as potentially phones, tablets, laptops, and any nubmer of new devices that are categorized as a System on a Chip (SoC) will be cryptographically locked down with DRM. But instead of using DRM to restrict what movies or music you can stream, this is DRM to control what software you can install on your device. While we have laws that protect hardware and software companies that maek use of DRM, this will be the first law *requiring* the use of DRM by device makers. This is an absurd overreach by the FCC and it must be stopped!
Fortunately, the FCC is accepting public comments on this issue. The deadline for comments is August 16th, so we need to act quickly. Fortunately, thanks to the work of individuals from OpenWRT, ThinkPenguin, LibreCMC, we already have some momentum building around this issue. But we need to come at this problem both singularly and together by growing a coalition that helps spread a more unified message to the FCC as well as encouraging supporters of those organizations and groups to submit comments to the FCC.
Whose with us?
Organization plus point of contact
- OpenWRT has already been helping to lead this effort
- Free Software Foundation, Joshua Gay
- LibreCMC, Bob Call
- OpenWRT
Organizations we want to support this
- EFF
- Demand Progress
- New America Foundation/OTI
- Center for Democracy and Technology
- Berkman Center
- OTI
- Free Press
- Prometheus Radio (and similar?)
- Public Knowledge
Resources
- Amongst other requirements, the proposed rule will require applicants to "Describe in detail how the device is protected from “flashing” and the installation of third party firmware such as DD-WRT". Software Security for UNII Devices.
- Call for comments states:
We propose to modify the SDR-related requirements in Part 2 of our rules based in part on the current Commission practices regarding software configuration control. To minimize the potential for unauthorized modification to the software that controls the RF parameters of the device, we propose that grantees must implement well-defined measures to ensure that certified equipment is not capable of operating with RF-controlling software for which it has not been approved. [ . . . ] We seek comment on these proposals.
