Prometheus-2486

Take a look at Social Engineering Toolkit if you haven't. One of its features allows you to "clone" a website (login page only, not a deep clone) on your machine, and then if you have the Pineapple redirect to your machines IP under whatever conditions you give it, the target will get your cloned version and bobs your uncle. SET offers credential harvesting and other goodies as well. Only problem with this credential harvesting attack is SET, when run as a normal MitM instead of a Pineapple, will redirect the target to the real site after a "failed login", but when run with the Pineapple the target isn't redirected properly and they get an endless loop of your cloned site.

Saying the pineapple is limited seems to be jumping to conclusions. Yes, it doesn't support WPA, but its capabilities are very diverse. It was created as a way to lure in clients in public, target rich environments where public un-protected wifi is available. Just need to know how to use it, and the way to do that is to start tinkering every chance you get. Stick with it a while before writing it off as limited.

Oh ok, thanks for the update Seb!

It's not really an issue of storage space, just thougth I'd try and get it working. Definetly not a necessity. And the USB drive it formatted to ext4

Hey guys, just got my Mark V, and after a little experimentation, I can't seem to get infusions to install to USB. Not sure if install to usb was dropped, if I've managed to mess it up, or if I've missed some new instruction somewhere. I've poked around on the forums, and have found no solutions that worked. My pineapple can see my USB drive, and as far as I can tell it's mounted correctly. Really not sure whether the problem is on my end, just assumed it was. Is it possible the Pineapple Bar isn't seeing the USB as a valid place to install infusions? My fstab config: config global automount option from_fstab 1 option anon_mount 1 config global autoswap option from_fstab 1 option anon_swap 1 config mount option target /usb option device /dev/sda1 option fstype ext4 option options rw,sync option enabled 1 option enabled_fsck 0 config swap option device /dev/sda2 option enabled 1 my opkg.conf: src/gz pineapple_packages http://cloud.wifipineapple.com/mk5/packages dest root / dest ram /tmp lists_dir ext /var/opkg-lists option overlay_root /overlay dest usb /usb dest sd /sd The USB drive appears on the list of "Attached USB Devices" on the USB Info tab of the Resources tile. I'm attempting a reflash now, it's taking a while, so if thats fixes the issue I'll delete the thread or mark it solved. Any ideas or solutions you guys can provide are greatly appreciated.

Not sure if I'm interpreting your post right, but wouldn't that just be a MItM attack???

Tested it further. Karma is working, association is going off without any hitches. Not 100% confident though because for whatever reason my mark IV associated fine where i'm at right now, and haven't gotten a chance to do a test in a target rich environment. So hopefully sometime soon I'll get a chance to test it in the wild lol. UPDATE Tested this further, in a target rich environment and the thing decided to stop associating again. So either I received a dud pigtail, broke it while putting it on, or this didn't solve my issue. Any feedback from others that had ordered pigtails? If it seemed to work for others i will order another and give it a shot

Got my pigtail in today, popped it on, and it seems to have fixed the problem. Will test more rigorously in the next few days, but for now it seems to be fixed. Thanks again 10base2 for the solution

Wow, funny how something so simple (loose antenna) happens to multiple people haha good catch, when i checked my connections i missed the tiny twist close to the end on the pigtail connector. Good find 10base2, ordered a replacement, should be here in a few days, ill post again once i get it replaced

Seems like its probably something obscure because not everyone is experiencing it, and version changes dont fix it

I completely understand that sometimes clients wont be able to connect due to distance, secured networks, etc, but ive tried connecting with my own android phone two feet away from my pineapple, directly without even using karma, and i cant connect.

So further investigation has thoroughly confused me lol. After a change of scenery, my pineapple seemed to function properly again. Back to location numero uno, association was impossible again. So I'm assuming my issue is a result of something going on at the first location. Is it possible that someone nearby is whitelisting access points, and sending disassociation packets to any access points not whitelisted? Not sure how I'd confirm something like that, but it seems likely to me that what's happening is clients authenticate, associate, and then are disassociated, where karma attempts to pick them back up again, in an endless cycle. I tried spoofing the pineapple's mac address to that of a legit access point, and also changed the SSID to one that would be whitelisted, but it didn't solve my problem. Hoping someone has some experience in this area that could enlighten me, any help would be greatly appreciated. OR i could just be unlucky and the problem is with the pineapple but it's just very selective lol. Could a messed up setting in the wifi jammer module, or the black list module, cause something like this? Don't believe I've made a mistake there, but it couldn't hurt to check.

Tried another reflash to 2.8.0 just now, still no luck, getting the same result

Hey everybody, been following Hak5 for a while, first time posting, so here it goes. Recently upgraded my Mark IV to 2.8.0, and ever since then my Mark IV has been having problems associating clients. I tried to find the source of the issue but so far a solution has eluded me. First, I noticed my pineapple wasn't associating clients. I attempted to connect via my Android phone, but it endlessly tries to connect, and never could complete the process. I first thought this might be a hardware issue, so I popped the pineapple open to check the connections, and everything looked intact. After this i re-upgraded to see if it would help, and that didn't either. In the pineapples logs there I see these entries over and over again: 19:28:23 Pineapple daemon.info hostapd: wlan0: STA f8:0c:f3:de:ae:13 IEEE 802.11: authenticated 19:28:23 Pineapple daemon.info hostapd: wlan0: STA f8:0c:f3:de:ae:13 IEEE 802.11: associated (aid 1) This occurs with all mac addresses that attempt to connect. What appears to be happening is the clients authenticate, and associate, in a never ending cycle. I'm interpretting this as some kind of failure to associate, or the pineapple keeps dropping clients. Anybody have any ideas as to why this could be happening? Thank you for any help you guys can provide!