strazzere / android-unpacker

Android Unpacker presented at Defcon 22: Android Hacker Protection Level 0
Apache License 2.0
1.12k stars 331 forks source link

DexProtector #21

Closed aleks921 closed 8 years ago

aleks921 commented 8 years ago

My android tools packed with DexProtector. How unpack this protector ? Can you add unpack this protector in your tool ?

geo2550 commented 8 years ago

What maybe

George Whitehill On Jun 3, 2016 7:05 AM, "aleks921" notifications@github.com wrote:

My android tools packed with DexProtector. How unpack this protector ? Can you add unpack this protector in your tool ?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/strazzere/android-unpacker/issues/21, or mute the thread https://github.com/notifications/unsubscribe/AEr9eQyDPGZcPH0xK_T8R6Wrz2S0mEbvks5qIBh6gaJpZM4Itd3Y .

aleks921 commented 8 years ago

How unpack this protector ? Help me please.

strazzere commented 8 years ago

Follow the directions in the README. This however is a relatively old project, so it depends on which version of dexprotector was used for the APK in question. Feel free to post it if you'd like - however this isn't really an "issue" with the project.

aleks921 commented 8 years ago

How know version of dexprotector on this apk ?

aleks921 commented 8 years ago

It http://rgho.st/8Bqs7JDxG apk with DexProtect. Do you can say me about version ?

strazzere commented 8 years ago

"My android tools packed with DexProtector."

If it's yours, then I'd assume you know what version you used ;)

aleks921 commented 8 years ago

It isn't my project. Packed not me. Can you know version ? How find version in this protector ?

strazzere commented 8 years ago

Unsure, it's newer than I've seen (Everything encrypted and stripped) I'd suggest trying to use the LKM method described by the antiunlink module;

https://github.com/strazzere/android-lkms

aleks921 commented 8 years ago

How install LKM method ? On windows or linux or android this tools need install ? Nedd root on android ?

aleks921 commented 8 years ago

How install your tools https://github.com/strazzere/android-unpacker on android ? I download package on android and in directory your project do comand: make, but android write that "make not found". How install on android this ? Help me please.

CalebFenton commented 8 years ago

Why are you trying to install this on Android? You'll find it's much easier to install on Linux or Mac. You'll need build tools and a working NDK environment.

strazzere commented 8 years ago

Yes, what @CalebFenton started discussing. Sadly, I'm not going to have enough time to attempt to do support for setting up the NDK, compiling files, etc. This is a highly technical project which has a rather high bar set for using the tools.

I'll also note that it's very likely that the APK you're referencing may not be unpacked properly by this project (thus why I suggest using the android-lkm project). You'll likely have more success getting this unpacked by finding (or likely by hiring) a technical person to do this work for you.

aleks921 commented 8 years ago

Ok, I understand that on Linux, but after install need push compiled tools on android or stay on linux ? I dont understant this comand in readme adb shell ./data/local/tmp/kisskiss com.package.name.to.unpack This ./data/local/tmp/kisskiss adress in Linux or need compiled tools push in android in ./data/local/tmp ?

strazzere commented 8 years ago

kisskiss is the binary which is cross compiled on your host system. This gets pushed (uploaded) to the device and run on the device via the command adb shell ./data/local/tmp/kisskiss com.package.name.to.unpack

aleks921 commented 8 years ago

Thank you for your answer. I want ask yet question about NDK, Android NDK need install on Linux only for build and install kisskiss tool ? After upload kisskiss on android virtual device NDK is not required yet in my system Linux ? Can I after compile and upload kisskiss on android do comand "adb shell ./data/local/tmp/kisskiss com.package.name.to.unpack" on Windows system without NDK ?

strazzere commented 8 years ago

The Android NDK is required to compile the code, as stated in the README;

https://github.com/strazzere/android-unpacker/blob/master/native-unpacker/README.md

You could likely compile this on Linux or Windows, personally I did this on OSX. If compiling on Windows, you likely would need to modify the make file - or potentially use cygwin or something. Honestly, I'm not sure. Once the binary is compiled, you wouldn't need the NDK anymore - unless you need to modify the code (and recompile, etc).

After you have the binary compiled, it doesn't matter what system your using, as long as you can use adb to interact with the device and already pushed kisskiss to the device.

aleks921 commented 8 years ago

Thank you. I will compile on Linux. I use emulator Genimotion. Can you say about SELinux, in this emulator this disabled or not ? And how off SELinux if enabled in this emulator.

strazzere commented 8 years ago

I don't know, you'll likely need to modify the make file to create a x86 binary for Genimotion. I can't speak towards what level of SELinux they have though.

aleks921 commented 8 years ago

The original Make file for ARM virtual devices only ? If i do not modify make, so the binaries will only run on ARM devices?

strazzere commented 8 years ago

Yes;

https://github.com/strazzere/android-unpacker/blob/master/native-unpacker/Makefile#L1

I'm not going to reply to this thread anymore. You need to figure out the rest of the steps yourself, I'm not going to do this work for you.

aleks921 commented 8 years ago

I understand, thank you for your answers.

aliheidari020 commented 7 years ago

Plz help me I run adb shell ./data/local/tmp/kisskiss com.package.name.to.unpack Will not run properly https://s11.postimg.org/l9qqlzfsj/Untitled.png

strazzere commented 7 years ago

1 - Please open a new issue. 2 - It would appear you've compiled it (maybe correctly?) - though you're literally trying to run it against com.package.name.to.unpack which does not likely exist. 3 - You probably just need to chmod the binary, but I don't know...