Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286.
Invalid header block at offset unknown at /usr/bin/pulledpork line 286
Until then, I understood that the meerkat problem exists with one of the rules, but I don’t understand the reason.
I’m also trying to find a solution but I can’t find a solution. There was no update for suricata for a long time, only the rules were updated in the background. They also write about this in the attached link, but there is no solution, because it seems that there may be a problem with the creation and format of the rule. I hope the package makers will notice and fix it, until then the meerkat rule won’t work.
Does suricata still work or does the Nethserver remain unprotected?
The update notification has arrived. In the evening, when everyone has finished the work, I will update and in the morning I will see the result of the repair.