Project

General

Profile

Actions

Bug #1108

closed

suricata.yaml config parameter - segfault

Added by Peter Manev almost 11 years ago. Updated almost 11 years ago.

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

Description

Further testing the config overriding I stumbled upon a peculiarity.When I start Suri like so:

suricata -c /etc/suricata/suricata.yaml  -i eth0 -v -S empty.rules --set stream.reassembly.memcap=128mb

it works as expected and there is no problem - it overrides the stream reassembly memcap to 128MB.

However if I do this instead:

suricata -c /etc/suricata/suricata.yaml  -i eth0 -v -S empty.rules --set stream.reassembly.memcap=128

Notice the "mb" missing at the end, I get a core dump(attached file has more info).

It can be reproduced with - 2.0dev (rev f791d0f)


Files

BUGS.txt (13 KB) BUGS.txt Peter Manev, 02/11/2014 01:51 PM
Actions

Also available in: Atom PDF