←back to thread

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

(blog.exodusintel.com)
387 points pedro84 | 3 comments | 26 Jul 17 19:51 UTC | HN request time: 0s | 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 #
Scramblejams ◴[27 Jul 17 00:02 UTC] No.14861519[source]▶
One theory I've seen bandied about related to GPU drivers is that it's harder for your competitors to notice you're infringing on their patents if you don't ship your source code.
replies(1): >>14861779 #
tedunangst ◴[27 Jul 17 00:58 UTC] No.14861779[source]▶
This seems unlikely. (Or maybe that's the reason given, but it seems implausible to be true.) Competitors have more than enough know how to determine if you're infringing a patent, source or no source.
replies(3): >>14861968 #>>14862322 #>>14863651 #
freyir ◴[27 Jul 17 01:36 UTC] No.14861968[source]▶
> Competitors have more than enough know how to determine if you're infringing a patent

How do you figure? The detectability of infringement is a key factor in deciding whether to file a patent.

Regardless, copyright infringement might also be an issue.

replies(1): >>14862259 #
1. tedunangst ◴[27 Jul 17 02:36 UTC] No.14862259[source]▶
Well, it's hard to be specific since nobody ever mentions which patents they're talking about. But I would assume that somebody at AMD has the skills to determine whether Nvidia uses the "good matrix" technique, or whatever it is people are assuming AMD patented that Nvidia is trying to hide.
replies(1): >>14862301 #
2. Justin_K ◴[27 Jul 17 02:47 UTC] No.14862301[source]▶
In court, there's a big difference between your assumption vs. published code.
replies(1): >>14862338 #
3. toast0 ◴[27 Jul 17 02:56 UTC] No.14862338[source]▶
Drivers are published code, freely available. If the driver does something, and you can't find an expert witness to testify it does what it does, maybe it doesn't do what you think?

Reading assembly with no comments is a different skill than reading C or C++, especially since it's not always clear what's an instruction and what's data, but it's still reading code, and there are tools to help you trace through it. And most of the drivers aren't writing code like it's a 64k demo (where the code is the data, and the data is the code, and they both modify each other)