not able to sniff com.peacocktv.peacockandroid #97
Comments
|
Interesting! Thanks for the detailed report. What happens if you skip the The In general it would be interesting to try skipping various scripts or commenting out certain patches, to see if you can work out which part of these scripts is causing this issue. It's also worth running using Frida but with no scripts at all - some apps actively detect Frida and fight against it, and some versions of Frida have bugs that crash under certain conditions, which means sometimes apps will crash with any use of Frida (regardless of these scripts). |
|
thank you for your response @pimterry, it must def be a me thing, so what i did is that i grabbed the certificate from proxyman from here I commented out the Which is happening with these ones at least the app doesn't crash anymore but i'm still not able to see traffic going thru, I'm assuming it's because of this particular error. |
|
also the error above appears when i add the |
|
Hi @luisfernandez93 I've just pushed a fix (8ca3cb5) for the native-tls-hook script, which might help resolve this (at the very least, it should avoid the To confirm your config is working correctly, it would also be helpful to try installing https://github.com/httptoolkit/android-ssl-pinning-demo on your device and check that you can intercept that correctly. If your config and scripts are set up properly, every button except the last one should work correctly and its corresponding request should appear in your proxy UI (don't worry about that last button - by design this is a custom check that isn't automatically covered). If some of those don't work then most likely your certificate config is wrong or Proxyman is doing something weird, it's hard to be more specific there though. If those do all work then your general setup is OK and something much more specific is going on. |
|
@pimterry thank you, so I tried running the demo app with frida got the error as i pressed the first button
when i pressed the unpinned request, it became red, i do see something in the proxyman app tho this is how it looks like when i don't use frida i press the buttons and they become green. I will try now with Charles. |
|
with Charles i sort of get the same pain point.. and same error, I think I'm doing something clearly wrong lol :D |
|
Yes, that unpinned request failing definitely means your certificate isn't trusted at all. That should be trusted either by installing it in the system certificate store (HTTP Toolkit ADB setup does this for you automatically) or using the That said, I've just released an HTTP Toolkit update you might find interesting: it now does automated Frida setup and configures & runs these scripts automatically, in one click. It's also totally free & open-source - want to try that it and see if it works for you? If you download the latest version from https://httptoolkit.com/ and run it then you should see the new "Android app via Frida" (and "iOS app via Frida") buttons light up if you have a suitable device attached to your computer. |
|
oh wow so yeah I used httptoolkit and I'm def sniffing traffic, however the app keeps on not able to do certain http requests, I'm using an emulator I'm wondering if I should go ahead and use a real device I just didn't want to root my phone lol also i'm not able to see which request is failing. 
I'm pretty sure the app doesn't like that i'm on the emulator, I feel like if i had the actual device it probably would work. 
the iOS app via frida is grayed out for me. |
The iOS option will activate when you have a connected iOS device (after accepting the trust prompts on device etc). For interception to work though, it needs to be jailbroken and running Frida server. This was only just released, and there'll be detailed docs for this (and walkthrough guides) available soon.
That means the basic setup is working at least, but there's some other issue that this script doesn't cover. I've just given this a quick test, and on my machine (with an emulator and a US VPN) I can start the app and start intercepting, but I quickly get a 403 response from tv.clients.peacocktv.com, which seems to be an Akamai endpoint. It's hard to know for sure, but I'd best this is TLS fingerprinting (some context: https://httptoolkit.com/blog/tls-fingerprinting-node-js/) which Akamai uses to block all sorts of slightly unusual clients. If you're seeing unexpected 403 errors causing issues, that could well be the cause, and will create issues with any kind of proxy intercepting tool unfortunately (the fingerprints for all of them are fairly easily distinguishable from direct traffic from a normal Android app). I'm working on some improvements here (openssl/openssl#19220) but it's going to be a long-term project and I can't offer many good solutions there in the short term. |
|
@pimterry thank you so much for all your help and support appreciate it a lot, it seems like I cannot do much for this app in particular right, at this moment. |
so I have been trying to use this btw thank you very much... so my current setup is
android emulator, pixel 3a upsidedowncake, frida and proxyman,
what i did:
override config.js in this repo with my own cert_pem which proxyman i think puts in
/Users/blabla/.proxyman/proxyman-ca.pemthen i ran the following:
what I see in logs:
The app starts and then shuts off.
this is what i see in when i use
adb logcat -T1The text was updated successfully, but these errors were encountered: