Issue with current macOS 11.3 beta 3 - kernel extensions

Hi!

Since current macOS 11.3 beta 3, a bug appeared that was also present on some previous betas :(

When loading a kernel extension, if it's unsigned but explicity allowed on AppleKextExcludeList (the list where Apple stores old safe kernel extensions, like vmware ones, some filesystems, etc) fails to load. This is a problem for all of us that want to keep running some legit software with no equivalent under SystemExtensions frameworks.

This is just an example of osxfuse present on allowed list by Apple, but happens with ALL kernel extensions on the allowed list (like turbo boost switcher one, vmware, etc).

All works just fine with current 11.2 Big Sur release.., please, fix that in order to add again the check against that list present on /Library/Apple/System/Library/Extensions/AppleKextExcludeList.kext/Contents/Info.plist
  • -- sudo kextutil -v ../Desktop/osxfusefs.kext

Defaulting to kernel file '/System/Library/Kernels/kernel'

Executing: /usr/bin/kmutil load --bundle-path /Users/Ruben/Desktop/osxfusefs.kext

Error Domain=KMErrorDomain Code=29 "Authenticating extension failed: Kext com.github.osxfuse.filesystems.osxfusefs v2.6.1 in executable kext bundle com.github.osxfuse.filesystems.osxfusefs at /private/var/db/KernelExtensionManagement/Staging/com.github.osxfuse.filesystems.osxfusefs.HnEP4u/osxfusefs.kext:

Authenticating extension failed: Bad code signature" UserInfo={NSLocalizedDescription=Authenticating extension failed: Kext com.github.osxfuse.filesystems.osxfusefs v2.6.1 in executable kext bundle com.github.osxfuse.filesystems.osxfusefs at /private/var/db/KernelExtensionManagement/Staging/com.github.osxfuse.filesystems.osxfusefs.HnEP4u/osxfusefs.kext:

Authenticating extension failed: Bad code signature}

Accepted Reply

Fiexed on 11.3 beta 4, just verified. Great! :)

Replies

Just Filed an issue with FB9029443
By the way, of course disabling SIP all works just fine..
Fiexed on 11.3 beta 4, just verified. Great! :)