Project

General

Profile

Feature #151

Terminate Function for ThreatScripts

Added by Luke Murphey over 14 years ago. Updated over 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Luke Murphey
Category:
-
Target version:
0.9 (Beta)
Start date:
05/12/2010
Due date:
% Done:

100%

Description

Add ability to define a terminate function that allows ThreatScripts to endnicely if the ScanEngine needs to end execution.

History

#1 Updated by Luke Murphey over 14 years ago

  • Target version set to 0.9 (Beta)

#2 Updated by Luke Murphey over 14 years ago

  • Assignee set to Luke Murphey

#3 Updated by Luke Murphey over 14 years ago

Need to determine if globally scoped variables persist (otherwise, the terminate function won't be usable)

#4 Updated by Luke Murphey over 14 years ago

Terminate function has been added but it has a negative side-effect. The scope of the global variables is global (affects all rules being executed in the scan engine) and persists through the entire session (until the scan engine is terminated).

The only way to prevent this is to spawn multiple instances of the definition and perform the analysis.

#5 Updated by Luke Murphey over 14 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Implemented in r464. Unfortunately, the script engine must be reinitialized for every evaluation since the environment must be rebuilt (otherwise some variables may be carried over from previous executions). This may cause a slight adverse effect on performance.

Also available in: Atom PDF