Conversation

Replying to
No, I don't, and I specifically brought up that it's pretty bad to be switching away from a modem with substantial auditing, mitigations, sandboxing, research directed at it, a driver which is designed not to trust it and has a lot of attention from researchers for that, etc.
1
Replying to
Look, go ahead and get hardware that's insecure and unfixable from day one. Give up on trying to peddle scams and misinformation to me. You really don't know the subject matter, and it's not interesting to have you try to explain things to me that you don't know about.
1
Replying to
I gave you plenty of information which you ignore and don't look into further, and you then go ahead with continuing to make the same clearly false and refuted claims over and over again. I don't see much point in talking to someone not being honest or acting in good faith.
1
Replying to
So, as before, ignoring most of what I am saying and just cherry-picking bits of it and misrepresenting the topic along with what I have said. I really don't see the point in any of these threads.
2
Replying to and
We currently target devices where Bluetooth, Wi-Fi and cellular is implemented in dedicated sandboxes on a chip that is itself isolated from the OS. They have all the basic mitigations deployed for them and a fair bit of external security research looking into it.
1
Replying to and
Wi-Fi has typically not been included on the smartphone SoC until recently and therefore it was up to OEMs to go out of the way to implement isolation for it and of course they don't actually tend to do that. Most OEMs don't really have hardware security teams doing that stuff.
1
Replying to and
As one example, any phone that has Broadcom Wi-Fi will generally have it connected via PCIe with no attempt to isolate it. Broadcom doesn't appear to care much about privacy/security and doesn't offer Wi-Fi anonymity (MAC rand via OS doesn't provide it) or hardening/sandboxing.
1
Show replies