Project

General

Profile

Bug #139

Scan Delay Does Not Apply to New Rules

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

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

100%

Description

NSIA does not apply the standard scan delay to newly created rules. Thus, rules get scanned almost immediately and may get scanned twice if a user presses the manual scan button.

History

#1 Updated by Luke Murphey almost 14 years ago

  • Assignee set to Luke Murphey

#2 Updated by Luke Murphey almost 14 years ago

This is going to require a database schema change since scan rules do not currently retain a create or modification date.

#3 Updated by Luke Murphey almost 14 years ago

Added created and modified dates to the ScanRule class and verified that they are being set properly.

Created and modified dates maintained per changes in r469.

#4 Updated by Luke Murphey almost 14 years ago

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

Implemented 5 minute delay in r470.

Also available in: Atom PDF