Project

General

Profile

Actions
Copy link

Bug #68

closed

thresholding is too strict in it's syntax

Added by Victor Julien about 14 years ago. Updated about 14 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Breno Silva
Target version:
0.8.1
Affected Versions:
Effort:
Difficulty:
Label:

Description

Our thresholding signature support only supports the options to be in a fixed order, while signatures use them in various orders. We need to be able to load those sigs as well.

Files

0001-Allow-threshold-options-in-any-order.patch (5.6 KB) 0001-Allow-threshold-options-in-any-order.patch Breno Silva, 01/24/2010 05:01 PM
Actions
Copy link
 #1

Updated by Victor Julien about 14 years ago

  • Status changed from New to Assigned
Actions
Copy link
 #2

Updated by Breno Silva about 14 years ago

  • File 0001-Allow-threshold-options-in-any-order.patch added
  • % Done changed from 0 to 100

Changed the regex and logic to handle threshold options.

Actions
Copy link
 #3

Updated by Breno Silva about 14 years ago

  • File deleted (0001-Allow-threshold-options-in-any-order.patch)
Actions
Copy link
 #4

Updated by Breno Silva about 14 years ago

  • % Done changed from 100 to 50
Actions
Copy link
 #5

Updated by Breno Silva about 14 years ago

Added a unit test for an invalid threshold rule in any order

Actions
Copy link
 #6

Updated by Victor Julien about 14 years ago

  • Status changed from Assigned to Closed

Applied, thanks Breno.

Actions
Copy link

Also available in: Atom PDF