Apple ARM binary codesign issue
ryandesign at macports.org
Thu Sep 24 14:05:22 UTC 2020
On Sep 24, 2020, at 08:51, Ruben Di Battista wrote:
> Ok, that's what I didn't know. I thought It was mandatory for Apple Store software and not everything... 😔
Yup. As of macOS Big Sur 11 beta 6, released September 3, 2020, codesigning is mandatory for everything on ARM Macs. How to deal with that in MacPorts is what this thread is about. See https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11-universal-apps-beta-release-notes:
> New in macOS 11 on Apple silicon Mac computers, and starting in macOS Big Sur 11 beta 6, the operating system enforces that any executable must be signed before it’s allowed to run. There isn’t a specific identity requirement for this signature: a simple ad-hoc signature is sufficient. This new behavior doesn’t change the long-established policy that our users and developers can run arbitrary code on their Macs, and is designed to simplify the execution policies on Apple silicon Mac computers and enable the system to better detect code modifications. This new policy doesn’t apply to translated x86 binaries running under Rosetta 2, nor does it apply to macOS 11 running on Intel-based platforms.
More information about the macports-dev