Jump to content

Sailor

Active Members
  • Posts

    64
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Sailor

  1. Try to have a look at tcpdump, it should be installed on the MKIV.
  2. Try this one: DATE=$(date +"%Y%m%d%H%M") tcpdump -n -C 128 -W 100 -i br-lan -w /sd/log/packetlog-$DATE.pcap >/dev/null 2>&1 & You can remove the -C and -W switches if you want just one big file
  3. I guess that would work. I have put this in a script that is called from a specific bootmode (from the GUI: configuration -> Bootmodes) I don't want to start Karma all the time No, that won't work. Just type 'hostapd_cli -h' in a SSH session to see the available options.
  4. You are right! My mistake, bad suggestion, don't use --ivs
  5. I have the following in my bootscript which prevents my other devices to connect to the MKV: # Start Karma hostapd_cli -p /var/run/hostapd-phy0 karma_enable >/dev/null 2>&1 & sleep 2 # Add own MAC addresses hostapd_cli -p /var/run/hostapd-phy0 karma_add_black_mac 00:XX:XX:XX:XX:XX > /dev/null hostapd_cli -p /var/run/hostapd-phy0 karma_add_black_mac 01:XX:XX:XX:XX:XX > /dev/null Looking forward to that!
  6. Nope, sorry. I never converted a capture file to hccap, I have just (succesfully) used the cap file in aircrack-ng. Maybe it would help to try the --ivs option in airodump-ng? This would only capture the required packets for cracking.
  7. I cannot tell from the screenshots if you have followed the right steps to capture a handshake (the last step I see is a deauth, but that doesn't guarantee that there is a reconnect from this client). And yes, sure this is possible. Try using the wifite python script (search on this forum). This automates the steps required to capture a handshake.
  8. Hard to tell without studying the source (https://github.com/bdpurcell/bully) but the author says the main differences with Reaver are:
  9. You should take br-lan as the interface (not sure if you mean that with 'port') for instance: tcpdump -n -C 10 -W 100 -i br-lan -w /sd/packetlog.pcap (this will create a maximum of 100 files, each 10MB big with all traffic from connected clients)
  10. Wifite works perfect on the MKV, just don't use the dictionary attack (WPA key cracking with pyrit/cowpatty), that would take too much time because of the limited processing power. Just follow the installation steps on: https://code.google.com/p/wifite/ No further configuration needed.
  11. Do you share internet from the MKV to the Pi or the other way around? Does this work without difficult configuration?
  12. Will require a bit of configuration but it is very likely that this will work since this is all Python based. Just need to install Scapy + nfqueue-bindings (BeEF will be a harder).
  13. As I understood the modems mentioned in this URL are considered to be supported by the Pineapple: http://www.draisberghof.de/usb_modeswitch/device_reference.txt
  14. The wait command is not intended for that. Try using sleep. In my script I use a couple of sleep commands, it adds up to about 180 seconds so you should be fine with that. I think it doesn't even matter for autossh since it will keep trying to make a connection.
  15. You can add the following to your boot dip script: /etc/init.d/autossh start >/dev/null &
  16. No problem to use the MKV battery packs from the shop for the MKIV. Same voltage and connector.
  17. Nope, urlsnarf doesn't provide that option. You can schedule the following script to run for instance every 15 minutes: #!/bin/sh logger "Clean-up Script Executed" # q = threshold in bytes q=52428800 w=`ls -la /sd/urlsnarf.log | awk '{print $5}'` if [ $w -ge $q ]; then logger "Log over threshold, zip and truncate" DATE=$(date +"%Y%m%d%H%M") gzip -f /sd/urlsnarf.log mv /sd/urlsnarf.log.gz /sd/$DATE.urlsnarf.log.gz echo "Log truncated" > /sd/urlsnarf.log else logger "Log looking good" fi
  18. I use the following which is at least more secure than the ftp solution: tail -f file-on-pineapple.log | ssh username@remoteshell "cat >> file-on-ssh-server.log" If you have setup your ssh connection right you will not be prompted for a password. Other options to look at are rsync and nc (netcat). The latter has a nice tutorial in the Hak5 channel on Youtube.
  19. You could use the following: tail -f /tmp/karma-phy0.log | grep 'pass\|AP-STA-DISCONNECTED\|Successful' | awk '{ print strftime("%Y-%m-%d %H:%M:%S"), $0; }' >> /sd/karma.log Modify the grep query to fit your needs, this logs connects and disconnects. If you want to log probes you would probably pipe through uniq as well.
  20. Already found out myself. Version 0.9 can be used: opkg update opkg install pyopenssl wget http://www.thoughtcrime.org/software/sslstrip/sslstrip-0.9.tar.gz -O /sd/sslstrip-0.9.tar.gz cd /sd tar zxvf sslstrip-0.9.tar.gz cd sslstrip-0.9 python ./setup.py install Install the sslstrip infusion (1.4) after this. Sslstrip will then run with version 0.9 instead of 0.6 from the Web UI.
  21. I have had this in my log on both the Mark IV en V but never found a solution. It doesn't affect the workings though (as I know of).
  22. Not sure how this is with the Mark V but my guess is that a laptop USB port has too little power (500 mA) where you probably going to need 1A+
  23. I would add a step 10. 10. (Double) Check polarity of your new cable and check if this is identical to the original cable. Switching polarity causes on instant fry of your device.
×
×
  • Create New...