This update fixes errors seen in previous versions when running in the latest beta, and adds the system version to saved reports.
XProtect
The apps claim my Mac is running an old version, but that the newer version was installed weeks ago. How come?
First release version of what was EFIcienC, to check EFI firmware, security settings, and security updates automatically.
So you downloaded and installed a ‘silent’ security update. But how do you get it to work on your Mac? Isn’t that automatic too?
SwiftUI, notarization, malware detection, and Time Machine for APFS: all look worryingly incomplete in Catalina. Are they a bit premature?
With recent privacy protection, notarization requirements, and extended checking of executable code, it’s getting more common for an app not to launch. What can you do when that happens?
Important changes for anyone distributing command tools in particular, and a good time to ensure you only ship signed and notarized apps if possible.
Look in Activity Monitor or the log, and you won’t find anything named Gatekeeper, is its a team of different systems, each of which can work on its own. Here’s the detail and a diagram.
First full release version, which conforms to macOS clearance convention, and lets you know which flags it has changed.
How this occurs, why, and what to do to manage the problem when it affects you. Complete with a visual summary and references.
