Created Custom attack scripts (markdown)

Custom-attack-scripts.md

@@ -0,0 +1,34 @@
+## About Custom Attack Scripts
+Custom attack scripts are a part of a new system which simplifies adding new attacks to fluxion. It is, in essence, a method for developers to integrate new attacks quickly into fluxion without having to modify the fluxion executable.
+<br>
+The system offers the following services to new attack scripts:
+* A systematic approach to adding new attacks to fluxion.
+* Quick integration with fluxion by creating an "attack bundle."
+* A method of accessing fluxion globals, such as target AP's ESSID, BSSID...
+* A systematic method of operation, by requiring certain hook functions.
+* A systematic method of attack abortion.
+
+## About Bundles
+An attack bundle is just a fancy term for a directory containing an attack script. These attack bundles <strong>must meet specific requirements</strong> to function properly.
+<br>
+### Attack Bundle Requirements:
+* An attack script, and all assets excluding lib, must be within a directory (with optional subdirectories).
+* The directory mentioned above must be named after the attack performed by the script.
+* The directory must contain an executable script named "attack.sh," containing the attack.
+
+## About Attack Scripts
+The attack script (attack.sh in the bundle) is the primary script of the bundle. It is the only script in the bundle loaded directly by fluxion and <strong>must meet specific requirements</strong> to function properly.
+### Attack Script Requirements:
+* The attack script (attack.sh) must implement four hook functions.
+* prep_attack() - Must prepare the script for the attack, leaving it capable of executing start_attack().
+* unprep_attack() - Must "unprepre," or undo what prep_attack() did, leaving it incapable of executing start_attack().
+* start_attack() - Must start executing the attack in the background and return control to fluxion.
+* stop_attack() - Must stop executing the attack, and all the processes start_attack may have started.
+* Attacks <strong>may not call the functions above</strong>, either directly or indirectly, themselves.
+* Attacks <strong>may not harm the host machine or its user</strong>, either directly or indirectly, in any way.
+* Attacks <strong>must not deviate from these rules</strong>.
+<br>
+Additionally, good practice states custom attacks or any of its scripts <strong>must not modify fluxion globals, the fluxion executable, or any of its assets, directly or indirectly, in any way</strong>. The attack should only modify anything within its bundle, and within the fluxion workspace.
+
+### Attack Script Optionals:
+* Once an attack has started, it may signal fluxion to stop the attack by sending it a SIGABRT signal.