←back to thread

Remotely Compromising Android and iOS via a bug in Broadcom's WI-FI Chipsets

(blog.exodusintel.com)
387 points pedro84 | 1 comments | 26 Jul 17 19:51 UTC | HN request time: 0.227s | source
Show context
thomastjeffery ◴[26 Jul 17 23:00 UTC] No.14861166[source]▶
Why does Broadcom insist on proprietary drivers?

How could it possibly be detrimental for Broadcom to have free software drivers?

This article is a poignant example that it is detrimental for them to continue to keep their drivers proprietary.

replies(6): >>14861174 #>>14861519 #>>14862058 #>>14863796 #>>14867469 #>>14871284 #
whowouldathunk ◴[26 Jul 17 23:01 UTC] No.14861174[source]▶
The drivers are probably pretty complicated and thus valuable IP.
replies(2): >>14861236 #>>14867384 #
1. azernik ◴[27 Jul 17 17:19 UTC] No.14867384[source]▶
Having worked on enterprise APs using BCM and Atheros chipsets:

The driver is not deeply protected IP. They will hand out full copies to any device manufacturer that uses they're chipset, so that they can integrate it with their systems. The secret sauce, the bit that they won't share with anyone even if it's necessary for debugging, is the on-chip firmware. That's the stuff they take seriously. The driver itself is just a lawyer thing.