At first, I thought the new XProtect version should be 5272, but some updated without that version changing. Then I stumbled across a secret way to update. Not a good omen for the release of Sequoia.
Sequoia
How SilentKnight can install macOS updates, up to a point, and how you can recover from an inadvertent download of a macOS update.
One cause of an app crashing as soon as it’s launched, these constraints prevent you from running bundled apps copied elsewhere, and can now be used by third-party apps.
Why disable the whole of SIP when all you need is to disable some of its features? Here are all the options explained, and how to combine them.
Sonoma 14.4 added support for exclaves and conclaves, which are used in Sequoia’s virtual machines. What is an exclave, and what does it add?
After a batch of new MacBook Pros were delivered with SIP disabled: LockRattler (December 2016), EFIcienC then SilentKnight (July 2019), and here’s what version 3 should look like.
While other Macs had happily updated XProtect’s data in the normal way, my Sequoia beta system told me it was out of date, and refused to find an updater. Then I recalled an old tweet.
How is it going to be harder to run apps that haven’t been notarized in Sequoia, and does it bring any benefit in return for the inconvenience?
How to update XProtect from a version number of 0 to 5271 in a single command, with the aid of a new version of SilentKnight.
Sequoia doesn’t use previous tools to update and maintain XProtect, so causes havoc with apps like Skint and SilentKnight. Two updates should help.
The Eclectic Light Company 