-
Posts
39 -
Joined
-
Last visited
Posts posted by comatose603
-
-
Also, I see that iptables has port 80 and 443 setup. Yet ../bin/sslsort isnt being run with the -a command. Is this right? If I manually start it with -a https traffic starts to work again.
-
Dunno if this matters, but I have an autostart.sh for sslsort in /usb/infusions/ (what rc.local links too) that has port 80 and 443, and one in /usb/modules that just has an iptables command for just port 80
-
Seems to be related to SSLstrip. If I turn it off the Facebook iPhone app all of a sudden starts working again; but SSLstrip isnt capturing any https traffic at that point.
-
I have an iPhone connected to the Pineapple (2.7.5). And, while http traffic works just fine in Safari, the Facebook iPhone app cannot update. Any ideas as to what is going on?
-
What was done to try and fix it?
-
Which Firmawre version are you using? The last updates have fixed issues like this. Try to upgrade your pineapple.
2.7.5
-
When I try to use this card it grabs wlan0 and the Pineapples onboard interface ends up on wlan1 causing all sorts of issues. How do I get this bloody awus036 to goto wlan1?
-
Just your typical setup. Pineapple into laptop via eth, ./wp4.sh, laptop is connect to internet via its own wlan0 and a nat'd wifi-router.
-
Any update on this?
-
Is there a fix for this yet?! Whistle Master said he was taking a look at it a few weeks ago:
-
Actually, it used to be the intended purpose. I suggest you upgrade to 2.7.5 as from 2.7.1+ there have been fixes for exactly that!
Just upgraded to 2.7.5. Having the same issue. Install Jammer. Pick wlan1. And the Pineapple reboots itself.
Another issue is autostart does not work with sslstrip (in 2.7.5 either I see). In order to get it working I had to add the full path to sslstrip in rc.local and the full path to python in autostart.sh.
Also, can I run sslstrip and urlsnarf at the same time in this release? That was another issue that, being new to the product and not knowing there was a confict, drove me insane at first.
-
The reason karma starts on both interfaces is because AP mode is turned on on both cards. You will need to turn AP mode off in the /etc/conf/wireless for your wlan1 interface.
What firmware version are you running?
Ah, that make sense. The latest stable... 2.7.0 Considering people will expect the optional Alpha usb radio to just work when they buy it with the Pineapple shouldnt this be turned off by default?! Not everyone is smart enough to realize the Jammer module isnt working because some hostapd process is fighting wtih it.
-
On boot Karma is starting on wlan1 as well as wlan0. Which causes the jammer and mdk3 to go crazy. How do I tell Karma to leave wlan1 alone?
urlsnarf module simultaneously with sslstrip module?
in WiFi Pineapple Mark IV
Posted · Edited by comatose603
Why is iptables setup for port 80 and 443? Moxie's instructions say to just do port 80...so...??? And, if I leave it as such with both port 80 and 443, https traffic stops working for clients.
Also, Moxie's sslstrip is up to 0.9. Why are we still on 0.6? ... it doesnt seem to be stripping all SSL POSTS, e.g., Gmail logons produce nothing. [EDIT: ah, HSTS sites that why]