Project

General

Profile

Actions

Bug #961

closed

max pending packets variable parsing

Added by Peter Manev about 9 years ago. Updated almost 5 years ago.

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

Description

During some tests I have noticed that Suricata parses all the yaml variable in a particular way:

If the variable is lexically correct - no problem. If it is not Suricata silently defaults to the default value.

I did some more test with 1.4.5 and latest git on more yaml variable
and the results are generally the same. One such example -


max-pending-packets: 4096o

Notice the wrongly put letter "O" instead of zero "0" at the end. In this cases Suricata silently defaults to the default 1024 packets.
value:
<Info> - preallocated 1024 packets. Total memory 4362240

I believe this is a general issue with most of the variable parsing from suricata.yaml

Thanks

Actions #1

Updated by Victor Julien almost 9 years ago

  • Target version set to TBD
Actions #2

Updated by Andreas Herz about 6 years ago

  • Assignee set to OISF Dev
Actions #3

Updated by Victor Julien almost 5 years ago

  • Status changed from New to Assigned
  • Assignee changed from OISF Dev to Victor Julien
  • Target version changed from TBD to 4.0.2/4.0.3
Actions #4

Updated by Victor Julien almost 5 years ago

  • Status changed from Assigned to Closed
Actions

Also available in: Atom PDF