Repository navigation
Home
Reference documentation for wifisting, a GTK4 wireless security toolkit for Linux. 58 modules covering Wi-Fi, Bluetooth, RF, router-side and network MITM work behind one interface.
This wiki is the reference. The README is the introduction — read that first if you haven't.
| Page | What it covers |
|---|---|
| Getting Started | Build, first run, and what to expect |
| Hardware | What each adapter buys you, and what works without one |
| Modules | Every module, what it does, and how to call it |
| CLI Reference | Running modules directly, without the GUI |
| Troubleshooting | When something doesn't work |
| Contributing | Testing, reporting, and code conventions |
Every module is a standalone script. The GUI is a view over them, not a container.
That means anything you can click, you can also script:
$ modules/41_wifi_geolocate.sh --apple-lookup e4:9e:12:05:34:59
e4:9e:12:05:34:59 43.2255745 0.0792846 45
$ modules/30_fingerprint.sh --scan wlan0
$ modules/53_jamming.sh --caps-tsvEverything lives in modules/. Run any of them with --help for its verbs,
or --selftest to check it works without touching hardware.
cd native
meson setup builddir
meson compile -C builddir
cd ..
./wifisting.shwifisting.sh launches the GUI, or the terminal interface if you prefer.
Both drive the same modules.
wifisting is early. It has been tested thoroughly on one machine, with one adapter. That is a real limitation and it is stated plainly rather than buried.
What this means in practice:
- Modules that need hardware you don't own will tell you so, by name, rather than returning an empty result
- Every module ships a
--selftestthat passes with no hardware attached. If a selftest fails on your machine, that's a bug worth reporting - The honest failure mode is the design goal: a module reporting success while the target is untouched is worse than one that fails loudly
See Hardware for what each radio unlocks, and the README for the current state.
- Bug or unexpected result — open an issue. Include your distro, adapter, and what you ran
-
Question about a module — run it with
--helpfirst; the verbs and their arguments are documented there - Something failed silently — that's the bug class worth reporting most. A module that reports OK while doing nothing is treated as a defect
