Description
Describe the issue
All dev binary files for macOS (i.e., stockfish-macos-m1-apple-silicon) are flat out rejected by macOS and can't be executed, because the OS isn't able to verify their digital signature, since they don't have any.
The binary files for macOS of Stockfish's final release versions (like 16, 16.1, 17) work fine, since they include a digital signature, but those dev versions of binary files don't have a digital signature and are thus blocked by macOS, even if the com.apple.quarantine extended attribute of the file is removed. It also doesn't help if a binary file is made executable, even if it is already, but just to be sure.
Expected behavior
I expect all dev binary files for macOS to be executable.
Steps to reproduce
- Download this Stockfish dev binary file for a Silicon-based Mac
- Unpack the downloaded TAR file
- Double-click the
stockfish-macos-m1-apple-siliconbinary file, found in thestockfish-macos-m1-apple-silicon/stockfishdirectory - You will get a warning message, and all you can do is put the file in the Trash
Anything else?
I haven't been able to test the Intel-based versions of Stockfish dev binary files, because I only have a Silicon-based Mac. I imagine the issue would be the same.
At compile time, all those binary files for Intel-based and Silicon-based Macs should get a digital signature, even if they are just development versions of Stockfish. This will certainly solve the issue, but I hope it is doable.
Operating system
MacOS
Stockfish version
All dev binary files for macOS