3 ms·
Or right-click unsigned binary → Open. The system basically wants acknowledgment from the user that they actually want to run the unsigned binary in question fo
by jwells89 3y ago
Or right-click unsigned binary → Open. The system basically wants acknowledgment from the user that they actually want to run the unsigned binary in question for the first launch, after which it’ll run like normal.
- adastra22 3y agoNot on the most recent macOS releases. I maintain binaries of an open-source app, and used to have instructions to right-click open on first use. This stopped working recently, I forget if it was on version 13 or 14. The users would get a denial, with no option to override. I ended up having to pay $100/yr for a developer account to be able to sign and notarize the binaries. They can now open them like usual, with just a warning that it was downloaded from the internet. But without the signature they get an uncircumventable gatekeeper error. ETA: See https://wiki.freepascal.org/Code_Signing_for_macOS#Big_Sur_and_later_on_Apple_M1_ARM64_processors https://wiki.freepascal.org/Code_Signing_for_macOS#Big_Sur_a...
- jwells89 3y agoI keep my macs up to date and haven't encountered this. Newly downloaded unsigned stuff still works fine. Perhaps there's some sporadic/conditional bug afoot.
- adastra22 3y agoIs it actually unsigned? Or just not developer-signed? Those are different things! When you build an app with Xcode it automatically self-signs app bundles, even if you're not a registered apple developer. Most apps you download are probably built that way. We use cross-compiling infrastructure on linux/docker for the app I maintain, which don't generate these signatures. This causes the resulting binaries to be rejected on recent apple devices (although they used to work just fine with user override on intel-based macs).