在Kextload期间将Kext与kext启用的证书进行协同编码失败,"代码签名无效"

Question

所以我们有一个允许我们签署kexts的证书,但是当我们运行> sudo kextload friendly.kext时,它失败了,我们签署了我们想要的kext,并证明它已签名,这里是一些诊断输出:

codesign --verify -vvvv friendly.kext

friendly.kext: valid on disk
friendly.kext: satisfies its Designated Requirement

spctl -a -vvvv friendly.kext

friendly.kext: accepted
source=Developer ID
origin=Developer ID Application: Friendly Corporation 
/Library/Extensions 

codesign -dvvv friendly.kext

Executable=/Library/Extensions/friendly.kext/Contents/MacOS/friendly
Identifier=com.friendly.friendly
Format=bundle with Mach-O thin (x86_64)
CodeDirectory v=20200 size=502 flags=0x0(none) hashes=18+3 location=embedded
Hash type=sha1 size=20
CDHash=a1e2bf8d53ea67c6cfe9fc3d6d2001fe56c838a7
Signature size=8528
Authority=Developer ID Application: Friendly Corporation
Authority=Developer ID Certification Authority
Authority=Apple Root CA
Timestamp=Oct 9, 2014, 11:49:02 AM
Info.plist entries=21
TeamIdentifier=1234567890
Sealed Resources version=2 rules=12 files=1
Internal requirements count=1 size=180

codesign --verify -vvvv friendly.kext

friendly.kext: valid on disk
friendly.kext: satisfies its Designated Requirement 

看起来它签名正确; 但是,当我运行> sudo kextutil -v friendly.kext时:

Defaulting to kernel file '/System/Library/Kernels/kernel'
Diagnostics for /Library/Extensions/friendly.kext:
Code Signing Failure: code signature is invalid
/Library/Extensions/friendly.kext appears to be loadable (not including linkage for on-disk libraries).
ERROR: invalid signature for com.techsmith.friendly, will not load 

我想我要么错误地下载了证书(我们肯定已经批准了kext签名),虽然我之前试过重新下载证书一次,所以这可能不是问题.否则,这就是我签约的方式.我想也许它与我在签名之前在kext上设置的权限有关？

以前有人见过这个问题吗？

提前致谢!

Answer 1

kext签名证书必须列出扩展名"(1.2.840.113635.100.6.1.18)" - 这就是将其指定为启用kext的证书.您可以通过在Keychain Access.app中查看它来轻松验证这一点.(它列在底部附近,在扩展名"(1.2.840.113635.100.6.1.13)"下面,我认为它用于应用程序,因此出现在所有开发者ID证书中)