Update README. Add ideas to TODO after reading the first 20 issues on wifite v1 :(
This commit is contained in:
46
TODO.md
46
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.
|
||||
|
||||
------------------------------------------------------
|
||||
|
||||
### 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.
|
||||
If it's possible to run these programs on Windows or OSX, Wifite should support that.
|
||||
|
||||
------------------------------------------------------
|
||||
|
||||
### 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":
|
||||
|
||||
Reference in New Issue
Block a user