> Disclosure to Apple and relevant security communities has been initiated or is recommended.
“or”? Was any disclosure ever initiated prior to posting this on HN? Which security communities were notified? Is there a timeline of contacts and publications?
adithyassekhar · 3h ago
Man this guy's repositories are wild.
duskwuff · 3h ago
If I'm reading this correctly, the author hasn't actually interacted with any of this "debug logic" (and doesn't even describe what it is), but is inferring that it must be active based on some log messages which mention debugging or which display diagnostic output. None of the log messages implicate a "hardware flaw"; it's not clear that any of them are even abnormal.
The report looks like AI slop. This is a meaningless waste of time.
Zagitta · 2h ago
Calling it slop is generous, it's straight up hallucinations
2OEH8eoCRo0 · 3h ago
Haven't they done this before?
FluGameAce007 · 4h ago
Observed on a production-fused A16 Bionic devices (e.g., iPhone 14 Pro Max),the internal debug pathways activating under stock iOS (debug = 0x0, dev-fused = 0). SecureROM, firmware, and co-processors all exhibit debug behavior without jailbreak, tampering, or provisioning profiles.
This violates Apple’s hardware trust model and exposes internal diagnostics meant for development silicon.
bayindirh · 2h ago
I'll link my favorite computing journal, and cite its title here:
“or”? Was any disclosure ever initiated prior to posting this on HN? Which security communities were notified? Is there a timeline of contacts and publications?
The report looks like AI slop. This is a meaningless waste of time.
This violates Apple’s hardware trust model and exposes internal diagnostics meant for development silicon.
PoC || GTFO [0].
[0]:https://www.alchemistowl.org/pocorgtfo/