Introduction

Scripting Editor/Debugger

Although not necessary to develop in the editor, it is safer, faster and better to create both correct and actually working scripts. This will ensure proper functioning of the script when inserted into the vulnerability scans unit of the GFI LANguard security scanner tool. In the GFI LANguard editor/debugger you can run the script under development in the same conditions as if it was running under the security scanner in a real life situation. You have a controlled environment in which you can create, analyze, refine and investigate problems prior to putting the script into action on a live security scan. The GFI LANguard editor/debugger has all of the supporting functionality like breakpoints, step into, step over, as well as capabilities to specify parameters to be passed to the script to enable proper testing without the need to scan a machine over and over again.

WARNING: Running and debugging the scripts with the scanner is not recommended and should never be allowed since if there is anything wrong in the script, that script will never work and also the user will have no way to see why it is not working. The scanner will automatically ignore incorrect/non functioning scripts.

WARNING: If a script is not properly scripted and debugged there can be a high probability that it will go into infinite loop situations which can stall some parts of the scanner. Scripts are executed in order one after the other. There is no timeout capability. If a script needs 10 minutes or more to execute it will not be stopped. The scripting engine will wait for it to finish before moving to the next script.

Script editor / debugger

Feature list present in GFI LANguard debugger

• Support for variable watches - monitor in real time the changing values in variables used.

• Step into / Step over functionality to debug your scripts line by line while monitoring what is going on during execution of the script.

• Syntax highlighting - easier to program scripts and locate problems

• Comprehensive error messaging - indicates the type and location of the errors. Helps detecting variable type based errors.

• Breakpoint - the debugger supports breakpoints which will shift into line by line debugging at a particular point of interest - Very significant aid when developing complex scripts.

• Capability to debug and run the script under alternative credentials during the script development and debugging process.