troyhunt

Quickie question guys: I's seeing probes for WPA protected networks, which I'd expect, and the client can't connect through to those which is also the behaviour I'd also expect. The question is this: if the WPA password is known, can the Pineapple successfully emulate both the SSID and credentials effectively allowing the same experience as Karma creates with open networks? And if not, is there something in the wireless protocol that prohibits this or it's simply not a feature in the Pineapple?

Thanks very much everyone who provided assistance here, the problem was indeed the way the drive was partitioned from Windows. I fired up an Ubuntu LiveCD and did it again which fixed the issue right up. For reference, I've written about the process in more detail on my blog under The beginners guide to breaking website security with nothing more than a Pineapple. I'll be using the device in a bunch of different blogging and training contexts to help developers get their TLS right, perfect tool for the job!

Here's what I'm seeing: root@Pineapple:~# ls -la /dev/sd* brw-r--r-- 1 root root 8, 0 Jan 1 1970 /dev/sda brw-r--r-- 1 root root 8, 1 Jan 1 1970 /dev/sda1 brw-r--r-- 1 root root 8, 5 Jan 1 1970 /dev/sda5 brw-r--r-- 1 root root 8, 6 Jan 1 1970 /dev/sda6 So yeah, probably a bit too much going on there! I've been formatting with MiniTool Partition Wizard on Windows (probably obviously Linux is not my daily by now), so that might be it. I'll grab a spare Linux VM from somewhere and format from there, seems like a few others have had issues so worth capturing the result here for future reference. I'll update shortly.

Just the two per Darren's guidance with one intended to be a swap file. Here's what I'm seeing: config global automount option from_fstab 1 option anon_mount 1 config global autoswap option from_fstab 1 option anon_swap 0 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 Anything there look odd?

Here's what I'm seeing - missing something? Guessing that's a "yes" with no USB records. Execute: mount rootfs on / type rootfs (rw) /dev/root on /rom type squashfs (ro,relatime) proc on /proc type proc (rw,noatime) sysfs on /sys type sysfs (rw,noatime) tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,size=14668k) tmpfs on /dev type tmpfs (rw,noatime,size=512k,mode=755) devpts on /dev/pts type devpts (rw,noatime,mode=600) /dev/mtdblock3 on /overlay type jffs2 (rw,noatime) overlayfs:/overlay on / type overlayfs (rw,noatime,lowerdir=/,upperdir=/overlay) debugfs on /sys/kernel/debug type debugfs (rw,relatime) /dev/sda5 on /mnt/sda5 type ext4 (rw,relatime,data=ordered) /dev/sda6 on /mnt/sda6 type ext4 (rw,relatime,data=ordered)

I followed Darren's post on three different drives (one at 4GB) with the same result. Device is running from AC mains and firmware is on 2.8. I'm just a bit suspicious that I can read and write to the drive just fine (and can probably just manually install the infusion if necessary) but can't install to it from the browser.

Hi guys, I'm struggling to get infusions installed to USB despite everything looking like it checks out just fine. Bear with me: USB is formatted for ext4 and shows up just fine under lsusb. I can SSH in and write to /usb without issue so all looks fine on that front. When I install infusions, there's only an option to install to internal storage. I'm not seeing USB anywhere and I'm not sure if it's because I'm missing something or if I'm just not supposed to and I'm simply doing it wrong. Ideas?