Hello Eric, i've been racking my brains for the last few days figuring out why i cant sniff my twitter android app traffic anymore!
Basically what worked before was that i had simply installed fiddler proxy on my PC, exported the root certificate (and added it to my android devices CA storage), then i installed cydia's mobile substrate and Android-SSL-TrustKiller because apparently the twitter apk uses certificate pinning that needs to be bypassed in order to properly MitM the app. I set my android wifi proxy settings to the same ip:port as the machine that fiddler is listening on.
Unfortunately this does not work anymore and im left unable to properly read twitters app traffic, whereas googleplay, facebook, instagram, etc etc all work fine. It had worked fine until a few days ago. I hadn't updated my twitter app either so im just not sure how it could have broke itself.
I tried proxydroid (which uses iptables i believe), and fiddler showed attempts at connecting to one of twitters ip, but it never goes through (i believe this is an issue with the IP not resolving to the host-name correctly, which causes certificate name mismatch errors)
With standard wifi proxy tuned to fiddler, i dont see ANY requests. With proxydroid, i see this http://gyazo.com/6792f884e1f88453a8cacb1632d0b3d5
(tones of CONNECTS and cert mismatches, despite having imported fiddlerroot into CA storage.
I'm incredibly vexed...i need someone who can help me properly diagnose and fix this issue.
If it helps, im on a SGS3 android version 4.1.2 (I even tried genymotionemulator, yielding the same results).
Basically what worked before was that i had simply installed fiddler proxy on my PC, exported the root certificate (and added it to my android devices CA storage), then i installed cydia's mobile substrate and Android-SSL-TrustKiller because apparently the twitter apk uses certificate pinning that needs to be bypassed in order to properly MitM the app. I set my android wifi proxy settings to the same ip:port as the machine that fiddler is listening on.
Unfortunately this does not work anymore and im left unable to properly read twitters app traffic, whereas googleplay, facebook, instagram, etc etc all work fine. It had worked fine until a few days ago. I hadn't updated my twitter app either so im just not sure how it could have broke itself.
I tried proxydroid (which uses iptables i believe), and fiddler showed attempts at connecting to one of twitters ip, but it never goes through (i believe this is an issue with the IP not resolving to the host-name correctly, which causes certificate name mismatch errors)
With standard wifi proxy tuned to fiddler, i dont see ANY requests. With proxydroid, i see this http://gyazo.com/6792f884e1f88453a8cacb1632d0b3d5
(tones of CONNECTS and cert mismatches, despite having imported fiddlerroot into CA storage.
I'm incredibly vexed...i need someone who can help me properly diagnose and fix this issue.
If it helps, im on a SGS3 android version 4.1.2 (I even tried genymotionemulator, yielding the same results).