Make a note on paper or your iOS device of the developer ID provided in parentheses, as you’ll need those in a few moments.Ĭlose your apps down and restart your Mac in Recovery mode. If the extension is notarized already, they will instead look like Origin=Developer ID Application: DeveloperName (NJ2ABCUVC1) Then press Return, and you should see three lines of response: Then drag and drop the extension from your Downloads folder to the end of that line, where its path and name should appear, e.g. One easy way to do this is to type most of the command To get the developer ID and check whether that extension has been notarized in one fell swoop, use the spctl command in the form There, locate one of the kernel extensions, open the contextual menu, and export that whole kext (the folder with the extension. The simplest way to obtain this now is to open the Installer package using Suspicious Package. The only piece of information that you require is the developer ID of those kernel extensions.
Check first to ensure that you’re not overlooking the normal security dialog, which invites you to open the Security & Privacy pane and agree to the extensions being installed there. Of course there are a thousand and one other possible reasons, but here I’ll assume it’s the result of this change in security. The probable cause is that one or more of the kernel extensions haven’t been notarized, and the security system in macOS has taken exception to that, refusing to install them. The install fails for no apparent reason. I fear with the onset of notarization, this scenario is going to become increasingly common: you’ve just tried to install software which you understand includes at least one kernel extension, and has worked fine before macOS 10.14.5 (which you’re running).
0 kommentar(er)
