On Oct 23, 2014, at 11:24 AM, Landon J Fuller wrote: > > On Oct 22, 2014, at 5:25 PM, Ryan Schmidt wrote: > >> On Oct 22, 2014, at 1:40 PM, Dan Ports wrote: >> >>> 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. >> >> I can understand the security motivations behind this change. You don't want >> untrusted code running in your kernel. > > It’s no more untrusted than any other code being run from MacPorts :-)
There's most certainly a difference in the potential for damage from bad kernel code vs. bad user code. One can cause a kernel panic; the other can't. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
