If id2t is run with an attack parameter that does not exist, ID2T crashes instead of telling the user something useful.
E.g.:
id2t -i dump.pcap -a portscan asdf.asdf=1
Also, the time it takes to report that a parameter is wrong is long for large pcap files. Errors with the parameters could be reported earlier.
If id2t is run with an attack parameter that does not exist, ID2T crashes instead of telling the user something useful.
E.g.:
`id2t -i dump.pcap -a portscan asdf.asdf=1`
Also, the time it takes to report that a parameter is wrong is long for large pcap files. Errors with the parameters could be reported earlier.
If id2t is run with an attack parameter that does not exist, ID2T crashes instead of telling the user something useful.
E.g.:
id2t -i dump.pcap -a portscan asdf.asdf=1Also, the time it takes to report that a parameter is wrong is long for large pcap files. Errors with the parameters could be reported earlier.
Fixed in commits
cbd485fdf3andcf47547713.