Good day, We are currently in the process of updating our build process to yield kernel extensions that do not generate a code signing warning on Mac OS 10.9 (aka, start signing kexts). We obtained new signing keys from Apple, dropped them in, turned on code signing, and everything worked. However, a detail remains that is confusing. According to Session 707 from WWDC 2013, we need to code sign using, among other things, Mac OS 10.8.3 or later, or else kernel extensions will not validate on Mac OS 10.8.3 or later. Our build server currently is running Mac OS 10.8.2, and Xcode 4.4.1. The resulting build appears to successfully run on Mac OS 10.6.8, 10.7.5, 10.8.5, and 10.9.2. Although we haven't tried all of the subversions, I was surprised that the kernel extensions loaded on 10.8.5 and 10.9.2, given what was said in Session 707. My initial thought here is "it's not broken; don't fix it". We've had problems in the past where we upgrade Xcode by a minor bug release, and suddenly our kexts don't load on one of the versions on OS X. This has caused us to want to avoid messing with the build server unless there is a real problem to address. So… Should we be worried that our build server is not running 10.8.3 or later? Actually, here's a better question: What subversions of OS X might have a problem with this? If we can see that the build doesn't work on a specific subversion of OS X, that would be reason enough to risk messing with the build server. Thanks, - Andrew Keller _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.app... This email sent to site_archiver@lists.apple.com