Miroslav Stampar

@xECK29x with the latest revision both trail and reference are included too

Thank you for your work, though, you've oversimplified this one: A) `core` is not the Maltrail. `core` is only holding the core functions required by the both `sensors` and `server`...

@jayvdb as far as I can see, you are interested ONLY into trails, because bundling ONLY the core doesn't make any sense. There is no point in making `maltrail` PyPI...

@jayvdb please, I'll do this when I catch time. I just need to think about it to do it properly

@netstat-peanut please update and retry with the latest revision/commit. Patched couple of related bugs

@netstat-peanut can you please retry with the latest revision? @mimugmail I will tag it once the issue is solved. Also, there were no memory-related changes for some time

@netstat-peanut current stdout output should be ok(ish). **[o] running...** runs from that first message until program dies. I've just double checked and it really works as expected, even after X...

@mimugmail tagged this moment the 0.16 (https://github.com/stamparm/maltrail/releases/tag/0.16)

Well, it doesn't go like this. You should send Maltrail "events", like you can find them in Maltrail log files. For example: `data = '"2019-09-10 15:24:40.924790" beast 192.168.5.137 - 136.161.101.53...

Basically, Maltrail's sensor should be used, the complete logic and not the packet forwarder (like you are trying to accomplish). There was a support for Maltrail's sensor years ago for...