Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'll grant there's an argument for requiring signed code for GSM-capable hardware on consumer devices; we don't want people accidentally turning their device into a jammer.

But:

1. closed-source driver code always has security holes. Having insecure devices is as bad for public policy as jamming.

2. if I really want to jam cell signals I can take the door off my microwave. (kids listening at home -- don't do this). Anyone who's ever flashed an android device will agree that it's easier to hotwire the microwave than build bootable code for the handset.

3. the radio controller runs a sophisticated RTOS that (I assume) can read the phone's RAM and execute wacky RPC. And most cellular networks have experimented in the past with some form of rootkit or spyware. Dear Verizon: I paid for the device. Let me own it.

One answer that compromises between consumer needs & FCC needs is to say signed code has to be open source and verified-build.

I'm guessing there's a lock-in argument for the radio chipset creator. Being the only vendor of software for your hardware means vertical integration, i.e. there are fewer companies expert in any part of your stack.



2. Microwaves are 2.4 GHz, and phones (except their wifi) is nowhere near. This should not work.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: