Closed athray closed 8 years ago
I can still capture with PAD 8.2.2, so it's most probably an issue with Android 6. I'll upgrade my Nexus7 and check it something breaks.
I've reproduced the issue with my upgraded Nexus 7.
Auto-Wifi is broken because I had to use private, unstable APIs to set the proxy. That happened for 5.0 and can probably be fixed.
But the core issue is that PAD calls do not go through the proxy at all. I've tried using the Manual Wifi mode, PADListener can capture the adds and Google Analytics calls on PAD's title page, but nothing else :/ I've no clue why that's happening. I can only guess that PAD simply won't work when using a Wifi with a proxy.
I've checked : Auto Iptables mode still works.
Thanks for the update, I appreciate it. I'm not really android or development savvy so there's not a whole lot I can do aside from offer to help test any new solution you come up with.
I think that PAD version 8.2.2 went full SSL so this complicates things a lot.
I don't think so.
I've been able to capture without issue using the Auto iptables mode. The only issue is that PAD seems to ignore the Wifi proxy settings which breaks Manual and Auto Wifi modes.
Is there a workaround that doesn't involve rooting my phone?
Are there alternative applications or processes that can update PADHerder?
Since root still involves flashing a decrypted kernel and formatting data on the nexus 6p, could you please confirm you are working on a non-root solution? Thanks?
I am using mitmproxy to workaround this issue. If your PAD Version uses https (mine does) you need to install mitmproxy certificate on your phone.
What it basically does is setup a proxy on your computer, then you setup your phone to point to your computer's ip addres port 8080 (default mitmproxy port) and you should start seeing traffic going through mitmproxy.
Steps:
mitmproxy
(no extra params)pc.ip.add.ress
8080
mitmproxy
console and use arrow keys
to move through entriesEnter
on that lineTab
to switch to Response
b
to save resultSeems cumbersome, but it is actually pretty easy once you get the hang of it.
What's weird is that on my Nexus 4 running Android 6.0, it seems that PAD doesn't use the proxy configuration. Can you confirm that this workaround works on 6.0 ?
And yes, I'm trying to implement a new listener mode that doesn't require root, but still works on every version. I don't have an ETA though.
I've been using padproxy.py and burpsuite to capture json box data as well, with a Nexus 5 on Android 6.0 and the setup is very similar on the android side, I think the only difference is I use a different port and set a static IP for the device. So I can confirm that the PAD traffic is going through the proxy.
Is it possible to add the feature of importing a JSON file? It's easier to control what to update comparing to importing the file in padherder.
Mitmproxy refused to install correctly, and padproxy.py couldn't get HTTPS data for me. Charles proxy worked though, and had a good GUI, making things nice and easy. Looking forward to the next iteration of padlistener to make all this stuff unnecessary.
Also using Charles proxy for now. Just right click the correct API (get_user_data) and hit save response. Upload the php file and then you're done.
Yet another temporary workaround for people on Windows (tested on JP today, works fine with latest 8.6.2 and Android Kitkat 4.4.2):
Thanks to the other commenters above for showing the way!
It's a rather cumbersome method, but yeah, hoping it'll be rendered unnecessary by the next awesome PADListener update. :)
No fix yet for the auto proxy ( http://developer.android.com/about/versions/marshmallow/android-6.0-changes.html#behavior-network ) But I managed to get the capturing of SSL work again in 6.0 , see my pull request : https://github.com/Neraud/PADListener/pull/97
After updating to Marshmallow, I have been unable to capture PAD box data, I did both of these updates nearly simultaneously so I'm not sure which broke the listening functionality.
My device is a Nexus 5 if that matters at all.
I've attempted force stopping the PAD process before relaunching it but that doesn't seem to have solved anything, behavior is the same. PAD launches, no response or notification from PAD listener that anything was captured.