Whistle Master

Hi ! My last addition to our pineapple, a URLSnarf module :) Features - Start / stop urlsnarf from UI - Log history Screenshots

Darren, If you are interested, I would be very keen to help you with such module :)

First version sent to Seb ;)

Hi ! I'm wanted to share my new project for our pineapple: a Mobile UI :) This is far from being ready, not everything is working :P What are you thoughts on this ? Don't hesitate to share your ideas ! This is a capture of the actual version:

Which version of the firmware ? It seems to be an old link. Try to update to last version (v2.0.0)

Regarding (2), if sslstrip is running BEFORE adding the iptables rule, you can still access the pineapple interface (you are redirected yourself through sslstrip). Correct me if I wrong, but this command would not help as we are accessing the pineapple with the IP 172.16.42.42 which is in the source subnet of this iptables rule iptables -t nat -A PREROUTING -p tcp -s 172.16.42.0/24 --destination-port 443 -j REDIRECT --to-ports 10000 except if you are accessing your pineapple from a different subnet like 192.168.1.0/24, right ? We could add the following rule to not redirect our IP to sslstrip: iptables -t nat -A PREROUTING -s 172.16.42.42 -p tcp --dport 80 -j ACCEPT And this IP could also be determined before starting sslstrip from the UI and therefore be anything else. Just a little brainstorm :)

Yes, you can either plug a 3G usb modem or use the Ethernet WAN port.

Your setup seems to be working as expected though. Have a look at those threads (1) and (2). Moreover, if you can connect with your android phone, your setup should be fine. You should see the connected clients on the status page normally and your android phone also.

Actually you can't customize the iptables rules from the UI. I prefer having a standard, simplified and working way for the moment from the UI for most of the users. I assumed advanced users can still go with ssh ;). I will maybe add a configuration section to modify the iptables command. I'm just wondering, in which case(s) you would like to customize the commands ?

I update it to reflect changes from the new v2.0 firmware. Download link is in the first post (and also here)

True :) I simplified to only one link (screenshots are not up-to-date) which will setup and start sslstrip. As soon as I received enough feedback, I will release the first version.

I did not update the advance module manager to reflect the changes brought by the firmware v2.0. I will release an update version later :)

No but as WatskeBart said, it seams that you don't have any connectivity from your pineapple. Can you ssh to the pineapple and try ping 8.8.8.8 -c 10

Well... this is the normal usage of dnsspoof and karma :P All the traffic is redirect to the landing page.

Yes, I mean with a browser. Can you see the list ?

If you manually go to http://cloud.wifipineapple.com/mk4/downloads.php?moduleList, what do you see ?

For those interested, I'm running a test phase for my sslstrip module.

You can perform the update manually through the webui upgrade page. Just download the last version.

I was not really happy with the keylogger module so I chose to not send it to Seb for the new firmware v2.0. I'm working on a new version using ettercap but ettercap is not working as it should for the moment on the pineapple.

Hi ! Since sslstrip is now working, I made a module for it Features - sslstrip log history - iptables rules automatically installed - start/stop sslstrip from ui Screenshots

Last version with Autostart and ignore rules is out :)

Last version with script execution and execution history is out :)

Same for WAN light: root@Pineapple:~# /etc/init.d/led reload setting up led LAN sh: write error: Invalid argument /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:lan/device_name: nonexistent directory /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:lan/mode: nonexistent directory setting up led WAN sh: write error: Invalid argument /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:wan/device_name: nonexistent directory /etc/rc.common: eval: line 1: can't create /sys/class/leds/alfa:blue:wan/mode: nonexistent directory setting up led WLAN setting up led USB

I know ;) But I was not really happy with this module and as we are currently working on a new version using ettercap...

For the moment, as said by Seb, it is not recommended to create symlinks for /www/pineapple/modules to usb ;) The module is done in a way that its location is /www/modules/ and creates symlinks to usb only for data.