I dont think so, but maybe..
Also, I am writing and testing this on Kali Linux.. there may be some tweaking necessary to get it to run on other distros..
In the meantime have done some work on input checks on the menu based input and tweaked it a little.
Looking pretty decent so far ;
Now would like to ask you guys for some advice on how you would consider the command line input looking right
and what options should be included.
At the moment I am considering ;
-i --- scan interface (so either mon0 or a monitor interface created from given interface such as wlan1)
-c --- channel to scan on
-s --- scan time in seconds
-m --- menu based input (as per above pic)
-e --- ESSID to search for and to spoof 1st found associated client MAC to your given interface to spoof
-b --- BSSID to search for and to spoof 1st found associated client MAC to your given interface to spoof
-I --- Interface to spoof (for instance wlan1)
So basically thinking the command line input could be something like ;
Searching for essid to spoof a connected client's mac
./mcfib.sh -i mon0 -c 3 -s 25 -e Cisco-Test -I wlan0
or searching for a bssid to spoof a connected client's mac
./mcfib.sh -i mon0 -b 00:11:22:33:44:55 -I wlan0
or running the menu based input
I have a boat load of ideas for options, but dont really want to overload it (yet.. lol)
Also, when requiring to start an interface (such as wlan0) to create a monitor interface, I have included "airmon-ng check kill".
This means an impact on networking, do you guys think that on quit the script should attempt to (re)start networking ?
as this could possibly not be what is wanted, but could I suppose include a query on whether this is desired or not..
Any pointers / ideas ?