Mr-Protocol

http://www.aircrack-ng.org/doku.php?id=compatible_cards That would be a good place to start looking.

:)

What do you mean by "Load Test"? That is probably what triggered it if I had to guess.

I would make sure you have permission first to do such testing. Keep it real, keep it legal. :D

Please refer to this URL: https://www.wifipineapple.com/?flashing https://www.youtube.com/playlist?list=PLW5y1tjAOzI1benBAgqAbMExp5dWkQLgO You can most likely get it up and running yourself without having to ship it back and forth.

Waaaaaaaaaant. *Gets credit card ready* Great work team, as always stepping up the game!

Is your target machine 32 bit Windows? I don't remember if there is a x64 shikata_ga_nai. Give this a read: https://www.offensive-security.com/metasploit-unleashed/

Try installing it with PTF. https://github.com/trustedsec/ptf

Yes, the USB-Micro cable is meant for charging only. It is not a data cable.

There is a way, it would be with the twin duck if I'm not mistaken. I honestly haven't played around with that. It would require a different firmware flashed on your ducky.

*Shrug* working fine on my Nexus 6P using Chrome. Any other iOS users having this issue?

Moved to ducky forum. Try a GUI key combination like GUI+R to bring up the run box. Also, your initial delay may not be long enough to have the ducky identify with the OS. Check this for some examples: https://github.com/hak5darren/USB-Rubber-Ducky/wiki/Payloads

There are devices out there that will help determine pinouts for JTAG/Serial/UART. But with a little searching I found this. It helps to remember I found my pinouts on openwrt site a few years back. https://wiki.openwrt.org/toh/netcomm/nb6plus4w May not be the exact model, but should get you in the right direction. What is the FCC ID of the device? When the device is powered, you should be able to test for voltage and ground on those pins with a multimeter. The other two would be TX and RX. You only need to connect TX, RX, and GND to your TTL adapter and power the device with the wall wart as normal operation. If you can't communicate with standard bauds (maybe the ones from the link above), then swap the cables on the pins you believe to be TX and RX. Try again. If smoke comes out of anything, you did something wrong :P

Kellyd3454 may not have permission due to account restrictions on the forums. I will promote the account and please try again.

Haha, well done Barry.

You could try ddrescue to image the disk. It will skip bad sectors, etc. You can tell it to skip right to the byte offset of /dev/sdb5 if you know the offset or can get a read on the MBR or GPT to get the locations.

https://forums.hak5.org/index.php?/topic/37064-introducing-the-wifi-pineapple-nano/?p=269121

DefCon, DerbyCon, ? not sure what else. Depends on if the time hits right.

I wonder if the phones are waiting for the correct SSID to broadcast before making more traffic. Do you have an idea as to what the phones are or if that is the case? Here is a github I plan on doing more of, just starting out with it: https://github.com/Mr-Protocol/DerbyCon_WarWalking In time I'll have a lot more SSIDs.

You have to have something plugged in to enable tethering I'm pretty sure. You can connect with the Management WiFi AP and navigate to 172.16.42.1:1471 that way. And the app I think only looks for the pineapple. I need to buy a USB C to OTG to test my NANO on the Nexus 6P. Well coding is all text ;) but he has awesome people to help him with color schemes.

About .5 inches thick http://imgur.com/a/8iUDf

Great work as always! I love seeing how this project has grown. CHEERS!

I would suggest you do some research into the output you have. There are actually two different hashes there. But an experienced pentester should already know that ;)

I'm guessing that's from a Windows machine? Hopefully from a legit pen-test.

Make sure you updated the tools. I know SET gets updated pretty frequently.