-
Notifications
You must be signed in to change notification settings - Fork 207
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
Fishing Clash app. Some super-duper pinning protection. #89
Comments
Hard to know I'm afraid. I think that DNS error is probably a red herring - it's reported elsewhere (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213178) as a logging issue that doesn't actually affect DNS queries, and I'd be surprised if that was the main problem here. One thing that is unusual is that your IP address in all that output has a preceeding |
Regarding the red herring, you might be right. It’s just that this is the only suspicious thing that i found, and it’s the only connection between Http ToolKit View showing
Regarding the Dot, I have no idea where it came from. Here’s what the config looks like:
(666 is just a quick replacement for this chat) UPD: It seems the issue with Dot has somehow disappeared, but it doesn’t affect the problem with the game. |
There’s a game called Fishing Clash. I’ve been trying to peek into and analyze the HTTPS traffic that this game sends and receives. The game is built on Unity3D, and the crucial networking part operates over RPC via HTTPS. When you cast your fishing line and hook a fish, a mini-game begins where you have to reel in the line. During this time, you don’t know what kind of fish it is, its weight, or quality until you actually catch it. However, all the complete data is sent right at the start of the mini-game.
I’ve been using a script android-certificate-unpinning.js successfully in the Chrome browser and the Twitter (X) app. But as soon as I use it with
com.tensquaregames.letsfish2
(Fishing Clash), it seems some clever ssl pinning defense mechanism kicks in, and the app doesn’t progress beyond the connection stage.I haven’t noticed anything else suspicious. Even intercepting via a VPN method yields the same result. Perhaps this is some intricate defense related to DNSSEC. In any case, I’ve been grappling with this for several days now and would greatly appreciate any assistance.
**Android**
Http ToolKit View:
Aborted connection to letsfish2-b-servers.cf-tsg.net.
Logcat:
I /system/bin/netd: gethostby*.getanswer: asked for ‘letsfish2-b-servers.cf-tsg.net IN A’, got type ‘RRSIG’.
Frida command:
frida -H 127.0.0.1:27042 -l ./config.js -l ./native-connect-hook.js -l ./native-tls-hook.js -l ./android/android-proxy-override.js -l ./android/android-system-certificate-injection.js -l ./android/android-certificate-unpinning.js -l ./android/android-certificate-unpinning-fallback.js -f com.tensquaregames.letsfish2
Frida log:
The text was updated successfully, but these errors were encountered: