Conversation

Dan Kaminsky
@dakami
Look what you do to people sometimes, security.
Quote Tweet
mcc
@mcclure111
OK so - adb push into the data directory of my application is not allowed because of permissions - but i'm allowed to adb push into a temp directory, then adb shell, then run-as, then copy files over - what. why. - that's slow - can i work around it? - how do people live this way
Show this thread
Image
1
5
mcc
@mcclure111
Replying to
@dakami
it's baffling because there's no security! it makes it really hard to develop code without protecting against any attack i can think of!
2
1
Daniel Micay
@DanielMicay
Replying to
@mcclure111
and
@dakami
The build of an app build being debuggable isn't reflected in the app data permissions. It's not a case of security people locking stuff down and making development inconvenient. ADB is a low-level tool and isn't designed to offer a high level user interface.
3
Daniel Micay
@DanielMicay
Replying to
@dakami
and
@mcclure111
Debugging on a mobile device isn't done the same way as traditional development, since it's tethered to another host. ADB is the low-level implementation of that bridge between the devices. It's not a debugger or an app development tool.
2
Daniel Micay
@DanielMicay
Replying to
@DanielMicay
@dakami
and
@mcclure111
It's the base for higher-level tools by bridging between the devices. For example it can proxy gdb <-> gdbserver on the device and similarly for jdb, perf, etc. The app layer could be completely different like a desktop Linux stack without app sandboxing and ADB wouldn't change.
2