Earlier quoted context omitted.
That's not correct. To quote Apple: > New in macOS 11 on Apple silicon Mac computers, and starting in the next macOS Big Sur 11 beta, the operating system will enforce that any executable must be signed with a valid signature before it’s allowed to run. There isn’t a specific identity requirement for this signature: a simple ad-hoc signature issued locally is sufficient, which includes signatures which are now genera…
And, as a user, what is the mechanism for ad-hoc signing an unsigned binary on silicon? :) You can’t distribute ad-hoc signed binaries. You can’t disable/bypass the gatekeeper on silicon. If you have access to a transition kit you can see this for yourself.
`codesign -s - my_binary`, though that would rarely be necessary unless you patched it in a hex editor or something, since otherwise it would have been automatically ad-hoc signed when it was linked.
> You can’t distribute ad-hoc signed binaries.
They have the same distribution restrictions on Apple silicon as on Intel. You can, but it requires the person running the binary to either (a) run it in a terminal, (b) right-click Open, or (c) use spctl --master-disable to disable Gatekeeper entirely.