We are seeing the same issue with our UAD-2 system driver. I filed a bug about it, radar: 24270565.I looked into it, and the problem appears to be that we are code signing everything on our build machine which is running OS X 10.8. Ideally we’d be running a later OS, but suffice it to say there are reasons we can’t do that right now. Codesigning on 10.8 results in a “v1 resource envelope”, which is technically obsolete and results in codesign --verify -vvvv <path to kext>” reporting it as such. However, the kext has always actually loaded fine on all systems prior to this 10.11.4 beta, and kextutil -nt” would not report any issues. But on the 10.11.4 beta, kextutil -nt” now reports that the code signature is invalid, and won’t load the kext. I manually re-signed the kext on my 10.9.5 system, and now the kext loads fine on the 10.11.4 system (code signing on 10.9.5 results in the v2 resource envelope getting generated in the signature).The v1 resource envelope was an issue for apps dist
Topic:
App & System Services
SubTopic:
Core OS
Tags: