Rewrite Zeek Module to C++

[stefanDeveloper]

Fixes #4

[stefanDeveloper]

Adjust pre-commit, should we support Windows systems?

[maldwg]

Adjust pre-commit, should we support Windows systems?

I think we can omit windows for our builds

[stefanDeveloper]

Adjust pre-commit, should we support Windows systems?

I think we can omit windows for our builds

Perfect! This simplifies the building and test process.

[maldwg]

LGTM otherwise

[maldwg]

I would be using 8098 as port so that the config.yaml here is directly comparable with the setup in the infra repository.

[stefanDeveloper]

I think, we do not need this / rewrite it to keep the container running. I'll take care if it.

// Replicating Python behavior: run tail -f /dev/null to keep container
// running
std::thread reader_thread([]() {
    FILE *pipe = popen("tail -f /dev/null", "r");
    if (!pipe) {
        spdlog::error("Failed to start tail process");
        return;
    }
    std::array<char, 1024> buffer;
    while (fgets(buffer.data(), buffer.size(), pipe) != nullptr) {
        std::cout << "[ZEEK LOG] " << buffer.data();
    }
    pclose(pipe);
});

[stefanDeveloper]

I also see that in every C++ project in HAMSTRING we use a different logging mechanism, sometimes spdlog and sometimes an abstraction layer. We should define a common logging procedure.

[maldwg]

Seems legit