Actions
Bug #694
closedYaml variables - leading to segfault
Affected Versions:
Effort:
Difficulty:
Label:
Description
As reported by rmkml and Nikolay Denev - i did some more experimenting.
Suriacta 1.4 Release segfaults when " (quotes) are not used around net or port variables.
if the value is "any" - without " (quotes) - it does not segfault.
Also it does not dump a core file - maybe this is a separate bug.
root@ubuntu64LTS:~# suricata -c /etc/suricata/suricata.yaml -i eth0 1/1/2013 -- 14:35:00 - <Info> - This is Suricata version 1.4 RELEASE 1/1/2013 -- 14:35:00 - <Info> - CPUs/cores online: 2 1/1/2013 -- 14:35:00 - <Info> - Found an MTU of 1500 for 'eth0' 1/1/2013 -- 14:35:00 - <Info> - allocated 229376 bytes of memory for the defrag hash... 4096 buckets of size 56 1/1/2013 -- 14:35:00 - <Info> - preallocated 1000 defrag trackers of size 144 1/1/2013 -- 14:35:00 - <Info> - defrag memory usage: 373376 bytes, maximum: 16777216 1/1/2013 -- 14:35:00 - <Info> - AutoFP mode using default "Active Packets" flow load balancer Segmentation fault (core dumped) root@ubuntu64LTS:~# ls -lh total 20K drwxr-xr-x 2 root root 4.0K Oct 26 11:17 Desktop -rw-r--r-- 1 root root 1.2K Dec 10 21:12 index.html drwxr-xr-x 13 root root 4.0K Dec 27 16:22 oisf drwxr-xr-x 3 root root 4.0K Dec 4 21:47 suri-buildbot drwxr-xr-x 3 root root 4.0K Dec 29 18:10 work root@ubuntu64LTS:~# pwd /root
Actions