-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[!] Could not find the required code to patch! #31
Comments
Did you fix the problem? |
Did you fix the problem? |
link on file https://ufile.io/srik0y6y |
if anyone have problem with version app you can use this rep https://github.com/pouyadarabi/Facebook_SSL_Pinning. That helped me so much |
@depocoder I tried the x86 version of your link with Android x86 (64 bit 7.1-r5) on VirtualBox (configured with a host-only adapter) but we cannot get past the login page, I can just see the login request in mitmproxy. If I try with the original APK from your link without replacing libcoldstart.so and without using a MITM proxy but a normal proxy like Squid, I cannot get past the login page either, probably because it is an old Facebook app not supported anymore. Update: the repository https://github.com/pouyadarabi/Facebook_SSL_Pinning is archived and I read "Deprecated: Use Facebook whitehat setting". I did not understand this sentence before but there are some articles like https://techmonitor.ai/technology/cybersecurity/facebook-whitehat-settings explaining that Facebook now allows to sniff the traffic without the need of reverse engineering the Android app. Update 2: I was not able to inspect requests of the Facebook Android app using the White Hat settings with mitmproxy, I got the error "tlsv1 alert unknown ca" (mitmproxy/mitmproxy#145 (comment)). Was someone able to inspect requests of the latest Facebook Android app using the White Hat settings or another method? |
Followed the steps, but had difficulties. I was able to find the libcoldstart.so file in /data/data/com.facebook.katana/lib-compressed, but got this error message.
The text was updated successfully, but these errors were encountered: