utilities/system updates
08/18/2005, 6:35am, EDT
Thursday, August 18th
Apple updates security patch to fix 64-bit glitch
Apple late Wednesday night fixed a glitch in its recent security update that prevented Tiger users from running 64-bit applications. As reported yesterday, the initial version of the Security Update 2005-007 1.0 accidently disabled 64-bit computing under Mac OS X 10.4.2, while addressing nearly three dozen other security exploits. Security Update 2005-007 v1.1, now available for both Client and Server editions of Tiger (via the web and Software Update), replaces Security Update 2005-007 v1.0 for Tiger systems Mac OS X v10.4.2. Apple recommends that users who have already installed v1.0 on Tiger systems to install v1.1. Version 1.1 of the update "provides a combined 32- and 64-bit version of LibSystem to replace the 32-bit version that was delivered in v1.0. No other changes have been made in version 1.1," according to Apple's documentation.
Filed under: software
, 
, 6
, 
, 
, 
, 
, 
, 
Top
subscribe to comments
for this article
So, if I read this correctly, Apple just FORGOT the 64-bit version of libsystem? Are you joking?
But with such a massive project, wouldn't the build scripts all be, well, scripted, such that it wouldn't require someone to remember to turn on or off some feature (like a big ol' -O or something). But then why would someone be hacking their way through the build scripts, esp. touching the parts that probably wouldn't have changed for a security patch?
Update scripts, on the other hand, have to be updated/tweaked/created for each build (as what needs to be installed changes). It seems to me like a more likely scenario to actually forget to include something.
But I'm basing this on personal experience where I never touch my compile scripts unless I have to, but I'm always forgetting a file when building the update package.