Certificate revocation checks in macOS could be misused in surveillance. How could you prevent that without putting your Mac at risk?
Does Big Sur require you to sign your own apps or other code using a proper Apple-issued signature? What about notarization and quarantine? Your questions answered.
You try to open an app on your M1 Mac, only to see an alert telling your that you don’t have permission to open it. Only that isn’t the reason.
Final in series. Examines how the hardened runtime controls access to protected private data and services, and how some use private entitlements.
Second in the series. Considers in detail what the hardened environment offers the user, and how notarized apps can opt out of its protection.
If you were to strip unwanted code from a Universal App, would it still pass Big Sur’s strict security checks?
If you have no other option and can be certain there’s no danger in doing so, you can remove a signed app’s signature. But it may not be so simple.
Stepping through building it correctly in Xcode, turning it into an Installer package getting it notarized and the ticket stapled to the tool.
Coming now to Apple Silicon Macs: all ARM-native executable code is required to be signed. Full details of this important change.
Who’s been ghost notarizing other people’s apps, and is Catalina wasting time to check whether shell scripts are notarized?