That's perfectly clear, but every recent Audio Hijack update has come with an ACE update.
Will each future one require our going the entire rigamarole again?
- Just as in Catalina on Intel Macs all kernel extension installations must be approved. If the extension is from Apple, or is properly signed by an approved developer, approval is automatic. Otherwise...
- the security settings must be changed to allow the installation of software that is not from Apple or an approved developer. Just as on Intel Macs with a T2 chip, re-setting the security settings for Macs with Apple SoC inside, require booting into the Recovery drive. On Intel Macs that reset is good for any bootable volume on that Mac. On Macs with Apple SoC, the setting is good only for that one bootable volume. (Whether or not that security setting will survive a clone operation or not I can't tell, because Apple's ASR utility doesn't work on Apple silicon yet, but I know that it doesn't survive a nuke and pave.)
- the user must approve or disapprove the installation, update, or removal of each non-Apple or Apple approved extension.
- Kernel extensions become effective by being incorporated into an extensions cache contained in the boot snapshot.
- Every time an extension is installed, updated, or removed that cache must be rebuilt.
- The installation and rebuild is not effective until the system is rebooted.
- The administrative user's approval of the installation in System Preferences > Security & privacy > General triggers the rebuild of the extensions cache and reboot.
So it would appear that assuming every update of Audio Hijack includes an updated ACE then it would require approval of the kext install and a reboot, but re-etting the security option would not be required so you would not hav to boot into the Recovery Drive. But
if the Security setting does not survive the ASR then you would have to boot into the Recovery Drive to change the security setting after each cloning procedure. (But that is still TBD.)
