I haven't upgraded to Yosemite myself yet, but I'm hearing that in 10.10 the system refuses to load any unsigned kernel modules by default. Worse, the only option for working around it appears to be turning off signature checks entirely.
This is obviously a problem for ports that build kexts, like osxfuse. What can we do about this? Dan -- Dan R. K. Ports UW CSE http://drkp.net/
--- Begin Message ---#45521: osxfuse 2.7.0 fails to load (Yosemite) ---------------------------------+---------------------- Reporter: nicolas.stransky@… | Owner: dports@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.2 Resolution: | Keywords: yosemite Port: osxfuse | ---------------------------------+---------------------- Comment (by fondacio@…): This might be relevant: https://github.com/Homebrew/homebrew/issues/31164. Relevant quote: "This is going to be a big pain in the behind for Homebrew, MacPorts, and compiling things from source generally. Currently, from 10.10, the system no longer permits unsigned kexts to run, at all. The only public way to circumvent this 'security' measure at the moment is to disable //all// kext signing checks, which is a less than delightful solution. The other way is limited to those with Apple development signing capabilities, which involves signing the kexts with your own certificates which will then enable them to run under Yosemite." -- Ticket URL: <https://trac.macports.org/ticket/45521#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
--- End Message ---
_______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
