fix: sign binaries added in https://github.com/ipfs/service-worker-gateway/releases/tag/v1.12.0

[SgtPooki]

We should ensure build-binary.yml is signing the binaries so we don't get messages like this:

[SgtPooki]

attempting fix with cb6906c

[SgtPooki]

another change: ccf5543

[2color]

How can I get the latest binary? I just tried running the binary from https://github.com/ipfs/service-worker-gateway/releases/tag/v1.12.0 and got the same error.

After manually allowing it in the Privacy and Security config in MacOS, I get the following when I open it:

[SgtPooki]

@2color macos binaries should working now. service-worker-gateway-aarch64-apple-darwin from https://github.com/ipfs/service-worker-gateway/releases/tag/v1.12.0 worked for me.

windows signing is not working currently because we don't have a valid cert, so that's disabled.

I'll resolve this once:

1. someone on windows acknowledges that the .exe works for them
2. someone on linux acknowledges that those binaries work for them

[SgtPooki]

Works on windows but users will see

Windows protected your PC
Microsoft Defender SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk.

App: 
service-worker-gateway-x86_64-pc-windows-msvc.exe 
Publisher:  
Unknown publisher 

[2color]

In order to get the binary to run on MacOS I had to chmod +x it, after which I was able to run it both from the terminal as well as by just double clicking it in the finder

[SgtPooki]

@2color ahh yea me too.. we don't want users to have to do that. We should update the build-binary step to do that for us

[SgtPooki]

@lidel you handle a lot of the windows certs.. do we have updated ones we can use or do we want to deprioritize this for now?

[lidel]

deprioritize

• windows does not block running unsigned binaries, only shows scary warning – CLI users on Windows are either used to that, or run Linux VM/env anyway, so not blocking anyone
• for windows we only sign ipfs-desktop, we don't sign Kubo nor any of the binaries on https://dist.ipfs.tech and have no turn-key solution that works with Azure Trusted Signing Service (requires research, testing – time sink)

[2color]

Re #718, the binary in the latest release is still missing executable permissions.