Android May Soon Restrict On-Device ADB

	Android May Soon Restrict On-Device ADB(kitsumed.github.io)
	373 points by shscs911 5 hours ago \| 170 comments
	tl;dr: A Google ADB maintainer has proposed restricting Android's ADB daemon to only bind to the wlan0 interface in response to CVE-2026-0073, which would break loopback (on-device) ADB connections used by tools like Shizuku, App Manager, and Termux-based workflows. The author, a Shizuku app developer, argues this would kill a legitimate ecosystem of power-user tools since malicious apps can't start ADBD or authenticate connections on their own, and suggests Google instead offer a persistent user-toggleable setting rather than a permanent block.
	HN Discussion: ↑Attack vector is unrealistic since it requires developer mode and remote ADB, so restriction is unjustified ↑This is part of a broader trend of Android becoming increasingly locked down and user-hostile ↓Physical access threats from authorities and third parties justify some security concerns •Users should switch to Linux phones to escape platform lock-in ↑Sarcastic mockery of security-justification framing used to restrict power-user features