Jump to content

Sebkinne

Root Admin
  • Posts

    3,978
  • Joined

  • Days Won

    331

Everything posted by Sebkinne

  1. The file name needs to be lowecase "md5" not "MD5". But instead, I suggest you follow our "Unbricking a bricked WiFi Pineapple MKV" guide. Even though you don't have a brick, this is the fastest way to get up and running. Best Regards, Sebkinne
  2. Usually because of an error with the files written to the SD card. We have implemented some new QA procedures to stop this from happening in the newer batches. Don't worry though, this will get you up and running. Best Regards, Sebkinne
  3. What instructions are you following? You should be following our "unbricking a bricked wifi pineapple mkv as outlined here: https://wifipineapple.com/?flashing This avoids the use of the SD card entirely. Best regards, Sebkinne
  4. All is possible. It's also quite possible that this was a lavabit style going out. Maybe a warrant cannary? Best Regards, Sebkinne
  5. Like you would in bash, with a ; or an && - depends on what you want to do. Also, it is important that you background long running processes. If you can do it in the command line, you can do it via a DIP switch. But why not just make a quick script and put this in your DIP configuration: /path/to/my/script.sh & Best Regards, Sebkinne
  6. Sure! The command you put in there is executed using bash. That means running "ls -ls > /tmp/ls_output" will do just that. That also means that running "/etc/my_script.sh" will execute that script. It's really that simple. The commands are executed on boot. We actually suggest pointing a DIP at a script rather than a command as it keeps it a bit more clean. Saying that, updating the DIP UI is on our list to make it more intuitive soon. Best Regards, Sebkinne
  7. Exactly. But if the private key has been compromised.. that is moot.
  8. I'll make sure to get that sorted for you. Please forward the email at seb [ a ] hak5.org. Best Regards, Sebkinne
  9. The biggest issue I see is this: We do not know the identity of the truecrypt maintainers. We do not know if the private key used to sign the binaries was compromised. This means that there is no real way of knowing if this was a hack or real. The maintainers could now change the website, show us a new key and say "Sorry, we got hacked" - but can we verify this is actually them? It's hard to tell what will happen..
  10. This. It's probably not bricked - just no LEDs setup. Best Regards, Sebkinne
  11. Come by IRC and we'll figure this out. Best Regards, Sebkinne
  12. Yeah, no idea where I got 211 from. Anyway, the above will do the trick for a static script indeed. You will also want to basically decrease the wait timeout to a second or so - as the script will be executed in a blocking manner, you won't need the delay. Best Regards, Sebkinne
  13. Quickly looking at the source, patching this functionality in is rather trivial. See line 143 of cracker.c. Simply do a system call to a script there. If you wish to change the script locations, you'll need to look at argparser.c and globule.c. You would have to add the argument to argparser.c and a get/set pair to globule.c. I might do this when I get some time.. Best Regards, Sebkinne
  14. Note that this is most likely illegal and can get you in serious, serious trouble, especially at airports.
  15. Seen yes, but if it fails to associate with another network, we mark it as unsupported. Best regards, Sebkinne
  16. I'll say it again for clarity: This is a feature, not a bug. Only clients connected to the access point with means of karma are shown in this list. If you have been connected beforehand or cleared the karma log, your devices will not show up in the Karma intelligence report. If you want to see all clients connected via wlan0 to your WiFi Pineapple, execute "iw dev wlan0 station dump". Best Regards, Sebkinne
  17. We just released a quick bugfix release 1.4.1 - fixing 3g modems and a couple other small fixes. Best Regards, Sebkinne
  18. We will release a fixed 1.4.1 asap. Thanks! Sebkinne
  19. Xt4xt1X, Can you execute the following two commands and see if it fixes the issue? opkg update opkg install kmod-usb-serial-option We will add the pincode option to the interface soon too - please create a suggestion on our bugtracker to help keep track of current suggestions :) Best Regards, Sebkinne
  20. Seeing as the WiFI Pineapple MKV webinterface is written in PHP and Javascript, it is easily found on every WiFi Pineapple MKV in the /pineapple folder. While the code is open source, it is under a non-commercial licence. Mind if I ask what you want to change and / or make better? Best Regards, Sebkinne
  21. You may have lost connection to the internet for a little while. I suggest you close the window and try again. Best Regards, Sebkinne
  22. For that to work, you will need to arp cache poison your targets first to become the man-in-the-middle. Best Regards, Sebkinne
  23. I have flown countless times and I usually carry a WiFi Pineapple + the big batter around with me. Never have I had any issues with it. The battery is checked once in a while (swabbed for particulates), and they might ask me to prove it can power my WiFi Pineapple MKV, but it has never been an issue. Just DO NOT use it on a plane. That's going to break a few laws. I hate to waste time travelling and often work on the WiFi Pineapple in the air. I do this by completely disabling the radios before my travels and usually just use ethernet / serial cables to work on it. This has caused a few flight attendants to ask me what it was and what I was doing, but has never caused any issues whatsoever. To be safe though, unless you are developing on it, you have no reason to use it during a flight. Keep it turned off. Best Regards, Sebkinne
  24. On the hakshop, we offer Sandisk Ultra 16 and 32GB cards with the WiFi Pineapple Builder. These cards have proven to be reliable and fast for the WiFI Pineapple MKV. Best Regards, Sebkinne
  25. ptrac3, From the information given, it is hard to think of why it works via the command line but not the webinterface. Can you set up Client Mode through the webinterface and then check your /etc/config/wireless file? Does this have all the correct information? If not, let us know what is wrong. Otherwise, if the above file is correct, please run the "wifi" command (while connected over ethernet) and make sure to note it's output. Best Regards, Sebkinne
×
×
  • Create New...