Conversation

Look what you do to people sometimes, security.

Quote Tweet

Oct 13, 2018

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

Replying to

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!

Replying to

and

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.

Replying to

and

but adb is the user interface people use in practice it just doesn't seem to make sense to offer a high-level user primitive like recursive push, but not offer the high-level user primitive of run-as, especially given recursive push is much less useful without run-as?

Replying to

and

App developers are expected to use Android Studio including the gradle-based app builds and other tooling. OS developers use ADB with userdebug builds where tools like `adb root` and `adb sync` exist. There are a lot of differences between the tooling for each including building.

10:40 PM · Oct 13, 2018Twitter Web Client

Replying to

and

I find these expectations unreasonable and it seems to me if google were paying attention they would most likely find they don't match user stories as well as they should for that to justify shipping broken basic tools