They are to be placed to $PATH, which allows to execute the programs from anywhere.
In Termux, the path usually is /data/data/com.termux/files/usr/bin/
. You may need to chmod +x
the scripts and edit paths to the actual programs.
Most of the scripts first change MAC address to random one and up the interface. Any arguments given to the launching script are passed to the actual program.
- OneShot
oneshot
oneshotb
- runs online bruteforceoneshotd
- runs online bruteforce, one attempt per 61 seconds (to prevent AP locking)oneshotf
- Pixie force modeoneshot_webui
- runs OneShot with web graphical interfaceoneshot_update
- updates local OneShot installation (throughgit pull
)
- PMKID Cracker
pmkid
- wigle_companion
wigle_companion
- runs in "dump" mode, meaning it only listens for scanswigle_companionr
- runs in "real" mode, also requests scanning
- eaphammer (not working in Termux, at least for me)
eaph_flush
- flushes output of eaphammer immediately to a fileswitchere
- used to switch between SSIDs from a list in given time intervals
- general usage
ifup
- only sets interface up with random MACifdown
- shuts the interface downexport_wps
- packs reports of OneShot, stored PINs and wigle_companion DB to a zip in Downloads folder, convenient for backups / exportsvibrate
- general purpose script to send a bell to terminal, which makes a vibration in Termux. Unlike in Termux API, the vibration is immediatemyip
- prints current local and public IP address (by web API)ssh_start
- starts SSH server and prints local IP address and portsupl_pass
- just a fancy grep shortcut to search in saved networks
Thanks to @jevgenyonegin for original scripts and inspiration