Reverse Engineering Native Apps by Intercepting Network Traffic
1–10 of 76 posts
Re: Reverse Engineering Native Apps by Intercepting Network Traffic
#2Isn't it possible for apps for ignore the OS's proxy settings and make a direct TCP connection? In that case the proxy man-in-the-middle trick won't work.
Re: Reverse Engineering Native Apps by Intercepting Network Traffic
#3[deleted]
Re: Reverse Engineering Native Apps by Intercepting Network Traffic
#4Isn't it possible for apps for ignore the OS's proxy settings and make a direct TCP connection? In that case the proxy man-in-the-middle trick won't work.
At least on Android you can generate a fake VPN-esque connection locally that passes everything through a proxy, so the proxy isn't exposed to the application
Re: Reverse Engineering Native Apps by Intercepting Network Traffic
#5Isn't it possible for apps for ignore the OS's proxy settings and make a direct TCP connection? In that case the proxy man-in-the-middle trick won't work.
[deleted]
Re: Reverse Engineering Native Apps by Intercepting Network Traffic
#6There is also a way, on rooted Androids, to sniff SSL pinned Apps.
SSL pinned is not an protection for reverse engineering anymore, you may want to add this info on your post.
More info at
Re: Reverse Engineering Native Apps by Intercepting Network Traffic
#7There is also a way, on rooted Androids, to sniff SSL pinned Apps.
SSL pinned is not an protection for reverse engineering anymore, you may want to add this info on your post.
More info at
Re: Reverse Engineering Native Apps by Intercepting Network Traffic
#8Isn't it possible for apps for ignore the OS's proxy settings and make a direct TCP connection? In that case the proxy man-in-the-middle trick won't work.
In that case I would look into ARP poisoning.
Re: Reverse Engineering Native Apps by Intercepting Network Traffic
#9I had to do this recently and found a great tool for Android for sniffing traffic on the device called Packet Capture. It can even sniff SSL without root permissions by installing a self-signed certificate and running an in-app local VPN proxy. It also had a bunch of other nice features like parsing common protocols, showing the good bits of HTTP, etc. Much nicer than the approach described here (this article is from 2013), although it's certainly only for Android folk.
I don't think it's FOSS, but hopefully a FOSS alternative will come along and use this approach.
Re: Reverse Engineering Native Apps by Intercepting Network Traffic
#10Isn't it possible for apps for ignore the OS's proxy settings and make a direct TCP connection? In that case the proxy man-in-the-middle trick won't work.
Yes. Socket programming. A number of banking apps in the UK use the connect(2) etc, although I can't say if this is the reason. It's most likely to make it a touch more difficult to reverse than hooking NSURLConnection etc.