Added by Shivani Bhardwaj over 6 years ago. Updated 2 months ago.
Description
If pcap-file-continuous is fed to suricatasc without any arguments, it hangs the process and starts using too much of processing power.
I guess this is an issue in both suricata and suricatasc? Or only in suricatasc?
Is there a version associated with this?
It seems like passing no arguments to pcap-file-continuous should generate an error due to https://github.com/OISF/suricata/blob/master/python/suricata/sc/specs.py#L28.
Yes, there is an error generated now as the utility was failing on user end. But that is mostly a cover for the issue that lies underneath. If you reset to this commit: https://github.com/OISF/suricata/commit/57285b54d5cf611cee78cef6f428320555cbe90d you can reproduce the issue.
No longer the case in 8 with rust suricatasc