Closed yehgdotnet closed 6 years ago
Heya,
I recall running into a similar problem with an Android 4.x device. Using and Android 5x device worked for me in that case. Admittedly I haven't dived in to deep into why this doesn't work in 4x installations, but my guess is some lack of support in the way the arbitrary class is initialized.
Is it possible for you to test on 5x and let me know?
Yes, I verified it doesn't work on Android 4.x.
I tested it on Android 7.x. It didn't trigger an error.
$ objection run android sslpinning disable
objc[29050]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called.
objc[29050]: +[__NSPlaceholderDate initialize] may have been in progress in another thread when fork() was called. We cannot safely call it or ignore it in the fork() child process. Crashing instead. Set a breakpoint on objc_initializeAfterForkError to debug.
Determining environment...
Running command... `android sslpinning disable`
Job: 846c20af-8103-40f3-9492-6a161b4a8db0 - Starting
[6a161b4a8db0] [android-ssl-pinning-bypass] Custom, Empty TrustManager ready
[6a161b4a8db0] [android-ssl-pinning-bypass] OkHTTP 3.x Found
Job: 846c20af-8103-40f3-9492-6a161b4a8db0 - Started
But interception seems impossible because of new security measure in Android 7
Yeah for Android 7.x I am just going to update the APK patcher to allow you to specify with a flag if a network_security_config.xml
should be included (or add it by default depending on how testing goes).
Awesome, Leon
Looking forward to this update.
I have added some warnings about older Android and iOS version and objection. As for tracking the network security configuration improvement with Android 7, lets use #48.
Hello awesome Sensepost team,
I was running objection on rooted Android phone 4.4.2 and experienced error in doing SSL Pinning on all apps.
Tested platform: Sumsung Android 4.4.2. Tested both: USB, Network
Directly running Pinning code with Frida triggered the same error.