Actions
Bug #1108
closedsuricata.yaml config parameter - segfault
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
Updated by Jason Ish about 10 years ago
Note that it also segfaults if you use "128" in the configuration file instead of "128mb", so I don't think this is a result of the set command line parameter.
Updated by Peter Manev about 10 years ago
- Subject changed from Override config parameter - segfault to suricata.yaml config parameter - segfault
Subject edited.
Updated by Victor Julien about 10 years ago
- Status changed from New to Closed
- Assignee set to Victor Julien
- Target version set to 2.0rc2
- % Done changed from 0 to 100
Fixed through https://github.com/inliniac/suricata/pull/855, thanks guys.
Actions