Project

General

Profile

Bug #4

Scan Policy Does Not Disable ThreatScript Definitions

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

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
04/08/2010
Due date:
% Done:

0%

History

#1 Updated by Luke Murphey about 14 years ago

ThreatScript definitions seem to execute even though they are disabled.

#2 Updated by Luke Murphey over 13 years ago

  • Status changed from New to Rejected

Disabling the definition just causes it to be ignored in the reports. Execution should still continue since they may set variables that are used by other definitions.

#3 Updated by Anonymous over 13 years ago

MaUhfQ <a href="http://pwdohlsqoujo.com/">pwdohlsqoujo</a>, [url=http://akywjzqdhwiv.com/]akywjzqdhwiv[/url], [link=http://llhkmnmmxtcp.com/]llhkmnmmxtcp[/link], http://qsovlabuhwlh.com/

Also available in: Atom PDF