codesign macOS Darwin releases.

[weswhet]

Starting with Apple Silicon machines, all executables will need to be signed in order to run. It would be great to sign the releases, so anyone doing a mass deployment doesn't need to sign it themselves. A simple ad-hoc signature is sufficient for this.

Happy to help with this if needed.

Thanks!

[csstaub]

@weswhet Some help on this would be great. Is there a way to generate the signatures on Linux (since that's where the build executes)?

[weswhet]

I believe so, we should be able to do it with Github Actions if that's an option for this repo.

[mbyczkowski]

I wonder if https://github.com/mitchellh/gon could be helpful here (came across this the other day, but haven't spent much time looking into it).

[csstaub]

Not using GH Actions for the build atm, but I've been meaning to move release builds to GH Actions anyway since it should be more reliable than cross-compilation. @weswhet I sent you an invite to the org

[csstaub]

I have some GH actions here that I was playing around with: #316

[csstaub]

Merged the GitHub actions stuff, so now Ghostunnel can compile natively on macOS. The next problem is that GH actions doesn't have Big Sur VMs yet, and Catalina doesn't support cross-compiling to Apple Silicon.

[thalesfsp]

Merged the GitHub actions stuff, so now Ghostunnel can compile natively on macOS. The next problem is that GH actions doesn't have Big Sur VMs yet, and Catalina doesn't support cross-compiling to Apple Silicon.

@csstaub Latest release is 2020, when u planning to cut a new one (or nothing changed enough to justify that)? Tkx!

[csstaub]

I was planning on releasing a new version once I can get the macOS keychain identities to work with TLS 1.3, see #335.

[thalesfsp]

I see, thank you!