And a kernel extension certificate is used to sign the passthrough file system extension.
I’m not sure how you came to that conclusion. There is such a thing as a KEXT-enabled code-signing identity [1], but that’s irrelevant to this discussion.
Does it need to be signed?
Yes. FSKit modules must be signed with the com.apple.developer.fskit.fsmodule entitlement. That’s a restricted entitlement, which means it must be authorised by a provisioning profile [2] [3]. To create that profile, you’ll need to be a member of a paid team.
Based on our records it looks like you are a member of a paid team. Given that, you should be able to get this working as follows:
- Sign into with your Apple Account in Xcode > Apple Accounts.
- In the sample code project, for each target, go to the Signing & Capabilities editor and select your team in the Team popup.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
[1] See KEXT Code Signing Problems for more info about that.
[2] To learn more about profiles, see TN3125 Inside Code Signing: Provisioning Profiles.
[3] You can probably bypass this by disabling SIP, but that’s not something I recommend in general.