MacOS ja4/ja4x binaries?

[Squiblydoo]

Hello!
Is there a reason for not building the ja4 and ja4x binaries for MacOS? I was unable to find past discussion regarding this.

I built the binaries in my own fork by uncommenting two lines in the existing workflow:

          - { os: macos-latest, target: x86_64-apple-darwin }
          - { os: macos-latest, target: aarch64-apple-darwin }

Because they aren't signed, I needed to first run them using the "Gatekeeper bypass" (command key + right click > "open" > hit "OK"). However, they seemed to work as I expected in my initial tests.

Is there something else I am missing in regards to why FoxIO doesn't compile them already? Or maybe it is just because of the signing issue?

Cheers.

[vvv]

@Squiblydoo Initially the Rust apps (ja4 and ja4x) were developed in a closed repository. We did build unsigned macOS binaries there, but that drained our CI/CD minutes quickly and I commented those YAML lines out.

But this repository is public. Meaning that its usage of GitHub-hosted runners is free:

GitHub Actions usage is free for standard GitHub-hosted runners in public repositories, and for self-hosted runners.

Re signing of macOS binaries, I for one don't have the bandwidth to jump into this particular rabbit hole. Fortunately, as you've correctly determined, we can easily provide unsigned macOS binaries — it's a matter of uncommenting 2 lines of code. I've submitted PR #174 that does just that.

Thanks for raising this issue!