For some reason Apple wants to change external kernel extensions location from /System/Library/Extensions to /Library/Extensions and introduced in Mavericks a code signing requirement for all extensions and/or drivers located in that folder. Extensions will not be loaded if not signed (those located in the “old” folder and not signed will only generate a warning [check my SyScan360 slides]). The signing certificates require a special configuration and to obtain them you need to justify it.
Print
Share
Comment
Cite
Upload
Translate
APA
() » Breaking OS X signed kernel extensions with a NOP. Retrieved from https://www.truth.cx/2013/11/23/breaking-os-x-signed-kernel-extensions-with-a-nop/.
MLA" » Breaking OS X signed kernel extensions with a NOP." - , https://www.truth.cx/2013/11/23/breaking-os-x-signed-kernel-extensions-with-a-nop/
HARVARD » Breaking OS X signed kernel extensions with a NOP., viewed ,
VANCOUVER - » Breaking OS X signed kernel extensions with a NOP. [Internet]. [Accessed ]. Available from: https://www.truth.cx/2013/11/23/breaking-os-x-signed-kernel-extensions-with-a-nop/
CHICAGO" » Breaking OS X signed kernel extensions with a NOP." - Accessed . https://www.truth.cx/2013/11/23/breaking-os-x-signed-kernel-extensions-with-a-nop/
IEEE" » Breaking OS X signed kernel extensions with a NOP." [Online]. Available: https://www.truth.cx/2013/11/23/breaking-os-x-signed-kernel-extensions-with-a-nop/. [Accessed: ]