It turns out that the new code signing feature in OS X is breaking
programs. Apparently quite a few new programs.
http://securosis.com/2007/11/01/leopard-firewall-code-signing-breaks-skype-and-other-applications
http://www.heise-security.co.uk/news/98492
I *approve*. And I hope Apple sticks to its guns.
In a nutshell, OS X can sign an application for you the first time that
the application runs. From that point forward, it checks the signature
every time that application runs.
Basically, whole bunches of programs are doing self-modification for
lots of different reasons--none of them beneficial to me, the user. And
Leopard busts them for it.
My only complaint is that Apple did not bring up a gigantic "DO NOT USE
THIS PROGRAM! NOW QUARANTINING!" warning box replete with klaxons and
red warning signs when the code check fails.
At this point, if you write an application on OS X, you either put your
user data where the user tells you, or you don't get to play at all.
Beautiful. Just beautiful.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
