CAG-Script - Bash script to automate MITM's, deauth's, passive sniffing, etc

CAG-Script v0.6

Hi guys,
This is a script that I wrote that automates running Ettercap-ng, Arpspoof, Sslstrip, the Dsniff suite, Nmap, Airdrop-ng, and other programs. If Airdrop-ng is not installed (as is the case for a BT4 live cd), the script will give you the option to install it.

Feel free to modify this script, I don't claim to have come up with all of it.
Thanks to all of the members of the Backtrack forums past and present for your continued help.

This script is very much a work in progress and therefore any help would be appreciated. After it is "completed", I will hopefully write a tutorial on using it. I the meantime, I will try to answer any questions that I can.

Main Script: CAG-Script v0.6 (hosted on pastebin.com)

Script to install Airdrop-ng: Installairdrop-ng-script (hosted on pastebin.com)

Very simple macchanging script: Macchanger-Script (hosted on pastebin.com)

You would do well to paste the script here in your above post so that others can review it. Use the code tags.
There may be those that do not trust the source website.

Moderators, feel free to delete this post as it is simply clogging up this thread. Thanks

Moderators, feel free to delete this post as it is simply clogging up this thread. Thanks

Moderators, feel free to delete this post as it is simply clogging up this thread. Thanks

when I run your script it says

"line 50: syntax error near unexpected token Configmenufunc()"

Quote:

---

Originally Posted by farang

when I run your script it says

"line 50: syntax error near unexpected token Configmenufunc()"

---

It's improper syntax for bash scripting.
If you want to correct all of them you will need to change functions to:

Code:

---

function FunctionName {
...
}

---

I get this error : bash: ./Sniffer_plus.sh: /bin/bash^M: bad interpreter: No such file or directory

Quote:

---

Originally Posted by Guerreiro

I get this error : bash: ./Sniffer_plus.sh: /bin/bash^M: bad interpreter: No such file or directory

---

You probably saved this script on a windows machine first.
If that is the case run the script through dos2unix, and it should fix it right up.

Just wanted to say thanks :)

I only wish i had a bit more time to work with it :(