Jump to content
Hak5 Forums


Active Members
  • Content count

  • Joined

  • Last visited

  • Days Won


About factgasm

  • Rank
    Hak5 Fan ++
  1. genxint, did this work for you? By the way, you can now update your MK5 to firmware version 3.0.0 by clicking on the post below:
  2. Er . . . what's this?

  3. Mk5 Client Mode - no interfaces?

    I have just upgraded to 3.0.0. It's a lovely lovely new look, it must be said. However still no interfaces showing on the Interface dropdown box of the Wifi Client Mode section. Please help! Is there some command I can issue in the Pineapple's command line I can enter to refresh the interfaces so they show? It is as if a file containing the list of interfaces has been corrupted, but I don't know which file. Please help!
  4. Mk5 Client Mode - no interfaces?

    Seriously would appreciate some help on this. In Recon mode the Pineapple picks up the ESSID for my home wifi but still no interfaces showing on the Client Mode tab of the Network tile. Please help!
  5. On the home page click on Network and then the Client Mode tab. Where it says "Join A Network" click Scan. Now pick an access point from that list and enter the password just beneath. Once joined, go back to the homepage and refresh the Network tab. Should be a-OK.
  6. Mk5 Client Mode - no interfaces?

    Mk5 using firmware version 2.4.0. Did a remote deploy last night. Pineapple was taped up with gaffer tape to protect it from the weather, so no sockets or plugs were exposed whatsoever. We had a torrential thunder storm about two hours after deployment. Got it home this morning, dried off the few drops on it. Opened the pineapple casing - it was bone dry inside. I was able to connect to it from my phone, and from my laptop I could shell in and WinSCP in too, but something didn't seem right about it. Did a factory reset. All four lights, green,yellow, blue, red flashed. Good. Then went to do some basic set up. Went into the Network tile, clicked Client Mode and clicked on the dropdown box next to Interface. There were no interfaces showing and have not been showing since. Please help. I have followed the suggestions on this thread. Shelling in and running the cat /etc/config/wireless from the command line showed no reference to radio1 at all, however an ifconfig shows reference to wlan0 and wlan0-1. PS I have just run iwlist wlan0 scanning and iwlist wlan0-1 scanning and both are picking up the ESSID for my home wifi so it appears both radios survived the weather but still no interfaces showing on the Client Mode tab of the Network tile. Please help!
  7. [Support] Evil Portal

    Fixed! (see below). I have been following frozenjava's excellent Evil Portal videos on Youtube. I have a Pineapple Mk5 running the latest firmware and I have a question for the forum. I watched both the "How to Setup Evil Portal 2.x" and "Getting Credentials with Evil Portal" videos and these were very clear indeed. The Evil Portal infusion is now running and I have editted the code to capture a username and password. I know that frozenjava's HTML and Javascript code works because stepped through it using Visual Studio's debugger. However I think Evil Portal needs some port configuration done to it because so far in testing it, the username and password are not being recorded to the stored.txt file. In Chris Haralson's video "How To: WiFi Pineapple Captive Portal Setup (Evil Portal & NoDogSplash)" he refers to an earlier version of EvilPortal and talks about Configuring UHTTP Daemon. (Go to exactly 3 minutes in). At that point he edits a line "list listen http" and he changes the 80 to read 8080. That is the port number used in frozenjava's code. The problem is that in the Evil Portal 2.4 version - which I have installed on my Mk5 Pineapple - there is no button to click for configuring the UHTTP Daemon. Does that editing need to be done in Evil Portal version 2.4? Do I need to edit the list listen_http value to 8080? Please help! Evil Portal GUI from earlier version showing option to Configure UHTTP Daemon: list listen_http being editted as shown by Chris Haralson: Evil Portal GUI from current version (August 2016) without option to Configure UHTTP Daemon: Fixed! Explanation: frozenjava's Youtube video was recorded using an earlier version of the Evil Portal infusion which used port 8080, hence the reason 8080 is embedded in the javascript. However version 2.4 of Evil Portal runs on port 80 instead. For proof just see below: Note that the command curl - which should cause the capture.php file to execute, - fails because the connection on port 8080 is refused. However, the command curl successfully causes the capture.php file to execute just fine. Quite simply, if you want to adapt frozenjava's code for your own Evil Portal (v2.4), make sure to change the port number from 8080 to 80. That's it, couldn't be simpler. I am a very happy bunny.
  8. I've just completed my first successful flash - thanks to everyone that has contributed to this thread! :)
  9. I have been merrily experimenting with the duck by running duckencode on my Windows command line. I have noticed some of the scripts don't work - almost certainly because I am using a UK keyboard. Could someone point me to the latest version of the jar file so I can run it in Windows please? Thanks. UPDATE: Found it! http://code.google.com/p/ducky-decode/downloads/detail?name=DuckEncoder_v2.6.1.zip&can=2&q= :)
  10. Australia and Indonesia please.