On 5 Mar 2014, at 03:18, Matt Bauer <matt@ciderapps.com> wrote:
The other problem you may face is Xcode getting confused with certificates.
A good option here is to use codesign to extract the certificate that was actually used to sign the binary, just to confirm that it is what you think it is. See the "--extract-certificates" option in <x-man-page://1/codesign>.
Make sure you have the KEXT endorsement on your developer ID from Apple.
Once you've extracted the certificate you can Quick Look it and then look for the required magic (a custom extension with OID 1.2.840.113635.100.6.1.18). Share and Enjoy -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.... This email sent to site_archiver@lists.apple.com