4 ms·
Shared resources isn't a "hardware bug." It's a design choice. I2C is always vulnerable to one device locking up the bus-- indeed almost all buses are. But i
by mlyle 1y ago
Shared resources isn't a "hardware bug." It's a design choice.
I2C is always vulnerable to one device locking up the bus-- indeed almost all buses are. But it's intended to be a bus hooking up multiple pieces of hardware.
This is an interesting phenomenon-- source account is 100% dubious Apple "bug reports" and then we have another completely new account choosing to misinterpret the dubious report (which isn't really security related despite involving a security component) as a critical vulnerability. The cited reports all ring like they're written by a LLM.
- FluGameAce007 1y agoTrue.. I2C lockups are a known limitation, not a bug. But this isn’t about bus contention. The issue is that debug logic is active on production-fused silicon, despite dev-fused = 0 and debug = 0x0. That’s a hardware trust failure, not a design trade-off. Fuses are supposed to make debug paths unreachable—but they’re not. That’s the problem.
- mlyle 1y agoThere's no secure enclave output here. Stop the bogus reports. If I want to talk to ChatGPT, I'll go to the site or use the API kthx.