kitsumed

6 ms·

1.
by kitsumed 2mo ago
The person who made that suggestion (sa...@google.com) is presumed to be the one of the main maintainer of ADB as their name (Fabien Sanglard) showed up in non-redacted in the history and CC here ( https://android-review.googlesou
2.
by kitsumed 2mo ago
The On-Device ADB work-arounds and a lot of open-source apps related to it are already in that fragile workarounds "zone". For most, this is the last resort / only way possible. As AOSP refuse to add secure permission or serv
3.
by kitsumed 2mo ago
From memory, for the kimwolf exploit things, other user already had good points about the device already beeing compromised. But also, the authentification part of ADB was just completly disabled, which is why this worked. Basically it was
4.
by kitsumed 2mo ago
Spyware using ADB could be a thing (assuming someone has full access to your phone, including the password). However, it is impractical, as a reboot, system update, or Wi-Fi change would likely break everything. It is much easier for spywar
5.
by kitsumed 2mo ago
> However, ADBD in this situation only sees a connection attempt, not which app made the attempt, right? Every ADB connection has some kind of certificate / key that is saved locally. This means that a new application would have a d
6.
by kitsumed 2mo ago
If I didn't word it like that (I'm the author) the "reddit mob" would have exploded the thread. That's the last thing I want. I want valuable feedback there, for now its somehwat working. Most of the users who saw t
7.
App to Record phone call on Android 11-16, without root, FOSS, privacy friendly(github.com)
1 points by kitsumed 4mo ago|0 comments