OSNews

Not at all, it's an update for PPC... I doubt x86 patch are advertised to other than the one under NDA

This security update breaks 64-bit applications since it is shipping with a broken version of libSystem

Amazing.

Mathematica stopped functioning immediately after I installed this update, and console.log said it was because Mathematica could not find /usr/lib/libSystem.B.dylib, although it reported that it did find a file in /usr/lib by that name, of "unknown file type." I don't know if this means the file got unexpectedly changed, or corrupted, but it put the kibosh on my Mathematecizing for the day.

Me again. I should have added that ls -al showed that /usr/lib/libSystem.B.dylib had most recently been 'touched' at the time I performed the security update, which certainly suggests that it was the update itself that caused the problem.

Instead of complaining on this forum, why don't you ring up the company that makes Mathematica, and inform them of the situation - they may have a work around or a patch they maybe able to forward to you.

email form Wolfram:

"** Important notification for users of G5 Macintosh systems running OS X 10.4 **

At approximately 8 p.m. PDT on Monday, August 15, Apple began
automatic distribution of Apple Security Update 2005-007 for Mac
OS X 10.4.2 (Tiger).

Due to an error on the part of Apple, this update prevents any
64-bit-native application from running. In particular, this means
that Mathematica 5.2 will not run on any G5 system if it has
installed this Security Update.

This problem was discovered by our testing procedures a few hours
ago, and Apple has now assured us that they have stopped
automatic distribution of Security Update 2005-007 at this time.

If you did not install Security Update 2005-007, then you will
not be affected. If your Mathematica 5.2 successfully launches
and performs any computation (such as 2+2), then this also means
that you have not been affected.

If you have been affected, then Mathematica 5.2 will generate a
MathLink error when you try to do any computation with it. (If
you run MathKernel directly from the command line, it will crash
at startup.)

Apple has informed us that there is no workaround for this
problem.

Apple is investigating the problem at high priority, and intends
to distribute a new Security Update in the very near future. This
update will correct the problem and allow Mathematica to run
successfully.

To run Mathematica 5.2 today, you must temporarily disable its
64-bit capabilities. You can do this by running the following
commands in the Terminal:

cd /Applications/Mathematica 5.2.app/Contents/MacOS
cp MathKernel MathKernel.bak
lipo MathKernel.bak -remove ppc64 -output MathKernel

If you are unable to run the script above, an alternative is to
use an earlier version of Mathematica. The problem with Apple
Security Update 2005-007 affects only 64-bit applications;
Mathematica 5.2 is the first 64-bit-native version of
Mathematica.

Note that when Apple has made the corrected Security Update
available, and you have installed it, you must reverse the
procedure above by running the following commands:

cd /Applications/Mathematica 5.2.app/Contents/MacOS
mv MathKernel.bak MathKernel

If you do not do run these commands, Mathematica will not operate
in optimized native 64-bit mode.


We regret the inconvenience caused by this problem, and hope that
as soon as Apple has corrected the problem you will continue to
enjoy the outstanding performance of Mathematica on 64-bit
Macintosh systems.

Sincerely,

The Technical Support Team
Wolfram Research, Inc.

P.S. Should you require further technical support for this problem,
Apple has informed us that you should contact them through
http://www.apple.com/contact/phone_contacts.html"

Umm, what do you think the first thing I did was? What am I, some 13 year old kid who thinks he's "breaking" some security leak? It wasn't a complaint, and I most certainly was not expecting to find any useful advice from this forum. I only posted it here A) because someone had mentioned there was a problem, but offered no documentation, and some other person immediately assumed it was a MS troll, so I just wanted to confirm it was a specific, legitimate problem, and B) so that maybe other people wouldn't install the update. I have now received confirmation from Apple, via Wolfram, that their update did roger libSystem, and that there was no workaround. Thanks for your snide reply and assumption that I'm just some idiot who wanted to complain about how Apple sucks and doesn't have the first fscking idea of what to do when I have a technical problem except whine about it.

i use windows xp every day and i never get hacked. u just got 2 know how to use a pc and download the right software you faget

You seem to think that an Intel Mac will somehow magically may the Airport problems go away. Curious...