4 ms·
Please note that Apple's linker will automatically ad-hoc sign binaries if you aren't using a signing certificate so there is no impact to package managers or a
by xenadu02 6y ago
Please note that Apple's linker will automatically ad-hoc sign binaries if you aren't using a signing certificate so there is no impact to package managers or any other forms of building software to run locally. Xcode already automatically opts such software out of GateKeeper checks when built from the UI. Similarly adding Terminal to the Developer Tool category in System Preferences will do the same for anything you run or build there.
I should also note directly launching the binary inside the App bundle from Terminal bypasses the UI dialog. The assumption is you know what you are doing in that case.
- wila 6y agoYou can run your own binaries locally because they do not have quarantine flags, not because they are locally signed. You can also remove quarantine flags from anything you download and after that you don't have the right click option either. For example: xattr -dr com.apple.quarantine ~/Downloads/Absolutely-Not-Malware.dmg
- saagarjha 6y agoThe comment you're replying to is confusing because it's been copied out of context from where it was originally posted, which as a discussion of a mandatory signing requirement on Apple silicon.
- wila 6y agoThanks for the correction. Yes I see now what you mean and with that background Xenadu02's reply does make a lot more sense. Don't have access to a Apple Developer Transition Kit, so was not aware of the new requirements.