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
Actions