Update README. Add ideas to TODO after reading the first 20 issues on wifite v1 :(

README.md

@@ -4,21 +4,21 @@ A complete re-write of [`wifite`](https://github.com/derv82/wifite), a Python sc
 
 What's new?
 -----------
-* Lots of files instead of "one big script".
 * Cleaner process management -- No longer leaves processes running in the background.
 * UX: Target access points are refreshed every second instead of every 5 seconds.
 * UX: Displays realtime Power level (in db) of currently-attacked target
+* No more WPS PIN attack (which can take days on-average). But the Pixie-Dust attack is still around.
+* Development: Lots of files instead of "one big script".
 
 What's not new?
 ---------------
 * Backwards compatibility with the original `wifite`'s arguments.
 * Same text-based interface everyone knows and loves.
 
-Full Feature List
+Brief Feature List
------------------
+------------------
-* Reaver Pixie-Dust attack (`--pixie`)
+* Reaver Pixie-Dust attack (`--wps-only`)
-* Reaver WPS PIN attack (`--reaver`)
+* WPA handshake capture (`--no-wps`)
-* WPA handshake capture (`--no-reaver`)
 * Validates handshakes against `pyrit`, `tshark`, `cowpatty`, and `aircrack-ng`
 * Various WEP attacks (replay, chopchop, fragment, etc)
 * 5Ghz support for wireless cards that support 5ghz (use `-5` option)
@@ -28,7 +28,7 @@ Full Feature List
 
 Support
 -------
-Wifite2 is designed entirely for the latest version of Kali Rolling release (tested on Kali 2016.2, updated May 2017).
+Wifite2 is designed entirely for the latest version of Kali Rolling release (tested on Kali 2017.2, updated Jan 2018).
 
 This means only the latest versions of these programs are supported: Aircrack-ng suite, reaver, tshark, cowpatty.
 

TODO.md

@@ -4,6 +4,39 @@ This file is a braindump of ideas to improve Wifite2 (or forward-looking to "Wif
 
 ------------------------------------------------------
 
+### Support Other Distributions (not just Kali x86/64)
+
+Off the top of my head:
+
+* Raspberry Pi (or any Debian distro)
+* Raspberry Pi + Kali (?)
+* Kali Nethunter
+* Various other distributions (backbox, pentoo, blackarch, etc)
+
+Deprecation of "core" programs:
+
+* `iwconfig` is deprecated in favor of `iw`
+* `ifconfig` is deprecated in favor of `ip`
+
+Versioning problems:
+
+* Pixiewps output differs depending on version
+  * Likewise for reaver & bully
+* Reaver and bully args have changed significantly over the years (added/removed/required)
+* airodump-ng --write-interval=1 doesn't work on older versions
+  * Same with --wps and a few other options :(
+* airmon-ng output differs, wifite sees "phy0" instead of the interface name.
+
+Misc problems:
+
+* Some people have problems with multiple wifi cards plugged in
+  * Solution: User prompt when no devices are in monitor mode (ask first).
+* Some people want wifite to kill network manager, others don't.
+  * Solution: User prompt to kill processes
+* Some people need --ignore-negative-one on some wifi cards.
+
+------------------------------------------------------
+
 ### Command-line Arguments
 
 Wifite is a 'Spray and Pray', 'Big Red Button' script. Wifite should not provide obscure options that only advanced users can understand. Advanced users can simply use Wifite's dependencies directly.
@@ -54,20 +87,13 @@ And some native Python implementations might be cross-platform, which would allo
 
 Some of Wifite's dependencies work on other OSes (airodump) but some don't (airmon).
 
-If it's possible to run these programs on Windows or OSX, Wifite should suporrt that.
+If it's possible to run these programs on Windows or OSX, Wifite should support that.
-
-------------------------------------------------------
-
-### Backwards Compatibility
-
-* WIFITE: needs command-line parity with older versions (or does it?)
-* AIRODUMP: --output-format, --wps, and other flags are only in new versions of Airodump.
 
 ------------------------------------------------------
 
 ### WPS Attacks
 
-Wifite's Pixie-Dust attack status output differs between Reaver & Bully. And the command line switches are... not even used?
+Wifite's Pixie-Dust attack status output differs between Reaver & Bully. And the command line switches are... not even used by bully?
 
 Ideally for Pixie-Dust, we'd have:
 
@@ -98,6 +124,8 @@ Users with that kind of dedication can run bully/reaver themselves.
 
 ### Directory structure
 
+**Note: This was mostly done in the great refactoring of Late March 2018**
+
 Too modular in some places, not modular enough in others.
 
 Not "/py":