As it is not installed on the target machine and it only generates error
messages.

Facebook uses some more assignments and spam the analysis by them.
Whitelist them as well.

Because pythons GIL ☺

This reverts commit 410107dd.

This reverts commit a80ea208.

This reverts commit 58697377.

So we push data faster. Maybe.

With smaller number of routers, try to fix some errors.

Allow a different filter for blue turris and omnia. Will get reverted
after a short while.

Like, at all.

Since we use our own CA, we need wget to verify it against that. Include
the certificate and link to it.

Test and fix the AmIHacked rust processing. Also include few
improvements:
• Use different hashes in hash tables, to speed up a bit.
• Provide tab in the output instead of a space, as is required by
  to_db.pl
• Accept both compressed and uncompressed input files, as needed by
  repu_add

Testing needed.

Splitting into functions, scoped threads

In parallel across all the input files.

If one client sends broken data, don't kill the whole batch for the
other clients.

The Mirai botnet use some more interesting ports.

The old version of the NetAddr::IP on the server doesn't know the
function and we probably don't care about storing up to two strange IP
addresses.

Omit addresses that shouldn't be on the wide internet. This is things
like local-network addresses, multicasts, etc. These just make little
sense as sources of attacks and it usually means something else than
attacks.

Use the attack kind as the first index and the date as second. First,
the resulting JSONs are likely to be smaller, second, it makes sense to
do a graph of one kind of attack over time, but it makes little sense to
do a graph for single day comparing pears and apples.

Sometimes (observed with at least telnet) it could generate item with 0
occurrences. That one is of no real use for the graphs or statistics, so
avoid generating them altogether.

Add definitions so the events from http proxies may be inserted into the
DB.