|
|
|
|
|
by wolvoleo
3 days ago
|
|
> This feature was proposed following a major security issue identified as CVE-2026-0073, which allowed the Wireless ADB authentication process to be fully bypassed. What is proposed in this issue is actually a nice idea. Clearly this is not an issue when the wireless authentication process works as intended. I see no need to change that at all. They just need to fix that bug. It's quite difficult to do this. You need to enable wireless debugging. Then pair to a random port with a random pairing code and then connect to yet another random port. When it works as intended it's more than secure enough. If they really want to restrict it, just let the user choose in the development settings what interface to listen to. |
|