That post title is a bit misleading: kexts need to be codesigned, and with a certificate issued by Apple. However, 3rd party developers can get these certificates (the process is a bit more involved than getting a regular app/installer codesigning cert, but doesn’t cost extra on top of the regular annual codesigning cert expense).
That’s what the title says, though. It doesn’t say “provided by Apple”. I guess, yes, coming from a context of unfamiliarity with the types of signing Apple does, clarification could be useful.
But I can’t build a kext myself and use it without disabling all kext security, right?
I use openafs, which is unsigned. Pain in the bosom.
Same here… the cost for signing is probably more than the openafs project will ever be able to afford. I think they may be trying to get a few of the universities that use afs heavily to try and split the bill somehow :/
Previously discussed here (in the context of Trim Enabler):