-
Notifications
You must be signed in to change notification settings - Fork 277
Fix README.md accuracy: correct version, CLI flags, and dead links #458
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,4 +1,4 @@ | ||||||
| [](#) | ||||||
| [](#) | ||||||
| [](https://github.com/kimocoder/wifite2/issues) | ||||||
| [](https://github.com/kimocoder/wifite2/network) | ||||||
| [](https://github.com/kimocoder/wifite2/stargazers) | ||||||
|
|
@@ -23,8 +23,6 @@ Wifite is designed to use all known methods for retrieving the password of a wir | |||||
| 5. WPA3: Transition mode downgrade attacks (force WPA2 on mixed networks). | ||||||
| 6. WEP: Various known attacks against WEP, including *fragmentation*, *chop-chop*, *aireplay*, etc. | ||||||
| 7. **Evil Twin**: Rogue AP attack with captive portal for credential capture. | ||||||
| 8. WIFI Signal jammer, block specific accesspoints or multiple. | ||||||
| signal jamming only works for specific Atheros WiFi chipsets. | ||||||
|
|
||||||
| Run wifite, select your targets, and Wifite will automatically start trying to capture or crack the password. | ||||||
|
|
||||||
|
|
@@ -58,7 +56,7 @@ Supported Operating Systems | |||||
|
|
||||||
| ### Mobile Support 📱 | ||||||
| * **Kali NetHunter (Android)** - Requires custom kernel with monitor mode support | ||||||
| * Tested on Android 10 to latest 16 | ||||||
| * Tested on Android 10 and newer | ||||||
| * Requires compatible wireless adapter and proper drivers | ||||||
| * See [NetHunter Documentation](https://www.kali.org/docs/nethunter/) for setup | ||||||
|
|
||||||
|
|
@@ -83,8 +81,7 @@ Second, only the latest versions of these programs are supported and must be ins | |||||
|
|
||||||
| **Required:** | ||||||
|
|
||||||
| * Suggest using `python3` as `python2` was marked deprecated as of january 2020. | ||||||
| * As we moved from older python and changed to fully support and run on `python3.14` | ||||||
| * `python3` (Python 3.9+, tested up to Python 3.14) | ||||||
| * [`Iw`](https://wireless.wiki.kernel.org/en/users/documentation/iw): For identifying wireless devices already in Monitor Mode. | ||||||
| * [`Ip`](https://packages.debian.org/buster/net-tools): For starting/stopping wireless devices. | ||||||
| * [`Aircrack-ng`](https://aircrack-ng.org/) suite, includes: | ||||||
|
|
@@ -161,8 +158,6 @@ poetry shell | |||||
| sudo wifite | ||||||
| ``` | ||||||
|
|
||||||
| **See [POETRY.md](POETRY.md) for detailed Poetry usage and commands.** | ||||||
|
|
||||||
| ### Development Install with pip | ||||||
|
|
||||||
| For development or if you want to modify wifite: | ||||||
|
|
@@ -238,7 +233,7 @@ Features | |||||
| * **Manual Control** - Specify primary and secondary interfaces manually | ||||||
| * **Backward Compatible** - Seamlessly falls back to single interface mode | ||||||
| * **📖 Complete Guide:** [Dual Interface Guide](docs/DUAL_INTERFACE_GUIDE.md) | ||||||
| * **🔧 Troubleshooting:** [Dual Interface Troubleshooting](docs/DUAL_INTERFACE_TROUBLESHOOTING.md) | ||||||
|
|
||||||
| * **Wireless Attack Monitoring** - Passive detection and analysis of wireless attacks (use with: `--monitor-attacks`) | ||||||
| * **Real-time Detection** - Identifies deauthentication and disassociation attacks as they occur | ||||||
| * **Attack Statistics** - Tracks attack counts, targeted networks, and attacker devices | ||||||
|
|
@@ -342,7 +337,7 @@ sudo apt update | |||||
| sudo apt install hcxdumptool hcxtools hashcat | ||||||
| ``` | ||||||
|
|
||||||
| **📖 For detailed installation instructions, version requirements, and troubleshooting, see [WPA3 Tool Requirements Guide](docs/WPA3_TOOL_REQUIREMENTS.md)** | ||||||
| **📖 For WPA3-specific troubleshooting, see [WPA3 Troubleshooting](docs/WPA3_TROUBLESHOOTING.md)** | ||||||
|
|
||||||
| #### Understanding WPA3 Network Types | ||||||
|
|
||||||
|
|
@@ -425,7 +420,7 @@ sudo wifite --monitor-attacks --monitor-hop | |||||
| sudo wifite --monitor-attacks --monitor-log /path/to/attack_log.txt | ||||||
|
|
||||||
| # Use classic text mode instead of TUI | ||||||
| sudo wifite --monitor-attacks --classic | ||||||
| sudo wifite --monitor-attacks --no-tui | ||||||
| ``` | ||||||
|
|
||||||
| #### Understanding the TUI Display | ||||||
|
|
@@ -523,7 +518,7 @@ sudo wifite --monitor-attacks --monitor-hop --monitor-log "attacks_$(date +%Y%m% | |||||
| sudo wifite --monitor-attacks --monitor-log /var/log/wifite/attacks_$(date +%Y%m%d).log | ||||||
|
|
||||||
| # Monitor specific channel in classic mode (no TUI, lower resource usage) | ||||||
| sudo wifite --monitor-attacks --monitor-channel 1 --classic --monitor-log attacks.log | ||||||
| sudo wifite --monitor-attacks --monitor-channel 1 --no-tui --monitor-log attacks.log | ||||||
| ``` | ||||||
|
|
||||||
| **Incident Response:** | ||||||
|
|
@@ -576,7 +571,7 @@ sudo wifite -i wlan0mon --monitor-attacks --monitor-channel 6 --monitor-log comp | |||||
| **Optimization Tips:** | ||||||
| - Use `--monitor-channel` to focus on specific channels for better performance | ||||||
| - Avoid channel hopping on busy networks to reduce CPU usage | ||||||
| - Use classic mode (`--classic`) on resource-constrained systems | ||||||
| - Use classic mode (`--no-tui`) on resource-constrained systems | ||||||
| - Regularly rotate log files to prevent excessive disk usage | ||||||
|
|
||||||
| **Scalability:** | ||||||
|
|
@@ -866,10 +861,10 @@ Performance Tips | |||||
| * **Use a dedicated wireless adapter** - USB adapters often perform better than built-in cards | ||||||
| * **Position matters** - Get closer to target networks for better signal strength | ||||||
| * **Choose the right channel** - Use `-c <channel>` to focus on specific channels | ||||||
| * **Limit concurrent attacks** - Use `--first 5` to attack only the strongest targets first | ||||||
| * **Limit concurrent attacks** - Use `-first 5` to attack only the strongest targets first | ||||||
|
||||||
| * **Limit concurrent attacks** - Use `-first 5` to attack only the strongest targets first | |
| * **Limit concurrent attacks** - Use `--first 5` to attack only the strongest targets first |
Copilot
AI
Mar 6, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
--pmkid is implemented as “PMKID only” (it disables other WPA/WPS attacks), but the text says “PMKID first”, which implies it will try PMKID and then fall back to other methods. Reword this to reflect that --pmkid restricts attacks to PMKID capture only, so users don’t accidentally reduce their success rate.
| * **PMKID first** - Try `--pmkid` for fastest WPA/WPA2 attacks (no clients needed) | |
| * **PMKID-only mode** - Use `--pmkid` to restrict attacks to PMKID capture only (disables other WPA/WPS methods and may reduce overall success rate) |
Copilot
AI
Mar 6, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Markdown formatting: this line begins with *** (no space after the list marker), so it won’t render as a proper list item and may be interpreted as bold/italic emphasis instead. Add a space after the bullet (e.g., * **[Evil Twin Attack Guide]...) to keep the documentation list formatting consistent.
Copilot
AI
Mar 6, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR description mentions adding a “Dual Interface Examples” doc link, but the README’s Documentation section doesn’t currently include it. If that addition is intended, add the missing bullet/link here (the file docs/DUAL_INTERFACE_EXAMPLES.md exists).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
Ipdependency link points to Debiannet-tools, butipis provided byiproute2(and the codebase’s dependency metadata forIpalso references iproute2). Update this link/text to avoid directing users to the wrong package.