Security Update 2005-007 v1.1 Released

[MacRumors]

https://www.macrumors.com/images/macrumorsthreadlogodarkd.png

After accidentally breaking 64 bit compatibility with version 1.0, Apple has released an updated version of the new Security Update that provides a combined 32 & 64 bit version of LibSystem.

Security Update 2005-007 delivers a number of security enhancements and is recommended for all Macintosh users.

Security Update 2005-007 v1.1 replaces Security Update 2005-007 v1.0 for Tiger systems Mac OS X v10.4.2. Users who have already installed v1.0 on Tiger systems should install v1.1.

Security Update 2005-007 v1.1 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.

This update includes the following components:

AppKit
BlueTooth
CoreFoundation
cups
Directory Services
HIToolBox
Kerberos
loginwindow
Mail
OpenSSL
QuartzComposerScreenSaver
Security Interface
Safari
X11
zlib

For detailed information on this Update, please visit this website: http://www.info.apple.com/kbnum/n61798

 

[g4pismo]

oops -- serves me right for updating right away...

 

[supergod]

Downloading right now. Hope it fixes some of the weird audio-out issues I've been having since the last one.

 

[RndmAxess]

Deleted

 

[AoWolf]

What other apps besides Mathmatica did Security Update 2005-007 break?

I'm not familiar with which apps are running 64 bit aware.

Yeah I had no idea there were any real apps using 64. Well it good that they fixed it so fast.

 

[sonny]

for that one person who wondered why anyone would ever worry about a security update...

 

[iDM]

haha that was quick

 

[CubaTBird]

this isn't the first time this happened... accidentally?

 

[ijimk]

Well glad to know they addressed the issue quickly...

 

[bwilfong]

This was available at 6:00 A.M. this morning at least. Why did it take MacRumors so long to post this?

 

[supergod]

It's annoying, but macrumors is always at least a few hours behind the times. Generally it's not a problem, but sometimes it even takes days to post a topic. One could say they're being very careful about their facts, or simply that it is difficult staying up to date, but I still find it to be very annoying. Most front page rumors are posted long after users have started their own forums on the topic, so I find it best to check all of the forums rather than the front page anyways, which is really the point of a rumor community like this.

 

[hob]

has anyone had a keyboard issue with v1.0? I'm installing 1.1 now so hopefully it'll go away, but on both my powerbook and powermac, my keyboard randomly stops responding - I'd have to log out and in again to get it to respond!!

 

[hob]

This was available at 6:00 A.M. this morning at least. Why did it take MacRumors so long to post this?

You don't say where you're from.... but, I was thinking about this.

I loaded the page at 16.00BST (GMT+1), it said posted at 10.00EST (GMT-5) - so I'm assuming I'm one of the first people to be reading this.

I could understand it being available at 10.00, Apple employees arriving at work in the morning at 8.30 or 9.00 and rolling it out, but when you said 6.00, I thought "woa, someone must have been up all night with this one!"

 

[57004]

Downloading right now. Hope it fixes some of the weird audio-out issues I've been having since the last one.

Yeah I noticed that too, sometimes the sound is suddenly choppy, especially in Battlefield 1942. But it's not likely as the kbase article from apple says the following about this update:

Security Update 2005-007 v1.1 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.

So I don't think that will be fixed. Frankly, I'm wondering why they recommend ALL tiger users with the previous update to install this one, I don't see why it would matter on my powerbook G4 which doesn't even do 64-bit..

Edit: hob: my keyboard was working fine, no problems there

 

[aprilfools]

No problems so far

I downloaded 1.1.early this morning. So far no problems.

 

[aaronsullivan]

You know, when I see people complain about issues after an update, I get this sinking feeling that they haven't issued a report to Apple itself. PLEASE tell Apple about it so they can fix it, and don't just complain about it on forums the right people will never read or care about.

Imagine if the Mathematica programmers only posted the issue on a MacRumors forum. Do you think this patch would be out yet?

Anyway, it is nice to see a quick fix like this. I'm sure some Apple programmers are sleeping for the first time, now, in 48 hours. It does seem like something that shouldn't have happened in the first place, though. It's pretty major.

 

[Plymouthbreezer]

Tisk tisk Apple... Don't get sloppy now.

 

[wdlove]

Kudos to Apple for a prompt bug fix. Thank you Apple.

 

[vonraptus]

has anyone had a keyboard issue with v1.0? I'm installing 1.1 now so hopefully it'll go away, but on both my powerbook and powermac, my keyboard randomly stops responding - I'd have to log out and in again to get it to respond!!

Yes!
Scary stuff, good to know i'm not alone!
So we'll get 1.2 tomorrow then?

Using a 1.33 PBook

 

[quackattack]

It looks like all those who wait to update finally had a good reason to. I must say I am a little suprised.

 

[killmoms]

I'd hate to be the guy that forgot to check "compile for 64-bit" when he did the final build for LibSystem for Security Update 1.0... Bet he got a stern "talking to."

 

[Bibulous]

has anyone had a keyboard issue with v1.0? I'm installing 1.1 now so hopefully it'll go away, but on both my powerbook and powermac, my keyboard randomly stops responding - I'd have to log out and in again to get it to respond!!

Yes, the keyboard (Apple USB) would not respond in Finder (could not rename folders), but works fine in other apps like MS Word.

Relaunched the Finder and it was back to normal, this has happen twice since the update - weird.

 

[AidenShaw]

even worse

I'd hate to be the guy that forgot to check "compile for 64-bit" when he did the final build for LibSystem for Security Update 1.0... Bet he got a stern "talking to."

I'd hate to be the manager of Apple's OSX QA group....

Introducing a bug like this shows a clear lack of proper QA procedures - specifically that there are *NO* 64-bit tests anywhere inside or outside of Apple on the final build.

Perhaps there were no 64-bit tests on any of the builds.

Hole, Truck, Drive Through....

 

[SiliconAddict]

Tell me again about how Apple's wares are so much better then MS's. This is the kind of crap I expect from a MS patch. And please guys. Don't act like this is the first time this has happened. IMHO it feels like Apple is treating their user base like release candidate testers which is NOT in any way shape or form cool.

 

[shamino]

I'd hate to be the guy that forgot to check "compile for 64-bit" when he did the final build for LibSystem for Security Update 1.0... Bet he got a stern "talking to."

How about the QA people who apparently don't have any 64-bit apps in their regression testing suite?